From hyperagents
Apply HyperAgents' self-referential improvement pattern to any code artifact. Triggers when Claude is asked to 'improve', 'optimize', 'evolve', or 'self-improve' code, agents, skills, or prompts. Also triggers on repeated failures as an automatic recovery strategy.
How this skill is triggered — by the user, by Claude, or both
Slash command
/hyperagents:self-improveThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill implements the core insight from Meta's HyperAgents paper: **agents can improve themselves by treating their own code/prompts as mutable targets, evaluating changes with fitness functions, and selecting the best mutations across generations.**
This skill implements the core insight from Meta's HyperAgents paper: agents can improve themselves by treating their own code/prompts as mutable targets, evaluating changes with fitness functions, and selecting the best mutations across generations.
/hyperagents:evolve┌─────────────────────────────────────────────┐
│ GENERATE LOOP │
│ │
│ 1. SELECT PARENT (from archive) │
│ │ │
│ 2. MUTATE (meta-agent modifies code) │
│ │ │
│ 3. EVALUATE (fitness scoring) │
│ │ │
│ 4. ARCHIVE (store generation + score) │
│ │ │
│ 5. SELECT NEXT PARENT (fitness-weighted) │
│ │ │
│ └──────── repeat ────────────┘ │
└─────────────────────────────────────────────┘
Unlike traditional agent frameworks where the orchestrator is fixed, HyperAgents allows the meta-agent to modify:
Changes are not accepted blindly. Every mutation is evaluated:
All generations are kept in an append-only archive:
All changes are made in isolation:
When asked to self-improve a target:
1. Create .hyperagents/ directory if not exists
2. Define fitness function for the target
3. Store initial version as gen_initial
4. For N generations:
a. Select parent from archive
b. Create git worktree
c. Dispatch meta-agent to modify target in worktree
d. Capture diff
e. Run fitness evaluation
f. Store results in archive
g. Clean up worktree
5. Apply best generation's changes
npx claudepluginhub zpankz/hyperagents-pluginGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Implements work from a spec or tickets using TDD at agreed seams, with regular typechecking and test runs, followed by code review.