[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6QAXBTWQWE34Y4DXKYMSWYM":3,"skill-same:01M6QAXBTWQWE34Y4DXKYMSWYM":77},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":14,"repositoryHtmlUrl":57,"repositoryHomepageUrl":58,"ownerHtmlUrl":59,"ownerBlogUrl":60,"ownerDescription":61,"updatedAt":62,"install":63,"resources":76},"01M6QAXBTWQWE34Y4DXKYMSWYM","autoresearch-agent",null,"Autonomous experiment loop that optimizes any file by a measurable metric. Inspired by Karpathy's autoresearch. The agent edits a target file, runs a fixed evaluation, keeps improvements (git commit), discards failures (git reset), and loops indefinitely. Use when: user wants to optimize code speed, reduce bundle\u002Fimage size, improve test pass rate, optimize prompts, improve content quality (headlines, copy, CTR), or run any measurable improvement loop. Requires: a target file, an evaluation command that outputs a metric, and a git repo.","Tashima-Tarsh\u002FDisha6.6","Tashima-Tarsh","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F269906498?v=4","01M6PBH98X03XERH0HFT4PFB1P","NITISH KUMAR","01M6PBH9DA0M6KM3Z12P848F0K",0,"MIT","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fautoresearch-agent\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"autoresearch","autoresearch agent","repo","outputs","headlines","rate","reduce","ctr","karpathy","use","command","image","quality","experiment loop","loop","improve","Evaluation","file","git","run","2026-11-10 10:12:30",false,"---\nname: \"autoresearch-agent\"\ndescription: \"Autonomous experiment loop that optimizes any file by a measurable metric. Inspired by Karpathy's autoresearch. The agent edits a target file, runs a fixed evaluation, keeps improvements (git commit), discards failures (git reset), and loops indefinitely. Use when: user wants to optimize code speed, reduce bundle\u002Fimage size, improve test pass rate, optimize prompts, improve content quality (headlines, copy, CTR), or run any measurable improvement loop. Requires: a target file, an evaluation command that outputs a metric, and a git repo.\"\nlicense: MIT\nmetadata:\n  version: 2.0.0\n  author: Alireza Rezvani\n  category: engineering\n  updated: 2026-03-13\n---\n\n# Autoresearch Agent\n\n> You sleep. The agent experiments. You wake up to results.\n\nAutonomous experiment loop inspired by [Karpathy's autoresearch](https:\u002F\u002Fgithub.com\u002Fkarpathy\u002Fautoresearch). The agent edits one file, runs a fixed evaluation, keeps improvements, discards failures, and loops indefinitely.\n\nNot one guess — fifty measured attempts, compounding.\n\n---\n\n## Slash Commands\n\n| Command | What it does |\n|---------|-------------|\n| `\u002Far:setup` | Set up a new experiment interactively |\n| `\u002Far:run` | Run a single experiment iteration |\n| `\u002Far:loop` | Start autonomous loop with configurable interval (10m, 1h, daily, weekly, monthly) |\n| `\u002Far:ar-status` | Show dashboard and results |\n| `\u002Far:ar-resume` | Resume a paused experiment |\n\n---\n\n## When This Skill Activates\n\nRecognize these patterns from the user:\n\n- \"Make this faster \u002F smaller \u002F better\"\n- \"Optimize [file] for [metric]\"\n- \"Improve my [headlines \u002F copy \u002F prompts]\"\n- \"Run experiments overnight\"\n- \"I want to get [metric] from X to Y\"\n- Any request involving: optimize, benchmark, improve, experiment loop, autoresearch\n\nIf the user describes a target file + a way to measure success → this skill applies.\n\n---\n\n## Setup\n\n### First Time — Create the Experiment\n\nRun the setup script. The user decides where experiments live:\n\n**Project-level** (inside repo, git-tracked, shareable with team):\n```bash\npython scripts\u002Fsetup_experiment.py \\\n  --domain engineering \\\n  --name api-speed \\\n  --target src\u002Fapi\u002Fsearch.py \\\n  --eval \"pytest bench.py --tb=no -q\" \\\n  --metric p50_ms \\\n  --direction lower \\\n  --scope project\n```\n\n**User-level** (personal, in `~\u002F.autoresearch\u002F`):\n```bash\npython scripts\u002Fsetup_experiment.py \\\n  --domain marketing \\\n  --name medium-ctr \\\n  --target content\u002Ftitles.md \\\n  --eval \"python evaluate.py\" \\\n  --metric ctr_score \\\n  --direction higher \\\n  --evaluator llm_judge_content \\\n  --scope user\n```\n\nThe `--scope` flag determines where `.autoresearch\u002F` lives:\n- `project` (default) → `.autoresearch\u002F` in the repo root. Experiment definitions are git-tracked. Results are gitignored.\n- `user` → `~\u002F.autoresearch\u002F` in the home directory. Everything is personal.\n\n### What Setup Creates\n\n```\n.autoresearch\u002F\n├── config.yaml                        ← Global settings\n├── .gitignore                         ← Ignores results.tsv, *.log\n└── {domain}\u002F{experiment-name}\u002F\n    ├── program.md                     ← Objectives, constraints, strategy\n    ├── config.cfg                     ← Target, eval cmd, metric, direction\n    ├── results.tsv                    ← Experiment log (gitignored)\n    └── evaluate.py                    ← Evaluation script (if --evaluator used)\n```\n\n**results.tsv columns:** `commit | metric | status | description`\n- `commit` — short git hash\n- `metric` — float value or \"N\u002FA\" for crashes\n- `status` — keep | discard | crash\n- `description` — what changed or why it crashed\n\n### Domains\n\n| Domain | Use Cases |\n|--------|-----------|\n| `engineering` | Code speed, memory, bundle size, test pass rate, build time |\n| `marketing` | Headlines, social copy, email subjects, ad copy, engagement |\n| `content` | Article structure, SEO descriptions, readability, CTR |\n| `prompts` | System prompts, chatbot tone, agent instructions |\n| `custom` | Anything else with a measurable metric |\n\n### If `program.md` Already Exists\n\nThe user may have written their own `program.md`. If found in the experiment directory, read it. It overrides the template. Only ask for what's missing.\n\n---\n\n## Agent Protocol\n\nYou are the loop. The scripts handle setup and evaluation — you handle the creative work.\n\n### Before Starting\n1. Read `.autoresearch\u002F{domain}\u002F{name}\u002Fconfig.cfg` to get:\n   - `target` — the file you edit\n   - `evaluate_cmd` — the command that measures your changes\n   - `metric` — the metric name to look for in eval output\n   - `metric_direction` — \"lower\" or \"higher\" is better\n   - `time_budget_minutes` — max time per evaluation\n2. Read `program.md` for strategy, constraints, and what you can\u002Fcannot change\n3. Read `results.tsv` for experiment history (columns: commit, metric, status, description)\n4. Checkout the experiment branch: `git checkout autoresearch\u002F{domain}\u002F{name}`\n\n### Each Iteration\n1. Review results.tsv — what worked? What failed? What hasn't been tried?\n2. Decide ONE change to the target file. One variable per experiment.\n3. Edit the target file\n4. Commit: `git add {target} && git commit -m \"experiment: {description}\"`\n5. Evaluate: `python scripts\u002Frun_experiment.py --experiment {domain}\u002F{name} --single`\n6. Read the output — it prints KEEP, DISCARD, or CRASH with the metric value\n7. Go to step 1\n\n### What the Script Handles (you don't)\n- Running the eval command with timeout\n- Parsing the metric from eval output\n- Comparing to previous best\n- Reverting the commit on failure (`git reset --hard HEAD~1`)\n- Logging the result to results.tsv\n\n### Starting an Experiment\n\n```bash\n# Single iteration (the agent calls this repeatedly)\npython scripts\u002Frun_experiment.py --experiment engineering\u002Fapi-speed --single\n\n# Dry run (test setup before starting)\npython scripts\u002Frun_experiment.py --experiment engineering\u002Fapi-speed --dry-run\n```\n\n### Strategy Escalation\n- Runs 1-5: Low-hanging fruit (obvious improvements, simple optimizations)\n- Runs 6-15: Systematic exploration (vary one parameter at a time)\n- Runs 16-30: Structural changes (algorithm swaps, architecture shifts)\n- Runs 30+: Radical experiments (completely different approaches)\n- If no improvement in 20+ runs: update program.md Strategy section\n\n### Self-Improvement\nAfter every 10 experiments, review results.tsv for patterns. Update the\nStrategy section of program.md with what you learned (e.g., \"caching changes\nconsistently improve by 5-10%\", \"refactoring attempts never improve the metric\").\nFuture iterations benefit from this accumulated knowledge.\n\n### Stopping\n- Run until interrupted by the user, context limit reached, or goal in program.md is met\n- Before stopping: ensure results.tsv is up to date\n- On context limit: the next session can resume — results.tsv and git log persist\n\n### Rules\n\n- **One change per experiment.** Don't change 5 things at once. You won't know what worked.\n- **Simplicity criterion.** A small improvement that adds ugly complexity is not worth it. Equal performance with simpler code is a win. Removing code that gets same results is the best outcome.\n- **Never modify the evaluator.** `evaluate.py` is the ground truth. Modifying it invalidates all comparisons. Hard stop if you catch yourself doing this.\n- **Timeout.** If a run exceeds 2.5× the time budget, kill it and treat as crash.\n- **Crash handling.** If it's a typo or missing import, fix and re-run. If the idea is fundamentally broken, revert, log \"crash\", move on. 5 consecutive crashes → pause and alert.\n- **No new dependencies.** Only use what's already available in the project.\n\n---\n\n## Evaluators\n\nReady-to-use evaluation scripts. Copied into the experiment directory during setup with `--evaluator`.\n\n### Free Evaluators (no API cost)\n\n| Evaluator | Metric | Use Case |\n|-----------|--------|----------|\n| `benchmark_speed` | `p50_ms` (lower) | Function\u002FAPI execution time |\n| `benchmark_size` | `size_bytes` (lower) | File, bundle, Docker image size |\n| `test_pass_rate` | `pass_rate` (higher) | Test suite pass percentage |\n| `build_speed` | `build_seconds` (lower) | Build\u002Fcompile\u002FDocker build time |\n| `memory_usage` | `peak_mb` (lower) | Peak memory during execution |\n\n### LLM Judge Evaluators (uses your subscription)\n\n| Evaluator | Metric | Use Case |\n|-----------|--------|----------|\n| `llm_judge_content` | `ctr_score` 0-10 (higher) | Headlines, titles, descriptions |\n| `llm_judge_prompt` | `quality_score` 0-100 (higher) | System prompts, agent instructions |\n| `llm_judge_copy` | `engagement_score` 0-10 (higher) | Social posts, ad copy, emails |\n\nLLM judges call the CLI tool the user is already running (Claude, Codex, Gemini). The evaluation prompt is locked inside `evaluate.py` — the agent cannot modify it. This prevents the agent from gaming its own evaluator.\n\nThe user's existing subscription covers the cost:\n- Claude Code Max → unlimited Claude calls for evaluation\n- Codex CLI (ChatGPT Pro) → unlimited Codex calls\n- Gemini CLI (free tier) → free evaluation calls\n\n### Custom Evaluators\n\nIf no built-in evaluator fits, the user writes their own `evaluate.py`. Only requirement: it must print `metric_name: value` to stdout.\n\n```python\n#!\u002Fusr\u002Fbin\u002Fenv python3\n# My custom evaluator — DO NOT MODIFY after experiment starts\nimport subprocess\nresult = subprocess.run([\"my-benchmark\", \"--json\"], capture_output=True, text=True)\n# Parse and output\nprint(f\"my_metric: {parse_score(result.stdout)}\")\n```\n\n---\n\n## Viewing Results\n\n```bash\n# Single experiment\npython scripts\u002Flog_results.py --experiment engineering\u002Fapi-speed\n\n# All experiments in a domain\npython scripts\u002Flog_results.py --domain engineering\n\n# Cross-experiment dashboard\npython scripts\u002Flog_results.py --dashboard\n\n# Export formats\npython scripts\u002Flog_results.py --experiment engineering\u002Fapi-speed --format csv --output results.csv\npython scripts\u002Flog_results.py --experiment engineering\u002Fapi-speed --format markdown --output results.md\npython scripts\u002Flog_results.py --dashboard --format markdown --output dashboard.md\n```\n\n### Dashboard Output\n\n```\nDOMAIN          EXPERIMENT          RUNS  KEPT  BEST         Δ FROM START  STATUS\nengineering     api-speed            47    14   185ms        -76.9%        active\nengineering     bundle-size          23     8   412KB        -58.3%        paused\nmarketing       medium-ctr           31    11   8.4\u002F10       +68.0%        active\nprompts         support-tone         15     6   82\u002F100       +46.4%        done\n```\n\n### Export Formats\n\n- **TSV** — default, tab-separated (compatible with spreadsheets)\n- **CSV** — comma-separated, with proper quoting\n- **Markdown** — formatted table, readable in GitHub\u002Fdocs\n\n---\n\n## Proactive Triggers\n\nFlag these without being asked:\n\n- **No evaluation command works** → Test it before starting the loop. Run once, verify output.\n- **Target file not in git** → `git init && git add . && git commit -m 'initial'` first.\n- **Metric direction unclear** → Ask: is lower or higher better? Must know before starting.\n- **Time budget too short** → If eval takes longer than budget, every run crashes.\n- **Agent modifying evaluate.py** → Hard stop. This invalidates all comparisons.\n- **5 consecutive crashes** → Pause the loop. Alert the user. Don't keep burning cycles.\n- **No improvement in 20+ runs** → Suggest changing strategy in program.md or trying a different approach.\n\n---\n\n## Installation\n\n### One-liner (any tool)\n```bash\ngit clone https:\u002F\u002Fgithub.com\u002Falirezarezvani\u002Fclaude-skills.git\ncp -r claude-skills\u002Fengineering\u002Fautoresearch-agent ~\u002F.claude\u002Fskills\u002F\n```\n\n### Multi-tool install\n```bash\n.\u002Fscripts\u002Fconvert.sh --skill autoresearch-agent --tool codex|gemini|cursor|windsurf|openclaw\n```\n\n### OpenClaw\n```bash\nclawhub install cs-autoresearch-agent\n```\n\n---\n\n## Related Skills\n\n- **self-improving-agent** — improves an agent's own memory\u002Frules over time. NOT for structured experiment loops.\n- **senior-ml-engineer** — ML architecture decisions. Complementary — use for initial design, then autoresearch for optimization.\n- **tdd-guide** — test-driven development. Complementary — tests can be the evaluation function.\n- **skill-security-auditor** — audit skills before publishing. NOT for optimization loops.\n","# Autoresearch Agent\n\n> You sleep. The agent experiments. You wake up to results.\n\nAutonomous experiment loop inspired by [Karpathy's autoresearch](https:\u002F\u002Fgithub.com\u002Fkarpathy\u002Fautoresearch). The agent edits one file, runs a fixed evaluation, keeps improvements, discards failures, and loops indefinitely.\n\nNot one guess — fifty measured attempts, compounding.\n\n---\n\n## Slash Commands\n\n| Command | What it does |\n|---------|-------------|\n| `\u002Far:setup` | Set up a new experiment interactively |\n| `\u002Far:run` | Run a single experiment iteration |\n| `\u002Far:loop` | Start autonomous loop with configurable interval (10m, 1h, daily, weekly, monthly) |\n| `\u002Far:ar-status` | Show dashboard and results |\n| `\u002Far:ar-resume` | Resume a paused experiment |\n\n---\n\n## When This Skill Activates\n\nRecognize these patterns from the user:\n\n- \"Make this faster \u002F smaller \u002F better\"\n- \"Optimize [file] for [metric]\"\n- \"Improve my [headlines \u002F copy \u002F prompts]\"\n- \"Run experiments overnight\"\n- \"I want to get [metric] from X to Y\"\n- Any request involving: optimize, benchmark, improve, experiment loop, autoresearch\n\nIf the user describes a target file + a way to measure success → this skill applies.\n\n---\n\n## Setup\n\n### First Time — Create the Experiment\n\nRun the setup script. The user decides where experiments live:\n\n**Project-level** (inside repo, git-tracked, shareable with team):\n```bash\npython scripts\u002Fsetup_experiment.py \\\n  --domain engineering \\\n  --name api-speed \\\n  --target src\u002Fapi\u002Fsearch.py \\\n  --eval \"pytest bench.py --tb=no -q\" \\\n  --metric p50_ms \\\n  --direction lower \\\n  --scope project\n```\n\n**User-level** (personal, in `~\u002F.autoresearch\u002F`):\n```bash\npython scripts\u002Fsetup_experiment.py \\\n  --domain marketing \\\n  --name medium-ctr \\\n  --target content\u002Ftitles.md \\\n  --eval \"python evaluate.py\" \\\n  --metric ctr_score \\\n  --direction higher \\\n  --evaluator llm_judge_content \\\n  --scope user\n```\n\nThe `--scope` flag determines where `.autoresearch\u002F` lives:\n- `project` (default) → `.autoresearch\u002F` in the repo root. Experiment definitions are git-tracked. Results are gitignored.\n- `user` → `~\u002F.autoresearch\u002F` in the home directory. Everything is personal.\n\n### What Setup Creates\n\n```\n.autoresearch\u002F\n├── config.yaml                        ← Global settings\n├── .gitignore                         ← Ignores results.tsv, *.log\n└── {domain}\u002F{experiment-name}\u002F\n    ├── program.md                     ← Objectives, constraints, strategy\n    ├── config.cfg                     ← Target, eval cmd, metric, direction\n    ├── results.tsv                    ← Experiment log (gitignored)\n    └── evaluate.py                    ← Evaluation script (if --evaluator used)\n```\n\n**results.tsv columns:** `commit | metric | status | description`\n- `commit` — short git hash\n- `metric` — float value or \"N\u002FA\" for crashes\n- `status` — keep | discard | crash\n- `description` — what changed or why it crashed\n\n### Domains\n\n| Domain | Use Cases |\n|--------|-----------|\n| `engineering` | Code speed, memory, bundle size, test pass rate, build time |\n| `marketing` | Headlines, social copy, email subjects, ad copy, engagement |\n| `content` | Article structure, SEO descriptions, readability, CTR |\n| `prompts` | System prompts, chatbot tone, agent instructions |\n| `custom` | Anything else with a measurable metric |\n\n### If `program.md` Already Exists\n\nThe user may have written their own `program.md`. If found in the experiment directory, read it. It overrides the template. Only ask for what's missing.\n\n---\n\n## Agent Protocol\n\nYou are the loop. The scripts handle setup and evaluation — you handle the creative work.\n\n### Before Starting\n1. Read `.autoresearch\u002F{domain}\u002F{name}\u002Fconfig.cfg` to get:\n   - `target` — the file you edit\n   - `evaluate_cmd` — the command that measures your changes\n   - `metric` — the metric name to look for in eval output\n   - `metric_direction` — \"lower\" or \"higher\" is better\n   - `time_budget_minutes` — max time per evaluation\n2. Read `program.md` for strategy, constraints, and what you can\u002Fcannot change\n3. Read `results.tsv` for experiment history (columns: commit, metric, status, description)\n4. Checkout the experiment branch: `git checkout autoresearch\u002F{domain}\u002F{name}`\n\n### Each Iteration\n1. Review results.tsv — what worked? What failed? What hasn't been tried?\n2. Decide ONE change to the target file. One variable per experiment.\n3. Edit the target file\n4. Commit: `git add {target} && git commit -m \"experiment: {description}\"`\n5. Evaluate: `python scripts\u002Frun_experiment.py --experiment {domain}\u002F{name} --single`\n6. Read the output — it prints KEEP, DISCARD, or CRASH with the metric value\n7. Go to step 1\n\n### What the Script Handles (you don't)\n- Running the eval command with timeout\n- Parsing the metric from eval output\n- Comparing to previous best\n- Reverting the commit on failure (`git reset --hard HEAD~1`)\n- Logging the result to results.tsv\n\n### Starting an Experiment\n\n```bash\n# Single iteration (the agent calls this repeatedly)\npython scripts\u002Frun_experiment.py --experiment engineering\u002Fapi-speed --single\n\n# Dry run (test setup before starting)\npython scripts\u002Frun_experiment.py --experiment engineering\u002Fapi-speed --dry-run\n```\n\n### Strategy Escalation\n- Runs 1-5: Low-hanging fruit (obvious improvements, simple optimizations)\n- Runs 6-15: Systematic exploration (vary one parameter at a time)\n- Runs 16-30: Structural changes (algorithm swaps, architecture shifts)\n- Runs 30+: Radical experiments (completely different approaches)\n- If no improvement in 20+ runs: update program.md Strategy section\n\n### Self-Improvement\nAfter every 10 experiments, review results.tsv for patterns. Update the\nStrategy section of program.md with what you learned (e.g., \"caching changes\nconsistently improve by 5-10%\", \"refactoring attempts never improve the metric\").\nFuture iterations benefit from this accumulated knowledge.\n\n### Stopping\n- Run until interrupted by the user, context limit reached, or goal in program.md is met\n- Before stopping: ensure results.tsv is up to date\n- On context limit: the next session can resume — results.tsv and git log persist\n\n### Rules\n\n- **One change per experiment.** Don't change 5 things at once. You won't know what worked.\n- **Simplicity criterion.** A small improvement that adds ugly complexity is not worth it. Equal performance with simpler code is a win. Removing code that gets same results is the best outcome.\n- **Never modify the evaluator.** `evaluate.py` is the ground truth. Modifying it invalidates all comparisons. Hard stop if you catch yourself doing this.\n- **Timeout.** If a run exceeds 2.5× the time budget, kill it and treat as crash.\n- **Crash handling.** If it's a typo or missing import, fix and re-run. If the idea is fundamentally broken, revert, log \"crash\", move on. 5 consecutive crashes → pause and alert.\n- **No new dependencies.** Only use what's already available in the project.\n\n---\n\n## Evaluators\n\nReady-to-use evaluation scripts. Copied into the experiment directory during setup with `--evaluator`.\n\n### Free Evaluators (no API cost)\n\n| Evaluator | Metric | Use Case |\n|-----------|--------|----------|\n| `benchmark_speed` | `p50_ms` (lower) | Function\u002FAPI execution time |\n| `benchmark_size` | `size_bytes` (lower) | File, bundle, Docker image size |\n| `test_pass_rate` | `pass_rate` (higher) | Test suite pass percentage |\n| `build_speed` | `build_seconds` (lower) | Build\u002Fcompile\u002FDocker build time |\n| `memory_usage` | `peak_mb` (lower) | Peak memory during execution |\n\n### LLM Judge Evaluators (uses your subscription)\n\n| Evaluator | Metric | Use Case |\n|-----------|--------|----------|\n| `llm_judge_content` | `ctr_score` 0-10 (higher) | Headlines, titles, descriptions |\n| `llm_judge_prompt` | `quality_score` 0-100 (higher) | System prompts, agent instructions |\n| `llm_judge_copy` | `engagement_score` 0-10 (higher) | Social posts, ad copy, emails |\n\nLLM judges call the CLI tool the user is already running (Claude, Codex, Gemini). The evaluation prompt is locked inside `evaluate.py` — the agent cannot modify it. This prevents the agent from gaming its own evaluator.\n\nThe user's existing subscription covers the cost:\n- Claude Code Max → unlimited Claude calls for evaluation\n- Codex CLI (ChatGPT Pro) → unlimited Codex calls\n- Gemini CLI (free tier) → free evaluation calls\n\n### Custom Evaluators\n\nIf no built-in evaluator fits, the user writes their own `evaluate.py`. Only requirement: it must print `metric_name: value` to stdout.\n\n```python\n#!\u002Fusr\u002Fbin\u002Fenv python3\n# My custom evaluator — DO NOT MODIFY after experiment starts\nimport subprocess\nresult = subprocess.run([\"my-benchmark\", \"--json\"], capture_output=True, text=True)\n# Parse and output\nprint(f\"my_metric: {parse_score(result.stdout)}\")\n```\n\n---\n\n## Viewing Results\n\n```bash\n# Single experiment\npython scripts\u002Flog_results.py --experiment engineering\u002Fapi-speed\n\n# All experiments in a domain\npython scripts\u002Flog_results.py --domain engineering\n\n# Cross-experiment dashboard\npython scripts\u002Flog_results.py --dashboard\n\n# Export formats\npython scripts\u002Flog_results.py --experiment engineering\u002Fapi-speed --format csv --output results.csv\npython scripts\u002Flog_results.py --experiment engineering\u002Fapi-speed --format markdown --output results.md\npython scripts\u002Flog_results.py --dashboard --format markdown --output dashboard.md\n```\n\n### Dashboard Output\n\n```\nDOMAIN          EXPERIMENT          RUNS  KEPT  BEST         Δ FROM START  STATUS\nengineering     api-speed            47    14   185ms        -76.9%        active\nengineering     bundle-size          23     8   412KB        -58.3%        paused\nmarketing       medium-ctr           31    11   8.4\u002F10       +68.0%        active\nprompts         support-tone         15     6   82\u002F100       +46.4%        done\n```\n\n### Export Formats\n\n- **TSV** — default, tab-separated (compatible with spreadsheets)\n- **CSV** — comma-separated, with proper quoting\n- **Markdown** — formatted table, readable in GitHub\u002Fdocs\n\n---\n\n## Proactive Triggers\n\nFlag these without being asked:\n\n- **No evaluation command works** → Test it before starting the loop. Run once, verify output.\n- **Target file not in git** → `git init && git add . && git commit -m 'initial'` first.\n- **Metric direction unclear** → Ask: is lower or higher better? Must know before starting.\n- **Time budget too short** → If eval takes longer than budget, every run crashes.\n- **Agent modifying evaluate.py** → Hard stop. This invalidates all comparisons.\n- **5 consecutive crashes** → Pause the loop. Alert the user. Don't keep burning cycles.\n- **No improvement in 20+ runs** → Suggest changing strategy in program.md or trying a different approach.\n\n---\n\n## Installation\n\n### One-liner (any tool)\n```bash\ngit clone https:\u002F\u002Fgithub.com\u002Falirezarezvani\u002Fclaude-skills.git\ncp -r claude-skills\u002Fengineering\u002Fautoresearch-agent ~\u002F.claude\u002Fskills\u002F\n```\n\n### Multi-tool install\n```bash\n.\u002Fscripts\u002Fconvert.sh --skill autoresearch-agent --tool codex|gemini|cursor|windsurf|openclaw\n```\n\n### OpenClaw\n```bash\nclawhub install cs-autoresearch-agent\n```\n\n---\n\n## Related Skills\n\n- **self-improving-agent** — improves an agent's own memory\u002Frules over time. NOT for structured experiment loops.\n- **senior-ml-engineer** — ML architecture decisions. Complementary — use for initial design, then autoresearch for optimization.\n- **tdd-guide** — test-driven development. Complementary — tests can be the evaluation function.\n- **skill-security-auditor** — audit skills before publishing. NOT for optimization loops.\n",{"name":5,"license":15,"metadata":49,"description":7},{"author":50,"updated":51,"version":52,"category":53},"Alireza Rezvani",1773360000000,"2.0.0","engineering","main","0da4485785ee599388900be50db1635489d53056",".agents\u002Fskills\u002Fautoresearch-agent","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6","https:\u002F\u002Fdisha6.6.thenitishkr.in\u002F","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh","www.thenitishkr","thenitishkr | AI • Cyber-security • Research\r\n","2026-11-08 03:33:25",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add Tashima-Tarsh\u002FDisha6.6 --skill autoresearch-agent",{"tool":69,"command":70},"bunx","bunx skills add Tashima-Tarsh\u002FDisha6.6 --skill autoresearch-agent",{"tool":72,"command":73},"pnpm","pnpm dlx skills add Tashima-Tarsh\u002FDisha6.6 --skill autoresearch-agent","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fautoresearch-agent\u002FSKILL.md",true,[],[78,108,131,156,179,202],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":87,"publishedAt":44},"01M6QRD07D4TGNDK6VJ4EHF8BV","youtube-full","Use when the user needs YouTube transcripts, video search, channel browsing, playlist extraction, or content monitoring. Trigger phrases: 'get the transcript for', 'search YouTube for', 'what are the latest videos on', 'list this playlist', 'monitor this channel', or any request involving a YouTube URL, video ID, or @handle. Do NOT use for downloading video or audio files, YouTube engagement data (likes, comments), or private\u002Fage-restricted videos.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fyoutube-full\u002FSKILL.md",[84],{"categoryNo":85,"categoryName":86,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",[88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107],"youtube full","youtube","full","transcript","search","monitoring","data","Video","Audio","list","files","do","get","age","trigger","URL","for","browsing","request","youtube transcripts",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":44},"01M6QRCJ3112VYPA97YG7KGMC2","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[115,116,117,118,92,119,53,120,121,122,123,124,125,126,33,127,128,129,130,104],"twitter","x twitter growth","growth","research","content","plan","web search","competitors","analyze","engine","write","strategy","platform","grow","posting","competitive",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":138,"publishedAt":44},"01M6QRBN3EHQNJY42RERP7A149","write-a-skill","Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, build, or author a new skill.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwrite-a-skill\u002FSKILL.md",[137],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[139,125,140,141,142,143,144,145,33,146,147,54,148,149,150,151,152,153,154,155],"write a skill","github","create","https","productivity","matt pocock","direct","example","build","new skill","structure","new agent","resources","with","tree","progressive disclosure","author",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":44},"01M6QRB6G8P33PNGAF9Y69EJ9T","wrap-up","Close out a launched Claude Managed Agent — recap every primitive the founder now owns, regenerate the single-file overview page, and suggest the next 1-2 upgrades. Use when the user says \"wrap up\", \"close this out\", \"what do I own now\", \"give me the summary\", \"recap the agent\", or when the orchestrator routes phase=wrap-up. primitives_inventory.py tables everything owned (agent, environment, session, memory, outcome, deployment); overview_page.py regenerates a self-contained .\u002Fmy-agent\u002Fagent-overview.html; upgrade_suggester.py ranks the next moves from recorded deferrals plus standing hardening steps. Companion to run-without-you; the last stop before phase=done.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwrap-up\u002FSKILL.md",[],[163,164,165,166,167,43,41,168,169,33,170,99,171,172,173,174,175,176,177,178],"wrap up","up","wrap","gemini","deployment","hardening","closeout","stop","upgrade","founder","close","companion","you","tables","directions","phase",{"skillNo":180,"name":181,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":183,"categories":184,"keywords":186,"publishedAt":44},"01M6QRA5AYC1RBFZ39GTWGS3N8","workflow-builder","Design and write deterministic multi-agent workflow scripts (.js files in .claude\u002Fworkflows\u002F) for Claude Code's Workflow tool. Use when a user wants to build, create, author, scaffold, or run a custom Claude Code workflow, orchestrate sub-agents (fan-out, pipeline, loop, judge-panel), or automate a repeatable multi-step task across fresh-context agents.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fworkflow-builder\u002FSKILL.md",[185],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[187,188,189,190,191,141,43,192,193,194,38,195,125,196,98,197,198,199,200,201],"workflow","workflow builder","builder","design","workflows","code","orchestrate","pipeline","multi-agent","context","across","fresh","scripts","judge","claude code workflow",{"skillNo":203,"name":204,"nameZh":6,"description":205,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":206,"categories":207,"keywords":208,"publishedAt":44},"01M6QR7QMCZESKQA0ERW1E657M","weekly-review","Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says \"\u002Fcs:weekly-review\". Walks David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — with deterministic scripts that inventory open loops, gate the checklist with named gaps, and score commitment health 0-100.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweekly-review\u002FSKILL.md",[],[209,210,211,212,213,214,215,216,217,38,218,219,220,221,222,223,100,224,225,178],"review","weekly review","weekly","deterministic scripts","reflect","feeds","inventory","open","team","projects","project-management","scanner","conversation","back","project","sprint","cadence"]