skill-lookup
Uses MCP tools to browse the prompts.chat skill catalog and retrieve or install Agent Skills. Supports extending Claude with reusable agent capabilities.
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.Uses MCP tools to browse the prompts.chat skill catalog and retrieve or install Agent Skills. Supports extending Claude with reusable agent capabilities.
Improves skill instructions, examples, activation, and cross-model reliability while reducing context cost. Supports diagnosing weak uptake, preventing regressions, and defining benchmarks and release gates for skill packs.
Guides decisions about placing content in SKILL.md versus reference files when creating or refactoring skills. Addresses oversized skill files, bundling, context efficiency, and distinctions between content organization and triggering problems.
Audits skills against best practices to assess quality and identify improvements. Covers skill structure, workflow design, description effectiveness, token use, and validation.
Reviews skill quality with evidence-based design rubrics and read-only batch inventories. Use for self-review, external skill or repository audits, and authorized auto-PR improvements. Separates design quality from measured task benefit and host compatibility.
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…
Assesses agent skill safety, including reviews before installation and SKILL.md validation. Checks for prompt injection, malicious scripts, excessive permissions, secret exposure, and supply chain risks.
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.
Combines deterministic scanning with intent analysis to assess local folders, skill archives, and repositories. Detects prompt injection, credential theft, persistence, memory poisoning, malicious code, supply chain risks, and discrepancies between descriptions and behavior.
Creates new Claude skills and shares them automatically on Slack using Rube. Supports team collaboration and skill discovery.
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…
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