agentleFS
joshua-zyyjoshua-zyy/academic-paper-writer/skills/academic-experiments/SKILL.md

academic-experiments

Skill111 starsChanged 5 months agoMITView on GitHub

Audit, run, or verify experimental evidence for CS/AI/ML papers. Produces Evidence Inventory with evidence_type annotations (newly_run/preexisting_artifact/user_claim) and Protocol Risk assessments. Use when: checking if experiment results are reproducible, auditing existing experiment artifacts, running minimal reproducible commands, evaluating checkpoints without full retraining, documenting protocol risks like data leakage or missing baselines. Triggers on: 复核实验, run experiments, 实验结果, experiment evidence, verify results, 实验验证, evidence inventory, protocol risk, 跑实验, check results, reproduce experiments, 实验审计.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read manifest.yaml. It declares always_load files, axes, and references.on_demand.

    line 12
  2. Very specific:

    Read every file listed under always_load.

    line 13

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.
  4. 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.
  5. Echo the selected mode to the user before executing.
  6. 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.