agentleFS
full-stack-skillsfull-stack-skills/agent-skills/skills/autoresearch/SKILL.md

autoresearch

Skill2 starsChanged 54 days agoApache-2.0View on GitHub

Autonomous iteration loop: modify, verify, keep/discard against any metric

100 other projects use a version of this, 5 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use aeon-update, auto-workflow and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • aaronjmarsSkill

    aeon-update

    Pull framework updates from the upstream Aeon repo into this instance - 3-way merges canon's new commits into a PR, never clobbering operator config.

    Also in 4 projects that use this

  • aaronjmarsSkill

    auto-workflow

    Two-mode aeon.yml workflow builder - analyze inspects URLs and emits a tiered, signal-verified skill-enablement plan plus an aeon.yml diff; enable flips slugs to enabled:true and opens a PR.

    Also in 4 projects that use this

  • +10 more from aaronjmars

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 96 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never push, publish, or deploy without explicit user approval.

    line 12
  2. Very specific:

    All results logged to autoresearch/{subcommand}-{YYMMDD}-{HHMM}/ directory.

    line 14

“Common” is measured: kept by at least 6 in 10 of the 96 edited versions of this file we could read. “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

Autoresearch — Autonomous Goal-directed Iteration

Safety Invariants (all subcommands)

  • Never push, publish, or deploy without explicit user approval.
  • Bounded by default. Override with Iterations: unlimited.
  • All results logged to autoresearch/{subcommand}-{YYMMDD}-{HHMM}/ directory.
  • Chain handoff via handoff.json. Evals reads *-results.tsv.

Dispatch (bare $autoresearch)

Parse the invocation in this order:

ConditionMode
Metric: or Verify: presentClassic — existing metric loop, unchanged
Free-form natural-language goal, no metric/verifyPlan — derive a reviewable metric and verification command; do not start an autonomous loop yet
NothingSetup wizard — interactive config builder
--classic flagForce Classic regardless of goal text

Print a banner on every invocation: [autoresearch] mode: classic | plan | wizard.

Subcommands

CommandDoesDefault Iterations
$autoresearchIterate against a metric: modify → verify → keep/discard25
$autoresearch planConvert a goal into validated Scope, Metric, Verify configN/A
$autoresearch debugHunt bugs: hypothesize → test → falsify → repeat15
$autoresearch fixCrush errors one-by-one until zero remain20
$autoresearch securitySTRIDE + OWASP audit with red-team personas15
$autoresearch shipShip through 8 phases: checklist → dry-run → deploy → verifyN/A
$autoresearch scenarioGenerate edge cases across 12 dimensions20
$autoresearch predict5 expert personas debate before implementationN/A
$autoresearch learnScout codebase → generate docs or wiki → validate → fix loop10
$autoresearch reasonAdversarial debate with blind judges until convergence8
$autoresearch probe8 personas interrogate requirements until saturation15
$autoresearch improveResearch ICP challenges, discover improvements, generate PRDs15
$autoresearch evalsAnalyze iteration results: trends, plateaus, regressionsN/A
$autoresearch regressionRegression stability gate: baseline vs candidate, verdict STABLE/UNSTABLEN/A

Universal Flags

FlagApplies ToPurpose
Iterations: NAll loopingSet iteration count
Iterations: unlimitedAll loopingOpt-in unbounded
--evalsAll loopingMid-loop checkpoints + final summary
--evals-interval NAll loopingOverride checkpoint frequency
--chain <targets>AllSequential handoff after completion
--<subcommand>AllShorthand for --chain <subcommand>
--classicBare $autoresearchForce Classic metric-loop mode

Natural-language goals

For a plain-language goal, load plan.md and produce a concrete Metric: and Verify: configuration for user review. Start the Classic loop only after those fields are explicit. This package does not currently include an executable cross-subcommand orchestrator.

references/orchestrator-routing.md records a future routing design. Treat it as design material only: do not invoke the commands described there and do not claim that automatic goal classification, state routing, or plateau detection is available.

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.