How do I install the Evolve skill?

Run npx skillmds@latest add adelaidasofia/evolve in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Evolve safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Evolve?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Evolve free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Evolve?

adelaidasofia (@adelaidasofia) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Evolve by adelaidasofia — Agent Skill

Name: Evolve
Rating: 4.2 (5 reviews)
Author: adelaidasofia

Evolve

Use when many related hardened instincts (high-confidence feedback_*/discovery_* memories) have piled up in one domain, when the user runs /evolve or asks to promote, cluster, graduate, or consolidate accumulated instincts into a Command, Skill, or Agent, or when files in Instinct Proposals need review. Part of the Instinct Engine. Not for one-off pattern capture (use patterns), daily journaling, or sharing instinct packs (use instinct-export / instinct-import).

adelaidasofia Updated Sep 10, 2026

File contents

/evolve — promote a cluster of instincts into a structure

{SKILL_DIR} = this skill's own folder (locally: the directory this SKILL.md lives in; a served brain substitutes the real absolute path before you read this). Shared starter files live at the repo root two levels up: {SKILL_DIR}/../... If a path does not resolve, name the missing file and stop — never guess another location.

When many related, high-confidence instincts pile up in one domain, that is a signal to promote them into ONE reusable structure instead of leaving them as loose memories. /evolve finds those clusters deterministically and drafts a proposal you refine.

ECC source pattern: "/evolve clusters related instincts into higher-level structures: Commands / Skills / Agents." Reimplemented clean per license-hygiene.

Step 1 — run the clusterer (deterministic, zero LLM cost)

python3 "{SKILL_DIR}/../../scripts/instinct.py" evolve

It groups every instinct by inferred domain, computes each cluster's median effective confidence, and for clusters that clear the propose bar (>= 2 instincts AND median confidence >= 0.80) writes a scaffold to <vault>/⚙️ Meta/Instinct Proposals/proposed-skill-<domain>.md. Clusters below the bar print as watch (not yet ripe).

Step 2 — judge each PROPOSE cluster

For each proposal the script wrote, decide the structure:

Command — the cluster is ONE repeatable procedure with a clear trigger.
Skill — the cluster is a coherent body of domain guidance (most common).
Agent — the cluster describes an autonomous multi-step workflow.

A cluster that is really just 2-3 facets of an existing rule should be CONSOLIDATED into that rule, not promoted. Reject those.

Step 3 — draft (only on confirm)

For an accepted cluster, draft the real skill/command body from the member instincts (keep each instinct's Action + Evidence). Place it in the right repo per the install rules, wire its discoverability + automation + verification in the SAME session (the three-layer wiring rule), then retire or link the source memories. Delete the proposal file once adopted or rejected — proposals are scratch, not a backlog.

Headless/auto mode

In a cron/--print session: run Step 1, report the PROPOSE clusters and the proposal paths, and STOP. Promotion to a real skill is a judgment call that needs a human — never auto-create skills.

---name: evolvedescription: Use when many related hardened instincts (high-confidence feedback_*/discovery_* memories) have piled up in one domain, when the user runs /evolve or asks to promote, cluster, graduate, or consolidate accumulated instincts into a Command, Skill, or Agent, or when files in Instinct Proposals need review. Part of the Instinct Engine. Not for one-off pattern capture (use patterns), daily journaling, or sharing instinct packs (use instinct-export / instinct-import).---# /evolve — promote a cluster of instincts into a structure> **`{SKILL_DIR}`** = this skill's own folder (locally: the directory this SKILL.md lives in; a served brain substitutes the real absolute path before you read this). Shared starter files live at the repo root two levels up: `{SKILL_DIR}/../..`. If a path does not resolve, name the missing file and stop — never guess another location.When many related, high-confidence instincts pile up in one domain, that is asignal to promote them into ONE reusable structure instead of leaving them asloose memories. `/evolve` finds those clusters deterministically and drafts aproposal you refine.ECC source pattern: "/evolve clusters related instincts into higher-levelstructures: Commands / Skills / Agents." Reimplemented clean per license-hygiene.## Step 1 — run the clusterer (deterministic, zero LLM cost)```bashpython3 "{SKILL_DIR}/../../scripts/instinct.py" evolve```It groups every instinct by inferred `domain`, computes each cluster's medianeffective confidence, and for clusters that clear the propose bar(>= 2 instincts AND median confidence >= 0.80) writes a scaffold to`<vault>/⚙️ Meta/Instinct Proposals/proposed-skill-<domain>.md`. Clusters belowthe bar print as `watch` (not yet ripe).## Step 2 — judge each PROPOSE clusterFor each proposal the script wrote, decide the structure:- **Command** — the cluster is ONE repeatable procedure with a clear trigger.- **Skill** — the cluster is a coherent body of domain guidance (most common).- **Agent** — the cluster describes an autonomous multi-step workflow.A cluster that is really just 2-3 facets of an existing rule should beCONSOLIDATED into that rule, not promoted. Reject those.## Step 3 — draft (only on confirm)For an accepted cluster, draft the real skill/command body from the memberinstincts (keep each instinct's Action + Evidence). Place it in the right repoper the install rules, wire its discoverability + automation + verification inthe SAME session (the three-layer wiring rule), then retire or link the sourcememories. Delete the proposal file once adopted or rejected — proposals arescratch, not a backlog.## Headless/auto modeIn a cron/`--print` session: run Step 1, report the PROPOSE clusters and theproposal paths, and STOP. Promotion to a real skill is a judgment call thatneeds a human — never auto-create skills.

Frequently asked questions