vc:autoresearch
Skill0 starsChanged 3 months agoMITView on GitHub
Autonomous iterative optimization loop for measurable metrics like coverage, performance, or bundle size. Use when repeated experiments can be judged by a mechanical score.
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 57
When required fields are missing, ask all at once:
- Distinctive: line 76
Commit BEFORE verify — git is memory, not a safety net
- Distinctive: line 78
Prefer git revert over git reset — preserve history
- Distinctive: line 145
Does not parallelize iterations — sequential by design (each iteration learns from the last)
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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.
Files
vc:autoresearch — Autonomous Optimization Loop
Constraint + Mechanical Metric + Fast Verification = Autonomous Improvement
When to Use
- Improve a measurable metric (test coverage, bundle size, ESLint errors, Lighthouse score, etc.)
- Autonomous execution over N iterations without manual intervention
- Git-tracked experiments where you want rollback on regression
- Exploring a search space of code changes with consistent evaluation
When NOT to Use
| Situation | Better Tool |
| Subjective goals ("make it cleaner") | execute-agent with an approved plan |
| Bug fixing with known root cause | debugger + execute-agent |
| One-shot tasks, no repetition needed | execute-agent |
| No mechanical metric to measure progress | normal RIPER flow instead of autoresearch |
| Files outside a defined scope | manual approach |
Configuration Format
Parsed from user message. Missing required fields trigger a batched AskUserQuestion.
Required
| Field | Description | Example |
Goal | Human description of what to improve | "Increase test coverage in src/utils" |
Scope | Glob pattern(s) for editable files | "src/utils/**/*.ts" |
Verify | Shell command that outputs a single number | "npx jest --coverage --json | jq '.coverageMap | .. | .s? | to_entries | map(.value) | (map(select(.>0)) | length) / length * 100' | tail -1" |
Optional
| Field | Default | Description |
Guard | none | Regression check command (exit 0 = pass) |
Iterations | 10 | Maximum iterations to run |
Noise | medium | Tolerance for metric variance: low / medium / high |
Min-Delta | 0 | Minimum improvement to count as progress |
Direction | higher | Whether higher or lower metric value is better |
Interactive Setup
When required fields are missing, ask all at once:
AskUserQuestion({
questions: [
{ question: "What metric do you want to improve? (e.g. 'test coverage in src/utils')", field: "Goal" },
{ question: "Which files may be edited? (glob, e.g. 'src/utils/**/*.ts')", field: "Scope" },
{ question: "Verify command — must print a single number to stdout", field: "Verify" },
{ question: "Guard command for regression check? (optional, press Enter to skip)", field: "Guard" }
]
})Core Protocol
See references/autonomous-loop-protocol.md for the full 8-phase specification.
Key invariants:
- ONE atomic change per iteration — atomicity test: can you describe it in one sentence without "and"?
- Commit BEFORE verify — git is memory, not a safety net
- Guard files are read-only — never modify files in guard command's scope
- Prefer
git revertovergit reset— preserve history
Results Logging
Each iteration appends a TSV line to loop-results.tsv in the working directory:
iteration commit metric delta status description
0 a1b2c3d 80.0 - baseline initial measurement
1 e4f5a6b 82.4 +2.4 keep add null checks to parser.ts
2 - 81.9 -0.5 discard extract helper functionSee references/autonomous-loop-protocol.md — Phase 7 for full schema.
Stuck Detection
| Condition | Action |
| 5 consecutive discards | Analyze patterns → shift strategy (different files, different approach) |
| 10 consecutive discards | STOP — report findings, surface to user |
Example Invocations
1. Increase test coverage
/vc:autoresearch
Goal: Increase test coverage in src/utils from ~60% to 80%
Scope: src/utils/**/*.ts, tests/utils/**/*.test.ts
Verify: npx jest tests/utils --coverage --coverageReporters=json-summary 2>/dev/null | node -e "const d=require('./coverage-summary.json');console.log(d.total.lines.pct)"
Guard: npx tsc --noEmit && npx jest --passWithNoTests
Iterations: 15
Direction: higher2. Reduce bundle size
/vc:autoresearch
Goal: Reduce main bundle size below 200KB
Scope: src/**/*.ts, src/**/*.tsx
Verify: npx vite build 2>/dev/null | grep "dist/index" | awk '{print $2}' | sed 's/kB//'
Guard: npx tsc --noEmit
Direction: lower
Min-Delta: 0.53. Eliminate ESLint errors
/vc:autoresearch
Goal: Drive ESLint error count to zero in src/api
Scope: src/api/**/*.ts
Verify: npx eslint src/api --format=json 2>/dev/null | node -e "const r=require('/dev/stdin');console.log(r.reduce((a,f)=>a+f.errorCount,0))" || echo 999
Direction: lower
Iterations: 20Limitations (Honest)
- Cannot optimize subjective or aesthetic goals
- Cannot modify files outside the declared
Scope - Cannot modify files referenced by the
Guardcommand - Cannot guarantee improvement — some metrics have hard ceilings
- Requires a git repository with a clean working tree before starting
Verifycommand must complete in < 30 seconds (otherwise loop is impractical)- Does not parallelize iterations — sequential by design (each iteration learns from the last)
References
references/autonomous-loop-protocol.md— Full 8-phase loop spec, decision matrix, anti-patternsreferences/git-memory-pattern.md— Git as cross-iteration memory, revert vs reset, commit conventionsreferences/guard-and-noise.md— Guard pattern for regression prevention, noise-aware verificationreferences/results-logging.md— TSV format spec, progressive summariesreferences/metric-library.md— Common verify commands by domain
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- opencue/cuecards★ 699% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository51 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- vc:kitSkill
- vc:auditSkill
- vc:autoresearchSkill
- vc:chrome-devtoolsSkill
- vc:context-engineeringSkill
- vc:debugSkill
- vc:docs-seekerSkill
- vc:generate-contextSkill
- vc:generate-planSkill
- vc:mcp-managementSkill
- vc:merge-worktreeSkill
- vc:previewSkill
- vc:problem-solvingSkill
- vc:publishSkill
- vc:repomixSkill
- vc:scoutSkill
- vc:securitySkill
- vc:sequential-thinkingSkill
- vc:setupSkill
- vc:stress-testSkill
- vc:tech-graphSkill
- vc:updateSkill
- vc:watzupSkill
- vc:web-testingSkill
- vc:xiaSkill
- vc:kitSkill
- vc:auditSkill
- vc:chrome-devtoolsSkill
- vc:context-engineeringSkill
- vc:debugSkill
- vc:docs-seekerSkill
- vc:generate-contextSkill
- vc:generate-planSkill
- vc:mcp-managementSkill
- vc:merge-worktreeSkill
- vc:previewSkill
- vc:problem-solvingSkill
- vc:publishSkill
- vc:repomixSkill
- vc:scoutSkill
- vc:securitySkill
- vc:sequential-thinkingSkill
- vc:setupSkill
- vc:stress-testSkill
- vc:tech-graphSkill
- vc:updateSkill
- vc:watzupSkill
- vc:web-testingSkill
- vc:xiaSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

