What Skills Do
A skill is a self-contained expertise module. It defines:- When to activate — patterns, keywords, and regex that match incoming messages
- What to inject — a markdown body with instructions, examples, and domain knowledge
- What tools to require — binaries, environment variables, and configuration needed
- How much context to use — a token budget cap per activation
Activation Pipeline
Skills pass through four stages before injection:Gate
Check that all prerequisites are met: required binaries exist on
PATH, required environment variables are set, required configuration is present. Skills that fail gating are skipped entirely — they never score or consume budget.Score
Each gated skill is scored against the current message using a deterministic algorithm: keyword matches, tag overlaps, and regex pattern matches. Higher scores indicate stronger relevance.Scoring is fully deterministic — no LLM involved. A skill must declare its activation criteria in the frontmatter so the scorer knows what to match.
| Field | Purpose |
|---|---|
keywords | Word or phrase matches. Exact word match scores higher than substring. |
patterns | Regex patterns. Each match adds significant weight — use for intent-specific phrases. |
tags | Short labels for broad domain matching (e.g. blockchain, cli). |
exclude_keywords | Veto list — if any appear in the message, the skill scores zero regardless of other matches. |
max_context_tokens | Token budget this skill may consume per turn. Omitting it leaves the skill with a 2000-token budget, effectively excluding it. |
Budget
Skills are sorted by score descending. Starting from the highest-scoring skill, each is selected until the
SKILLS_MAX_TOKENS budget is exhausted. Lower-scoring skills that don’t fit are dropped for this turn.Trust Levels
| Trust Level | Source | Tool Access |
|---|---|---|
| Trusted | User-placed in ~/.ironclaw/skills/ or workspace skills/ | All tools available to the agent |
| Installed | Downloaded from ClawHub registry via skill_install | Read-only tools only — no shell, no file write, no HTTP |
Skill Directories
IronClaw discovers skills from three locations, checked in order:| Directory | Trust | Description |
|---|---|---|
~/.ironclaw/skills/ | Trusted | User’s global skills, available in all sessions |
<workspace>/skills/ | Trusted | Per-workspace skills, activated in that workspace’s context |
~/.ironclaw/installed_skills/ | Installed | Registry-installed skills from ClawHub |
installed_skills/ have their tool access capped by the attenuation layer regardless of what they declare.
Each skill lives in its own subdirectory named after the skill:
Auto-Discovery
WhenSKILLS_AUTO_DISCOVER=true (the default), IronClaw scans all skill directories at startup and indexes all valid SKILL.md files. New skills added while the agent is running are picked up on the next restart.