Autoresearch Skill for Claude

> Run the Parallel Autoresearch Engine — massively parallel SKILL.md optimization. Generates 10+ SKILL.md variants per generation, tests each with programmatic harness (no browser needed), scores with triple-run averaging, and iterates autonomously. Use when asked to run autoresearch, improve SKILL.md at scale, or start parallel autoresearch.

864 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

134

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/popmechanic/VibesOS --skill autoresearch

The instruction itself

9 sections, as written by the author

Parallel Autoresearch Engine

> Plan mode: This skill is ONE plan step: "Invoke /vibes:autoresearch". Do not decompose.

Prerequisites Check

VIBES_ROOT="${CLAUDE_PLUGIN_ROOT:-$(dirname "$(dirname "${CLAUDE_SKILL_DIR}")")}"
echo "Checking autoresearch prerequisites..."
test -f "$VIBES_ROOT/scripts/eval-ssr-check.ts" && echo "✓ Tier 1.5 SSR check" || echo "✗ Missing eval-ssr-check.ts"
test -f "$VIBES_ROOT/scripts/eval-harness.ts" && echo "✓ Tier 2 harness" || echo "✗ Missing eval-harness.ts"
test -f "$VIBES_ROOT/scripts/eval-parallel.ts" && echo "✓ Orchestrator" || echo "✗ Missing eval-parallel.ts"
test -f "$VIBES_ROOT/scripts/eval-scoring.ts" && echo "✓ Scoring" || echo "✗ Missing eval-scoring.ts"
test -f "$VIBES_ROOT/eval/config.md" && echo "✓ Config" || echo "✗ Missing eval/config.md"
test -f "$VIBES_ROOT/eval/napkin.md" && echo "✓ Napkin" || echo "✗ Missing eval/napkin.md"
ls "$VIBES_ROOT/eval/specs/"*.md 2>/dev/null | wc -l | xargs -I{} echo "✓ {} eval specs found"
cd "$VIBES_ROOT/scripts" && bun -e "import React from 'react'; console.log('✓ React available')" 2>/dev/null || echo "✗ React not installed"

If any prerequisite is missing, stop and inform the user.

Running

Option 1: Full Autonomous Run (Recommended)

Dispatch the autoresearch orchestrator agent (.claude/agents/autoresearch-orchestrator.md) with context from eval/config.md, eval/napkin.md, and eval/scoreboard.md.

Pass any CLI arguments from the user (e.g., --variants=5 --generations=10).

Option 2: Single Eval Pipeline Test

VIBES_ROOT="${CLAUDE_PLUGIN_ROOT:-$(dirname "$(dirname "${CLAUDE_SKILL_DIR}")")}"
bun "$VIBES_ROOT/scripts/eval-parallel.ts" --mode=eval-only <app.jsx> <spec.md>

Option 3: Score Existing Generation

VIBES_ROOT="${CLAUDE_PLUGIN_ROOT:-$(dirname "$(dirname "${CLAUDE_SKILL_DIR}")")}"
bun "$VIBES_ROOT/scripts/eval-scoring.ts" "$VIBES_ROOT/eval/results/gen-N/"

What It Does

Each generation:

Mutate: N independent SKILL.md variants (fix-targeted, structural, adversarial, etc.)
Generate: Each variant × each prompt × 3 runs
Evaluate: Tier 1 (static) → Tier 1.5 (SSR) → Tier 2 (data model) — all programmatic
Score: Triple-run averaging with consistency penalty; fitness = mean - 0.5×stddev
Select: Best variant replaces current SKILL.md; git commit on improvement
Repeat: Until plateau (3 gens), max generations, or score oscillation

Monitoring

eval/results/gen-N/summary.json — per-generation results
eval/results/summaries.json — cumulative history
eval/scoreboard.md — human-readable scoreboard
eval/napkin.md — failure log (grows monotonically)

Final Report

VIBES_ROOT="${CLAUDE_PLUGIN_ROOT:-$(dirname "$(dirname "${CLAUDE_SKILL_DIR}")")}"
bun "$VIBES_ROOT/scripts/eval-report.ts" "$VIBES_ROOT/eval/results/summaries.json"

Other skills for the same job

different authors, same section of the catalogue

Skill Creator

by anthropics

vendor ×10

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

Replace with description of the skill and when Claude should use it.

35 tokens

Dispatching Parallel Agents

by ZhanlinCui

×5

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

Use when creating new skills, editing existing skills, or verifying skills work before deployment

26k tokens scripts

How to use it

Copy the folder

Take popmechanic/autoresearch from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.