Loading...
Loading...
Found 2,726 Skills
Build, validate, and troubleshoot deep links for Codex, Cursor, VS Code, Visual Studio, and similar tools. Use when users ask for clickable links (especially in Slack) that open threads, files, folders, or app settings.
This skill should be used when the user asks to "create an agent", "make an agent", "write an agent", "build a subagent", "add an agent to a plugin", "design an autonomous agent", "generate an agent file", "write a system prompt for an agent", "what frontmatter does an agent need", "create a specialized agent". Not for skills or commands — use create-skill.
Design a new PM skill through guided conversation. Use when you have raw content or an idea and want to shape it into a compliant skill.
Enforces vendor-neutral UTM naming conventions by validating marketing links and generating a normalized, policy-compliant output.
Validate that a Dynamo deployment's NIXL/UCX/NCCL interconnect is ready for disaggregated serving over RDMA/NVLink. Use after recipe-runner brings a deployment up (especially disagg/multi-node) to confirm the KV transport is correct; use troubleshoot for diagnosing already-failed pods.
After solving a non-trivial problem, detect generalizable learnings and propose skill updates. Always active — applies to every interaction.
Design stress-test engine. Does NOT generate designs — it pressure-tests YOUR existing draft against real-world edge cases, code constraints, and failure paths. One sharp question at a time, drilling down the decision tree, using code facts to stress-test assumptions, then outputs a tight Facet Brief. NOT for: executing clear tasks, factual Q&A, or pure brainstorming (go brainstorm first, then come back with a direction). Triggers: "facet / pressure-test this plan / stress-test the design".
Verify code against paper. Use when user asks "does this match the paper", "check my implementation", or is implementing equations/algorithms from literature.
Enforces local testing before any deployment. MUST be used before running vercel, git push, or any deployment command. Prevents deploying untested code.
Manage template overrides for customizing Kata output formats. List available templates, copy defaults for local editing, edit overrides, validate template schemas. Triggers include "customize template", "override template", "edit template", "template overrides", "list templates", "show templates", "template customization", "manage templates", "what templates can I customize", "template schema", "custonmize Kata", "custom config".
Agent testing methodology - run agents with test inputs, observe outputs, iterate until outputs are accurate and well-structured.
2. Create Feature Design Document