AI Research Engineering Playbooks

    1

    Turn any coding agent into a disciplined research engineer that plans, runs, debugs, and evaluates reproducible AI experiments end to end.

    Free

    1 useSecurity scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    AI Research Engineering Playbooks

    Example session with this skill installed

    I have a Llama-3.1-8B-Instruct base model and a finance instruction dataset at data/finance_train.jsonl (about 12k rows, held-out eval split at data/finance_eval.jsonl). Set up a low-memory LoRA fine-tuning experiment: pick sane rank, alpha, and learning-rate defaults, write the training config with a fixed seed, run a short sanity pass, then benchmark the adapter against the base model using identical prompt formatting and sampling parameters. Report perplexity and task accuracy side by side, review at least 30 failure cases, and flag anything that looks like train/eval leakage before I commit GPU hours to the full run.

    • Read your context and instructions
    • Compiled the ai research engineering

    Summary

    LoRA adapter finance-instruct-lora-v1 (r=16, alpha=32, 4-bit base, seed 17) trained on 11,842 deduplicated rows and evaluated against the base model with identical prompt formatting. Clear task improvement, no safety regression, one train/eval overlap issue flagged before the full run.

    MetricBaseLoRA v1
    Task accuracy54.1%71.6%
    Held-out perplexity9.86.2
    Refusal rate2.1%2.4%
    Train/eval overlap0.9%0.9%
    Median latency410ms415ms

    Artifacts in runs/finance-instruct-lora-v1/: config snapshot, environment versions, raw generations, and metric tables.

    Next steps

    • Purge the 107 overlapping eval records before spending more GPU hours
    • Retry r=32 if output formatting degrades on long answers
    • Manually review the 34 failure cases in results/failures.jsonl
    • Re-run the refusal/safety prompt suite after the full training pass

    Connects securely to your tools. The creator never sees your data.

    About this skill

    AI research often stalls on engineering overhead rather than scientific insight. This skill library provides disciplined workflows to transform general coding agents into practical research engineers. It replaces vague prompting with structured playbooks for data preparation, experiment execution, and rigorous evaluation.

    What it does

    • Standardizes experiments by providing reusable playbooks for data cleaning, training configurations, and benchmarking.
    • Ensures reproducibility through mandatory dataset fingerprinting, config snapshots, and environment logging.
    • Optimizes training with specific patterns for LoRA fine-tuning, parameter-efficient adapters, and checkpoint management.
    • Automates evaluation via benchmark protocols that calculate exact match, edit distance, and statistical significance.
    • Diagnoses failures using mechanistic diagnostic tools to hook into activations and identify layers causing hallucinations or refusals.
    • Generates reports by turning raw metrics and logs into paper-style summaries with ablation studies and error analysis.

    How it works

    1. Identify the specific research question, such as fine-tuning or inference tuning.
    2. Select the corresponding skill module from categories like data curation, training, or safety.
    3. Execute a dry run on a small data subset to verify the configuration and environment.
    4. Run the full experiment using provided Bash and YAML templates for consistent artifact logging.

    Frameworks & tools

    Built for Python-based ML workflows using Hugging Face PEFT, safetensors, vLLM for serving, and TransformerLens for mechanistic interpretability.

    Why this beats prompting it yourself

    Standard prompting often ignores reproducibility and data hygiene, leading to "hallucinated" results. This skill enforces a rigorous engineering loop that requires metric verification and failure analysis before declaring success.

    Use cases

    • Domain adaptation via LoRA fine-tuning for specific vertical tasks like finance or legal QA.
    • Performance profiling to identify bottlenecks in LLM serving latency and throughput.
    • Safety red-teaming to detect jailbreaks and calibrate refusal behavior.
    • Data auditing to detect contamination and leakage across training and evaluation splits.

    Known limitations

    Does not automate the creation of novel scientific theory. Requires an environment with pre-installed GPU drivers and ML libraries like PyTorch or JAX to execute playbooks.

    The training and serving examples assume GPU access and a Hugging Face / vLLM-style stack, so exact commands may need adaptation to other engines. It standardizes experiment hygiene and reporting but does not generate novel scientific hypotheses or guarantee benchmark outcomes.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    1 use

    Times used to date

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    • Free with an Agensi account

    Requires

    Python

    Permissions

    Terminal / Shell

    File Scopes

    **/*.yaml
    **/*.py
    **/*.md
    data/**
    runs/**

    Needs shell access to launch training, evaluation, and benchmark jobs, plus file read/write for configs, datasets, and run artifacts.

    Listed1 month ago

    What's inside

    Frequently Asked Questions

    While these playbooks are optimized for Python-based ML frameworks like Hugging Face and PyTorch, they are designed to be agent-agnostic and work with any coding agent capable of executing terminal commands and managing file structures.

    You will receive a library of structured YAML templates, Bash execution scripts, and modular Python workflows specifically designed for tasks like LoRA fine-tuning, benchmark automation, and model diagnostics.

    This skill bridges the gap between 'simple coding' and 'scientific rigor' by enforcing data fingerprinting, environment logging, and ablation study protocols that standard prompts typically overlook.

    Yes, the playbooks are modular; you can easily integrate the diagnostic or evaluation components into your existing ML pipelines without adopting the entire training workflow.

    The playbooks require a Linux-based environment with GPU drivers (CUDA/ROCm) and standard ML libraries like PyTorch or JAX already configured to execute the generated code.

    The fine-tuning, quantization, and serving playbooks assume GPU access (local or rented). The data-curation, benchmark-design, and research-reporting modules work CPU-only.

    PEFT/LoRA and Hugging Face-style training configs, plus vLLM-like serving knobs and a generic eval harness command pattern. The workflows are engine-agnostic, so you can map them onto your own stack.

    It enforces reproducibility artifacts (seeds, config snapshots, dataset fingerprints, raw logs), known failure-mode checklists, and evaluation hygiene such as leakage detection and refusal regression checks, so every result is auditable rather than a one-off run.

    New in LLM Ops

    Free