Ml Research Lab logo

Ml Research Lab

Community
AnastasiyaW
ml-research-lab

Machine-learning research loop for dataset curation, fine-tuning, evaluation, inference deployment, experiment tracking, and model explainability. Use when working on ML experiments, training data, model benchmarks, RunPod/GPU runs, classifier quality, vLLM/GGUF serving, SHAP-style model explanations, or research-to-code iterations. Do not use for a simple code edit that has no ML dataset, metric, model, or experiment artifact.

Overview

PublisherAnastasiyaW
Repositorycodex-claude-code-config
Skill nameml-research-lab
Stars
212
Forks
32
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by AnastasiyaW on GitHub. Read the source before you install it.

Installation

Install the Ml Research Lab AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/AnastasiyaW/codex-claude-code-config/tree/main/skills/ai-ml/ml-research-lab
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/AnastasiyaW/codex-claude-code-config.git /tmp/codex-claude-code-config
mkdir -p .claude/skills
cp -r /tmp/codex-claude-code-config/skills/ai-ml/ml-research-lab .claude/skills/ml-research-lab
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Ml Research Lab in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Ml Research Lab on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Ml Research Lab is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

ML Research Lab

Use this skill as the compact router for ML work. It is derived from an audit of synthetic-sciences/openscience at commit 531467c, but does not require running OpenScience or loading its full 250+ skill set.

Operating Loop

  1. Freeze the question as a measurable hypothesis.
  2. Identify dataset provenance, labels, splits, leakage risks, and regeneration cost.
  3. Pick the smallest baseline that can disprove the idea.
  4. Define metrics before training. For release claims, require train/val/test split, no test-set model selection, and multi-seed proof when cost permits.
  5. Run or wire experiment tracking before long jobs start.
  6. Save artifacts: config, command, data manifest, metrics JSON/CSV, logs, model hash, and a short conclusion.
  7. Compare against baseline, then keep/discard the change from evidence.

Domain Routing

  • Dataset or scrape cleanup: start from data quality, deduplication, leakage checks, train/eval splits, and regeneration notes.
  • Classical classifier or tabular baseline: use scikit-learn-style pipelines with preprocessing inside the pipeline and stratified splits for classification.
  • Model debugging or trust: add SHAP/explainability for feature importance, leakage, bias/proxy features, and misclassified samples.
  • LLM fine-tuning: prefer JSONL chat format, data validation, LoRA/QLoRA baseline, and tracked runs before scaling.
  • Single-GPU fast LoRA/QLoRA: consider Unsloth only after checking hardware, CUDA, model support, and export target.
  • Large or production inference: use vLLM for high-throughput GPU serving, GGUF or llama.cpp for local/Apple/CPU-friendly deployment, and TensorRT-LLM only when the NVIDIA production optimization cost is justified.
  • Research write-up: report method, dataset, exact metric formula, baseline source, limitations, and failure cases.

Verification Gates

  • Data gate: schema valid, duplicates/leakage checked, split manifest saved.
  • Metric gate: exact metric formula named; if benchmarked, original baseline source and benchmark code checked.
  • Runtime gate: command/log path and environment captured; GPU memory and errors checked for long runs.
  • Tracking gate: metrics are retrievable as JSON/CSV or a dashboard link plus local export.
  • Deployment gate: latency, throughput, memory, and OOM behavior measured before claiming production readiness.

Adoption Boundary

Do not import broad external skill collections wholesale. Use the inventory script scripts/openscience_skill_inventory.py to rank candidates, inspect the relevant source skill manually, then promote only compact workflows or deterministic scripts that improve our own tests.

Frequently asked questions

What does the Ml Research Lab AI skill do?

Machine-learning research loop for dataset curation, fine-tuning, evaluation, inference deployment, experiment tracking, and model explainability. Use when working on ML experiments, training data, model benchmarks, RunPod/GPU runs, classifier quality, vLLM/GGUF serving, SHAP-style model explanations, or research-to-code iterations. Do not use for a simple code edit that has no ML dataset, metric, model, or experiment artifact.

Why use Ml Research Lab on TypingMind?

Because you install it once and use it with any model. Ml Research Lab is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Ml Research Lab in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/AnastasiyaW/codex-claude-code-config/tree/main/skills/ai-ml/ml-research-lab. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Ml Research Lab?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Ml Research Lab?

As many as you like. As long as a model supports skills, you can use Ml Research Lab with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Ml Research Lab AI skill free?

Yes. It is published on GitHub by AnastasiyaW under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