Agent skill

Inno Experiment Dev

by LigphiDonk in LigphiDonk/Oh-my--paper

Creates implementation plan, writes project code with judge feedback loop, and submits final experiment run.

MITAuto-check passedAgent Workflows

Install Inno Experiment Dev

skills CLI
$ npx skills add LigphiDonk/Oh-my--paper --skill inno-experiment-dev -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install LigphiDonk/Oh-my--paper inno-experiment-dev --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/LigphiDonk/Oh-my--paper.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/inno-experiment-dev .claude/skills/inno-experiment-dev && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
inno-experiment-dev
GitHub stars
738
Token cost
~2.8k tokens
SKILL.md length
945 words
Files
10 (incl. references)
Skills in repo
27
Repo updated
First seen
Licence
MIT

At a glance

Creates implementation plan, writes project code with judge feedback loop, and submits final experiment run.

  • Works in 3 steps: Create Implementation Plan → Implement and Iterate → Submit Experiment
  • Tasks that involve Planning
  • SKILL.md covers Canonical Summary, Trigger Rules, Resource Use Rules and Execution Contract, plus 8 more sections
  • Calls python

What it does

Inno Experiment Dev is an agent skill from LigphiDonk/Oh-my--paper. Creates implementation plan, writes project code with judge feedback loop, and submits final experiment run.

Its SKILL.md is about 2.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files, including reference files (for example `prompts/build_iteration_query.md`, `prompts/build_judge_query.md` and `prompts/build_judge_simple_query.md`).

It sits in Agent Workflows, covering Planning. The repository describes itself as: A Claude Code plugin that turns your terminal into an autonomous research lab — literature survey, experiment execution, paper writing, all in one pipeline. The licence is MIT.

When your agent uses it

  • Tasks that involve Planning

Example prompts

  • “Use the inno-experiment-dev skill to create implementation plan, writes project code with judge feedback loop, and submits final experiment run”
  • “/inno-experiment-dev”

Requirements

  • Python 3

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Create Implementation Plan
  2. Implement and Iterate
  3. Submit Experiment

What it can do on your machine

Read from SKILL.md and the folder at commit 6baece9. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • python

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Inno Experiment Dev loads about 2.8k tokens when it runs, and up to ~4.8k if it reads all its reference files. Until then it costs about 32 tokens; SKILL.md has 945 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~32
When it runs · the whole SKILL.md, loaded when a task matches
~2.8k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from LigphiDonk/Oh-my--paper at commit 6baece9, republished under its MIT licence (© LigphiDonk). 945 words, ~2,767 tokens.

Download SKILL.mdSave it as .claude/skills/inno-experiment-dev/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.
name
inno-experiment-dev
description
Creates implementation plan, writes project code with judge feedback loop, and submits final experiment run.
id
inno-experiment-dev
version
1.0.0
stages
experiment
tools
read_file, search_project, write_file
summary
Creates implementation plan, writes project code with judge feedback loop, and submits final experiment run. Use after code-survey in both Idea and Plan…
primaryIntent
experiment
intents
experiment
capabilities
research-planning
domains
general
keywords
inno-experiment-dev, experiment dev, research-planning, inno, experiment, dev, creates, implementation, plan, writes, project, code

inno-experiment-dev

Canonical Summary

Creates implementation plan, writes project code with judge feedback loop, and submits final experiment run. Use after code-survey in both Idea and Plan branches.

Trigger Rules

Use this skill when the user request matches its research workflow scope. Prefer the bundled resources instead of recreating templates or reference material. Keep outputs traceable to project files, citations, scripts, or upstream evidence.

Resource Use Rules

  • Read from references/ only when the current task needs the extra detail.

Execution Contract

  • Resolve every relative path from this skill directory first.
  • Prefer inspection before mutation when invoking bundled scripts.
  • If a required runtime, CLI, credential, or API is unavailable, explain the blocker and continue with the best manual fallback instead of silently skipping the step.
  • Do not write generated artifacts back into the skill directory; save them inside the active project workspace.

Upstream Instructions

Inno Experiment Dev (Planning, Implementation, and Submission)

Merges the former inno-implementation-plan, inno-ml-dev-iteration, and the submit step of inno-experiment-submit-refine. Mirrors _create_implementation_plan (830-858), _implement_and_iterate (861-920), and the submit portion of _submit_and_refine_experiments (922-945) in run_infer_idea_ours.py.

Inputs

