agentleFS
LazyIsEfficientLazyIsEfficient/agentic-os/.claude/skills/autoresearch/SKILL.md

autoresearch

Skill17 starsChanged 24 days agoMITView on GitHub

Run Karpathy-style autoresearch optimization on any content. Generates 50+ variants, scores with a 5-expert simulated panel, evolves winners through multiple rounds, outputs optimized version + full experiment log. Use when optimizing landing pages, email sequences, ad copy, headlines, form pages, CTA text, or any conversion-focused content. Triggers on "optimize this page", "run autoresearch", "score these variants", "A/B test this copy".

105 other projects use a version of this, 2 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

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

  • 0

    Common

    Most of the 101 edited versions we read keep these.

  • 7

    Distinctive

    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
  1. Distinctive:

    Every run outputs 3 files:

    line 19
  2. Distinctive:

    Run up to 3 rounds per element.

    line 31
  3. Distinctive:

    Write 3 output files: optimized content, experiments JSON, optimization report.

    line 33
  4. Distinctive:

    < 70: Don't ship. Something fundamental is broken.

    line 49
  5. Distinctive:

    Never call the API once per variant.

    line 57
  6. Distinctive:

    Don't over-optimize for one dimension — a 95 clarity + 45 trust is a misleading overall score.

    line 58
  7. Distinctive:

    Don't run more than 5 rounds.

    line 59

“Common” is measured: kept by at least 6 in 10 of the 101 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 Skill

Karpathy-style optimization loops for any conversion-focused content. No traffic needed. Simulated expert panel. Minutes, not weeks.

The sequence: Run autoresearch FIRST to hit 85+ simulated score. Then deploy. Then validate with real traffic.

What You'll Produce

Every run outputs 3 files:

FilePurpose
{name}-optimized.{ext}The winning optimized content
data/{name}-experiments.jsonFull experiment log — all variants + all scores
data/{name}-optimization-report.mdHuman-readable summary with winner rationale

Core rules

  1. Intake: parse content type from file extension (HTML → landing/form page; markdown → email/ad copy). List all optimizable elements and confirm with user before starting.
  2. Score every variant against the 5-expert panel in a single batched API call per round — never one call per variant.
  3. Run up to 3 rounds per element; stop early when top variant hits the minimum score threshold (default: 80).
  4. Cross-breed only after each element has its own winner — premature cross-breeding creates incoherent combinations.
  5. Write 3 output files: optimized content, experiments JSON, optimization report.
  6. Report back: winning score, biggest score jump, top 2 runner-ups, file paths, next step.

User Options

OptionDefaultDescription
elementsallWhich elements to optimize
variants_per_round10How many variants per round
min_score80Stop when this score is hit
rounds3Max rounds before stopping
auto_applyfalseOverwrite source file with winners
content_typeauto-detectForce a content type if auto-detect is wrong

Quality Gates

  • < 70: Don't ship. Something fundamental is broken.
  • 70-79: Marginal. One more round targeting the lowest-scoring dimension.
  • 80-84: Good. Shippable. Validate with real traffic.
  • 85-89: Strong. Ship with confidence.
  • 90+: Rare. Ship immediately.

Anti-Patterns

  • Never call the API once per variant. Always batch. A 10-variant round = 1 call.
  • Don't over-optimize for one dimension — a 95 clarity + 45 trust is a misleading overall score.
  • Don't run more than 5 rounds. If not hitting 80 after 3, the problem is strategic, not tactical.

References

  • references/round-structure.md — round-by-round procedure and 5-expert panel definitions
  • references/content-types.md — elements and score dimensions per content type (landing pages, email, ads, forms)
  • references/execution-protocol.md — 6-step execution protocol with JSON schema

Related skills

  • content-ops — quality scoring gate; run after autoresearch optimization
  • conversion-ops — audits a LIVE landing-page URL across CRO dimensions; use it instead when scoring a live page rather than optimizing copy variants pre-launch

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.