Your agent can do more. Find the skill that makes it happen.
Find your next superpower If you are an agent, refer to our llms.txt for full access.Guides Claude Code skill creation and management using Anthropic best practices. Covers skill structure, YAML frontmatter, skill-rules.json, trigger patterns, enforcement levels, hooks, session tracking, activation debugging, progressive disclosure, and the 500-line rule.
Use when deciding whether an agent skill should exist, formally evaluating routing/load/end-to-end behavior, measuring skill lift, or diagnosing an observed off-target or missed load.
Find the right skill for a capability. Load when a user or skill needs to check if a skill exists for a given task, when process-decomposer assigns skills to steps, or when agent-builder checks skill availability. Triggers on "what skill does this need", "find a skill for", "is there a skill that", "which skill handles", "does a skill exist for", "skill lookup", "check skill library". Prevents ski…
Show one skill in full — its team record or Library folder, versions, installs, health, and its eval report when it is a team skill — as Markdown boards from the terum-skills CLI. Use when the user names a skill and asks what it is, who installed it, how it scored, or what its receipt says.
Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).
Match a user request to the right skill using trigger matching, project context, and conversation history. Score ambiguity 1–10 and resolve it using context signals or a single clarifying question. Load when project-orchestrator needs to route a request, or when multiple skills could match and the right one is unclear. Also triggers on "which skill should handle this", "route this request", "I'm n…
Find the right skills for a task before acting. Use at the start of any multi-step or unfamiliar request to retrieve relevant skills by meaning, not name. Triggers when the user asks to build, set up, design, deploy, fix, or automate something and the right skill isn't obvious.
Show the state of terum-skills on this machine — team, clone, session hook, pending work, machine facts — and whether a newer CLI release exists, as Markdown boards. Use when the user asks whether terum-skills is set up, in sync or up to date, or when something about it seems off.
Design the architecture for a multi-command skill system — the shared state schema, the command map, the router, and the boundary each command stops at — before any skill files get written. Use when the user wants to turn one skill into a system, combine several related or overlapping skills into a single coherent one, build a skill with subcommands (like /thing audit, /thing polish), design a…
Use when measuring whether a skill-concierge gate-threshold change helped real skill usage or adoption — "did the new gate values help", "skill usage impact after the change", "assess skill helpfulness", "audit skill usage post-deploy", "which telemetry is valid for skill-usage analysis". Stops the reflex of using the skill-invocation-ledger or treating offer→take as usage; routes to the transcrip…
Codify the most recent successful /scrape flow into a permanent browser-skill on disk. (gstack)
Reviews and scores existing skills stored under .codex/skills. Supports requests to audit, optimize, or refactor those skills.
Skills give your agent reusable instructions for a specific job. Pick one, read what it does, and bring it into your workflow.
A name only tells half the story. Search the full description and instructions to find the right fit.
Read the skill, visit its source, and see exactly what you’re adding to your agent.
Copy the install command from a skill page and run it in your project.
npx skillycli add owner/repo --skill name