agentleFS
PatriotAgenticLLCPatriotAgenticLLC/better_claude_skillz/skills/evolve/SKILL.md

evolve

Skill3 starsChanged 5 months agoMITView on GitHub

Cluster related instincts into skills, commands, or agents

41 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use map, refine and 3 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.
  • AWSSkill

    map

    Map verified service capabilities against customer-provided control framework and threat model. Produces mapping-results.json, controls-catalog.md, and framework-mapping.md. Supports pluggable frameworks: CCMv4, NIST 800-53, CIS Benchmarks, ISO 27001, etc. Split into 4 focused sub-skills for better accuracy; this skill orchestrates them.

    Also in 5 projects that use this

  • AlexPEClubSkill

    refine

    Always use when the user wants to discuss an exsiting feature or specification. Open an existing feature spec to improve, extend, or fundamentally challenge it. Pass the feature ID as argument (e.g. /refine PROJ-2).

    Also in 3 projects that use this

  • HeshamFSSkill

    loop

    Run a command or check on a recurring interval

    Also in 4 projects that use this

  • HK-hubSkill

    distill

    Strip designs to their essence by removing unnecessary complexity. Great design is simple, powerful, and clean. Use when the user asks to simplify, declutter, reduce noise, remove elements, or make a UI cleaner and more focused.

    Also in 3 projects that use this

  • anombyte93Skill

    discover

    Phase 1 of the prd-taskmaster pipeline: brainstorm-driven discovery. Delegates to superpowers:brainstorming in Interactive Mode (one adaptive question at a time), or self-brainstorms in Autonomous Mode when no user is present. Intercepts before the brainstorming chain hands off to writing-plans — this skill owns the exit. Extracts constraints, calibrates scale (Solo / Team / Enterprise), and advances the pipeline to GENERATE.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 36 edited versions we read keep these.

  • 7

    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:

    Run the instinct CLI using the plugin root path:

    line 10
  2. Distinctive:

    Commands: When instincts describe user-invoked actions

    line 23
  3. Distinctive:

    Skills: When instincts describe auto-triggered behaviors

    line 24
  4. Distinctive:

    Agents: When instincts describe complex, multi-step processes

    line 25
  5. Distinctive:

    When instincts describe actions a user would explicitly request:

    line 39
  6. Distinctive:

    When instincts describe behaviors that should happen automatically:

    line 52
  7. Distinctive:

    When instincts describe complex, multi-step processes that benefit from isolation:

    line 65
  8. Very specific:

    Read all instincts from ~/.claude/homunculus/instincts/

    line 80

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

Evolve Command

Implementation

Run the instinct CLI using the plugin root path:

python3 "${CLAUDE_PLUGIN_ROOT}/skills/continuous-learning-v2/scripts/instinct-cli.py" evolve [--generate]

Or if CLAUDE_PLUGIN_ROOT is not set (manual installation):

python3 ~/.claude/skills/continuous-learning-v2/scripts/instinct-cli.py evolve [--generate]

Analyzes instincts and clusters related ones into higher-level structures:

  • Commands: When instincts describe user-invoked actions
  • Skills: When instincts describe auto-triggered behaviors
  • Agents: When instincts describe complex, multi-step processes

Usage

/evolve                    # Analyze all instincts and suggest evolutions
/evolve --domain testing   # Only evolve instincts in testing domain
/evolve --dry-run          # Show what would be created without creating
/evolve --threshold 5      # Require 5+ related instincts to cluster

Evolution Rules

-> Command (User-Invoked)

When instincts describe actions a user would explicitly request:

  • Multiple instincts about "when user asks to..."
  • Instincts with triggers like "when creating a new X"
  • Instincts that follow a repeatable sequence

Example:

  • new-table-step1: "when adding a database table, create migration"
  • new-table-step2: "when adding a database table, update schema"
  • new-table-step3: "when adding a database table, regenerate types"

-> Creates: /new-table command

-> Skill (Auto-Triggered)

When instincts describe behaviors that should happen automatically:

  • Pattern-matching triggers
  • Error handling responses
  • Code style enforcement

Example:

  • prefer-functional: "when writing functions, prefer functional style"
  • use-immutable: "when modifying state, use immutable patterns"
  • avoid-classes: "when designing modules, avoid class-based design"

-> Creates: functional-patterns skill

-> Agent (Needs Depth/Isolation)

When instincts describe complex, multi-step processes that benefit from isolation:

  • Debugging workflows
  • Refactoring sequences
  • Research tasks

Example:

  • debug-step1: "when debugging, first check logs"
  • debug-step2: "when debugging, isolate the failing component"
  • debug-step3: "when debugging, create minimal reproduction"
  • debug-step4: "when debugging, verify fix with test"

-> Creates: debugger agent

What to Do

  1. Read all instincts from ~/.claude/homunculus/instincts/
  2. Group instincts by:
    • Domain similarity
    • Trigger pattern overlap
    • Action sequence relationship
  3. For each cluster of 3+ related instincts:
    • Determine evolution type (command/skill/agent)
    • Generate the appropriate file
    • Save to ~/.claude/homunculus/evolved/{commands,skills,agents}/
  4. Link evolved structure back to source instincts

Output Format

Evolve Analysis
==================

Found 3 clusters ready for evolution:

## Cluster 1: Database Migration Workflow
Instincts: new-table-migration, update-schema, regenerate-types
Type: Command
Confidence: 85% (based on 12 observations)

Would create: /new-table command
Files:
  - ~/.claude/homunculus/evolved/commands/new-table.md

## Cluster 2: Functional Code Style
Instincts: prefer-functional, use-immutable, avoid-classes, pure-functions
Type: Skill
Confidence: 78% (based on 8 observations)

Would create: functional-patterns skill
Files:
  - ~/.claude/homunculus/evolved/skills/functional-patterns.md

## Cluster 3: Debugging Process
Instincts: debug-check-logs, debug-isolate, debug-reproduce, debug-verify
Type: Agent
Confidence: 72% (based on 6 observations)

Would create: debugger agent
Files:
  - ~/.claude/homunculus/evolved/agents/debugger.md

---
Run `/evolve --execute` to create these files.

Flags

  • --execute: Actually create the evolved structures (default is preview)
  • --dry-run: Preview without creating
  • --domain <name>: Only evolve instincts in specified domain
  • --threshold <n>: Minimum instincts required to form cluster (default: 3)
  • --type <command|skill|agent>: Only create specified type

Generated File Format

Command

---
name: new-table
description: Create a new database table with migration, schema update, and type generation
command: /new-table
evolved_from:
  - new-table-migration
  - update-schema
  - regenerate-types
---

# New Table Command

[Generated content based on clustered instincts]

## Steps
1. ...
2. ...

Skill

---
name: functional-patterns
description: Enforce functional programming patterns
evolved_from:
  - prefer-functional
  - use-immutable
  - avoid-classes
---

# Functional Patterns Skill

[Generated content based on clustered instincts]

Agent

---
name: debugger
description: Systematic debugging agent
model: sonnet
evolved_from:
  - debug-check-logs
  - debug-isolate
  - debug-reproduce
---

# Debugger Agent

[Generated content based on clustered instincts]

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.