auto-skill

Auto-Skill

Detect when a workflow you just completed is reusable enough to become a skill, then generate a SKILL.md for it. Works in two modes: automatic detection during reflection, or explicit creation when the user asks.

Usage

/auto-skill                      -- detect skill candidates from recent session
/auto-skill <name>               -- create a skill from a specific recent procedure
"make this a skill"              -- explicit trigger (H3), works even if autoSkill.enabled is false

How It Works

Mode A: Automatic Detection (During Reflection)

This runs during the homaruscc event loop reflection step 4, after a local/howto/* memory has been stored.

Step 1: Check Config

Read ~/.homaruscc/config.json. If autoSkill.enabled is not true, skip detection entirely. If the key is missing or false, stop here and continue the event loop normally.

Step 2: Run Detection Heuristics

Evaluate each heuristic independently. Any single match is sufficient to flag a candidate.

H1 -- Complexity Threshold (R500): Count the tool calls from the current workflow. If 5 or more tool calls were made toward a single goal, this is a candidate.

H2 -- Recurrence Signal (R501): Search memory for existing howtos with keywords from the new howto:

memory_search: query="<keywords from new howto>" filter="local/howto/*"

If 2 or more existing local/howto/* entries match, this is a candidate.

H4 -- Reflection Similarity (R503): Search memory using the full text of the new howto:

memory_search: query="<full howto text>"

If the top result has >0.7 similarity score AND is a different memory key, this is a candidate.

Note: H3 (explicit request) is handled by Mode B below, not here.

Step 3: Evaluate Results

If no heuristic matched, continue the event loop -- no candidate.