VariableSourceDescription
survey_resinno-idea-generation or userThe finalized selected idea (or refined_for_downstream)
referencespipeline configPre-formatted string of source papers
updated_prepare_resinno-prepare-resourcesJSON with reference_codebases and reference_paths
code_survey_resinno-code-surveyComprehensive implementation report / model survey notes
dataset_descriptionfrom prepare step / contextDescription of available datasets (not in instance.json)
core_codeinstance.json Experiment.core_codeAbsolute path when created by Dr. Claw (e.g. <project_path>/Experiment/core_code); use as-is or resolve with path.join(project_path, value) if relative
code_referencesinstance.json Experiment.code_referencesAbsolute path when created by Dr. Claw (e.g. <project_path>/Experiment/code_references); use as-is or resolve if relative
max_iter_timespipeline configMax judge-iteration rounds (default 2)
context_variablesshared stateMutable dict carrying state across agents

Plan mode additionally uses ideas and survey-specific prompt variants (build_plan_query_with_survey, build_iteration_query_for_plan, etc.).

Outputs

VariableDescription
plan_resDetailed implementation plan with dataset, model, training, and testing sections
ml_dev_resFinal ML Agent implementation result
judge_resFinal Judge Agent feedback
judge_messagesFull conversation thread (preserved for inno-experiment-analysis)
submit_resExperiment submission result with statistical outputs
context_variablesUpdated with dataset_plan, training_plan, testing_plan, suggestion_dict, raw_error_stats

Cache Artifacts

FileAgentContent
Experiment/core_code/logs/coding_plan_agent.jsonCoding Plan Agentcontext_variables + messages from planning phase
Experiment/core_code/logs/machine_learning_agent.jsonML AgentInitial implementation messages (+ _iter_{N}.json for judge iterations)
Experiment/core_code/logs/judge_agent.jsonJudge AgentEvaluation messages (+ _iter_{N}.json for iterations)
Experiment/core_code/logs/machine_learning_agent_iter_submit.jsonML AgentSubmission run messages and results

Instructions

Phase 1: Create Implementation Plan

Mirrors _create_implementation_plan.

  1. Optional pre-step (Idea mode only): If refining the idea for implementation clarity, call the idea refinement agent to produce refined_for_downstream with tensor interfaces and forward-pass sketch.

  2. Build plan query:

    • Idea mode: plan_query = build_plan_query(survey_res, references, updated_prepare_res, code_survey_res, dataset_description) (see prompts/build_plan_query.md)
    • Plan mode: Use build_plan_query_with_survey(ideas, references, prepare_res, code_survey_res, dataset_description)
  3. Call Coding Plan Agent with messages = [{"role": "user", "content": plan_query}].

    • The agent reviews codebases using tree / cat, then creates structured plans via plan_dataset, plan_training, plan_testing.
    • Calls case_resolved to merge plans.
    • Set plan_res = plan_messages[-1]["content"].
    • See references/coding_plan_agent.md for agent details.
  4. Verify the plan has clear sections: dataset, model, training, evaluation, file layout.

Show full SKILL.md (458 more words)Show less
Phase 2: Implement and Iterate

Mirrors _implement_and_iterate.

  1. Initial implementation: Build ml_dev_query = build_ml_dev_query(survey_res, prepare_res, code_survey_res, plan_res, dataset_description, core_code, code_references) (see prompts/build_ml_dev_query.md). Use paths from instance.json: Experiment.core_code, Experiment.code_references (absolute in Dr. Claw–created projects; use as-is or resolve with project path if relative). Call ML Agent with messages = [{"role": "user", "content": ml_dev_query}]. Set ml_dev_res = ml_messages[-1]["content"].

    • See references/ml_agent_instructions.md for agent details.
  2. Initial judge evaluation: Build judge_query = build_judge_query(survey_res, prepare_res, plan_res, ml_dev_res) (see prompts/build_judge_query.md). Call Judge Agent with input_messages = [{"role": "user", "content": judge_query}]. Set judge_res = judge_messages[-1]["content"].

    • See references/judge_agent_instructions.md for agent details.
  3. Iteration loop (for i in 0..max_iter_times - 1): a. Build iteration_query = build_iteration_query(survey_res, prepare_res, code_survey_res, plan_res, ml_dev_res, judge_res, core_code, code_references) (see prompts/build_iteration_query.md). Use paths from instance.json (absolute in Dr. Claw–created projects; use as-is or resolve if relative). Plan mode uses build_iteration_query_for_plan. b. Append as user message to judge_messages. Call ML Agent with iter_times=i+1. Update ml_dev_res. c. Build judge_simple_query = build_judge_simple_query(survey_res, prepare_res, plan_res, ml_dev_res) (see prompts/build_judge_simple_query.md). Plan mode uses build_judge_simple_query_for_plan. d. Append as user message to judge_messages. Call Judge Agent with iter_times=i+1. Update judge_res. e. If "fully_correct": true in last message, break early.

  4. Preserve judge_messages for the submit step and for downstream inno-experiment-analysis.

Phase 3: Submit Experiment

