AugmentClaude

Academic Experiments

Audit and verify experimental evidence for research papers with reproducibility checks.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up β€” so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.

    This copies the whole skill folder into ~/.claude/skills/academic-experiments-joshua-zyy/ β€” the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates β€” they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description β€” no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the β€œWhat this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

Use when auditing, running, or verifying the experimental evidence behind a CS/AI/ML paper β€” builds an evidence inventory, flags protocol risks like data leakage or missing baselines, and runs minimal reproducible checks without full retraining.

What this skill does

Academic Experiments

skill "",,

Router Protocol

  1. Read manifest.yaml. It declares always_load files, axes, and references.on_demand.
  2. Read every file listed under always_load. These are the skill's binding rules β€” not reference material.
  3. Apply the loaded material as constraints:
  • stance.md defines non-negotiable rules, evidence type semantics, failure degradation, and scope.
  • red-lines.md defines absolute prohibitions. Do not negotiate these.
  • output-contract.md defines deliverables per mode and claim-readiness classification.
  • anti-patterns.md defines known failure modes and their correct alternatives.
  1. Detect the mode using the manifest's mode axis: experiment-evidence-pass, evidence-inventory-only, or minimal-reproducible-run. Align evidence type semantics to ../shared/core/evidence-policy.md.
  2. Echo the selected mode to the user before executing.
  3. Reach for references/ only when the manifest's references.on_demand condition is satisfied.

Modes

ModeUse when
experiment-evidence-passFull audit: inventory + run + record + risk analysis
evidence-inventory-onlyInventory existing artifacts only, no execution
minimal-reproducible-runExecute minimal reproducible command (e.g. eval existing checkpoint)

Agent Dispatch

agents/experiment_agent.md is dispatched by academic-paper-writer orchestrator at Step 4. The agent may run experiments but must not modify project source code or data files, nor write paper prose independently.

Independent Use

InputModePriorityBehavior
repo_path + no run modeexperiment-evidence-pass2 (path trigger)Full audit: inventory β†’ env β†’ minimal run β†’ risk
repo_path + "inspect only"evidence-inventory-only1 (explicit)Inventory only, no commands
repo_path + specific commandminimal-reproducible-run1 (explicit)Verify env β†’ execute β†’ record
No repo_pathβ€”3 (no input)Ask path, or auto-detect entry files
ScenarioRecommended
Just auditing/reproducing evidenceThis skill (standalone)
Writing results into paper proseacademic-paper-writer orchestrator
Draft results need verificationThis skill β†’ academic-reviser

Related skills