Mirrors the submit portion of _submit_and_refine_experiments.

  1. Build submit query: submit_query = build_submit_query(survey_res, ml_dev_res, judge_res, core_code) (see prompts/build_submit_query.md). Resolve core_code from instance.Experiment.core_code. Plan mode uses build_submit_query_for_plan.

  2. Append to judge_messages as user message. Call ML Agent with iter_times="submit".

    • The agent adjusts epochs (3-10), runs run_training_testing.py, ensures checkpoints are saved.
    • Set submit_res = judge_messages[-1]["content"].
  3. If the implementation is not runnable, ML Agent calls case_not_resolved. Otherwise, case_resolved with statistical results and analysis.

Tool Mappings

All custom Python tools map to Claude Code built-in capabilities:

Original ToolClaude Code Equivalent
execute_commandShell tool (direct execution)
run_pythonpython <script> via Shell tool
create_file / write_fileWrite tool
read_fileRead tool or cat <path>
create_directorymkdir -p <path>
list_filesls <path>
gen_code_tree_structuretree -L 3 <path>
diagnose_code_errorAnalyze stderr output + inspect code
rollback_and_reimplementRe-write file with different approach
view_error_historyTrack error fingerprints in agent memory
plan_dataset / plan_training / plan_testingStructure plan sections in agent response
case_resolved / case_not_resolvedAgent returns result / failure reason

Checklist

  • Optional idea refinement applied if desired (Idea mode).
  • Correct build_plan_query variant used for Idea vs Plan mode.
  • Coding Plan Agent called; plan_res has clear dataset/model/training/testing sections.
  • ML Agent initial implementation completed; ml_dev_res recorded.
  • Judge Agent initial evaluation completed; judge_res recorded.
  • Iteration loop runs with correct prompt variants; early exit on fully_correct.
  • judge_messages preserved across all phases.
  • Submit query appended to judge_messages; ML Agent submission run completed.
  • Final model checkpoint saved to Experiment/core_code/checkpoints/model_final.pth.
  • Cache artifacts saved to Experiment/core_code/logs/: coding_plan_agent.json, machine_learning_agent.json, judge_agent.json, machine_learning_agent_iter_submit.json.

References

  • run_infer_idea_ours.py: _create_implementation_plan (830-858), _implement_and_iterate (861-920), _submit_and_refine_experiments submit step (922-945)
  • prompt_templates.py: build_plan_query (203-233), build_ml_dev_query (236-381), build_judge_query (384-417), build_iteration_query (420-468), build_judge_simple_query (471-494), build_submit_query (497-527)
  • Agent definitions: plan_agent.py, ml_agent.py, judge_agent.py in inno/agents/inno_agent/

© LigphiDonk, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 9 other files (references) in skills/inno-experiment-dev of LigphiDonk/Oh-my--paper.

  • SKILL.md
  • prompts/build_iteration_query.md
  • prompts/build_judge_query.md
  • prompts/build_judge_simple_query.md
  • prompts/build_ml_dev_query.md
  • prompts/build_plan_query.md
  • prompts/build_submit_query.md
  • references/coding_plan_agent.md
  • references/judge_agent_instructions.md
  • references/ml_agent_instructions.md

Open the folder on GitHubat commit 6baece9

Compare with similar skills

Inno Experiment Dev next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Inno Experiment Dev compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Inno Experiment Dev this skillLigphiDonk/Oh-my--paper738—~2.8kAutomated safety check: PassMIT
Executing Plans Inlineobra/superpowers296k2 repos~5.1kAutomated safety check: PassMIT
Interview Meaddyosmani/agent-skills103k6 repos~3.8kAutomated safety check: PassMIT
OpenSpec Guided OnboardingFission-AI/OpenSpec71k1 repos~4.5kAutomated safety check: PassMIT
Writing Plansgeeksblabla/stateofdev.ma16357 repos~661Automated safety check: PassNone
Subagent Driven DevelopmentAsvarox/allkaraoke26138 repos~1.2kAutomated safety check: PassNone

Similar skills

  • Executing Plans Inline

    obra/superpowers

    Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.

    296k GitHub starsUsed in 2 repos~5.1k tokens
    Agent WorkflowsAuto-check passed
  • Interview Me

    addyosmani/agent-skills

    Asks one question at a time, each with a best guess attached, until the agent is about 95 percent sure what you really want, before any plan, spec or code.

    103k GitHub starsUsed in 6 repos~3.8k tokens
    Agent WorkflowsAuto-check passed
  • OpenSpec Guided Onboarding

    Fission-AI/OpenSpec

    Walks you through a complete OpenSpec workflow cycle with narration while doing real work in your codebase.

    71k GitHub starsUsed in 1 repo~4.5k tokens
    Agent WorkflowsAuto-check passed
  • Writing Plans

    geeksblabla/stateofdev.ma

    A skill your agent uses when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file…

    163 GitHub starsUsed in 57 repos~661 tokens
    Agent WorkflowsAuto-check passed
  • Subagent Driven Development

    Asvarox/allkaraoke

    A skill your agent uses when executing implementation plans with independent tasks in the current session

    261 GitHub starsUsed in 38 repos~1.2k tokens
    Agent WorkflowsAuto-check passed
  • Planning With Files

    jd-opensource/JoySafeter

    Implements Manus-style file-based planning for complex tasks.

    313 GitHub starsUsed in 19 repos~1.8k tokens
    Agent WorkflowsAuto-check: notes

More from LigphiDonk/Oh-my--paper

All 27 skills in this repo
  • Preprint Search on bioRxiv

    LigphiDonk/Oh-my--paper

    Searches bioRxiv life sciences preprints by keyword, author, date range or category with a Python script, returning JSON metadata and optional PDF downloads.

    738 GitHub starsUsed in 13 repos~3.7k tokens
    Auto-check passed
  • Literature PDF OCR Library Builder

    LigphiDonk/Oh-my--paper

    Searches and downloads legally accessible academic PDFs, OCRs them to Markdown, and organizes the results into a traceable, AI-readable literature library.

    738 GitHub stars~1.1k tokensUpdated 5 mo ago
    Auto-check passed
  • Inno Code Survey

    LigphiDonk/Oh-my--paper

    Finds and clones missing code repositories for a chosen research idea, then writes a survey that maps academic concepts to their implementations.

    738 GitHub stars~3.6k tokensUpdated 5 mo ago
    Auto-check passed
  • Turns experimental data such as CSV, JSON or TensorBoard logs into statistical significance tests, visualizations and a drafted Results section.

    738 GitHub stars~3k tokensUpdated 5 mo ago
    Auto-check passed
  • Citation Verification Guide

    LigphiDonk/Oh-my--paper

    Lays out principles for catching fake, mismatched, or inconsistently formatted citations in academic writing, checked through live web search.

    738 GitHub stars~2.2k tokensUpdated 5 mo ago
    Auto-check passed
  • Single-Cell Initial Analysis

    LigphiDonk/Oh-my--paper

    Runs a seven-step quality-control and exploration pipeline on scRNA-seq, CyTOF or flow cytometry data and writes a plain-language report of what it found.

    738 GitHub starsUsed in 1 repo~1.4k tokens
    Auto-check passed

Categories

Questions about Inno Experiment Dev

What does Inno Experiment Dev do?

Creates implementation plan, writes project code with judge feedback loop, and submits final experiment run. Inno Experiment Dev is an agent skill from LigphiDonk/Oh-my--paper. Creates implementation plan, writes project code with judge feedback loop, and submits final experiment run.

When should I use Inno Experiment Dev?

Inno Experiment Dev fits situations like: tasks that involve Planning.

How do I install Inno Experiment Dev in Claude Code?

Run `npx skills add LigphiDonk/Oh-my--paper --skill inno-experiment-dev -a claude-code`. Or copy the skill folder (skills/inno-experiment-dev in LigphiDonk/Oh-my--paper) into .claude/skills/inno-experiment-dev in your project. Claude Code loads it when a task matches its description.

How do I install Inno Experiment Dev in Codex?

Run `npx skills add LigphiDonk/Oh-my--paper --skill inno-experiment-dev -a codex`. Or copy the skill folder (skills/inno-experiment-dev in LigphiDonk/Oh-my--paper) into .agents/skills/inno-experiment-dev in your project. Codex loads it when a task matches its description.

Can I use Inno Experiment Dev in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LigphiDonk/Oh-my--paper --skill inno-experiment-dev -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/inno-experiment-dev, .gemini/skills/inno-experiment-dev, .github/skills/inno-experiment-dev and .opencode/skills/inno-experiment-dev in your project.

What does Inno Experiment Dev need to run?

Going by SKILL.md and its folder, Inno Experiment Dev needs the command-line tools its instructions call (python). Our summary lists: Python 3.

Does Inno Experiment Dev access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Inno Experiment Dev safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Inno Experiment Dev use?

Inno Experiment Dev is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Inno Experiment Dev use?

About 2.8k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.1k tokens, read only when the agent opens those files.

What are the alternatives to Inno Experiment Dev?

Skills that share tags, products or a category with Inno Experiment Dev: Executing Plans Inline (obra/superpowers, 296k stars), Interview Me (addyosmani/agent-skills, 103k stars), OpenSpec Guided Onboarding (Fission-AI/OpenSpec, 71k stars) and Writing Plans (geeksblabla/stateofdev.ma, 163 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Inno Experiment Dev?

LigphiDonk (a GitHub user) maintains it in LigphiDonk/Oh-my--paper, which has 738 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on April 15, 2026.

Source: LigphiDonk/Oh-my--paper on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.