Loading...
Loading...
Found 6,566 Skills
Apply the canonical GitHub issue and pull-request label set to a repository.
La puerta de entrada del kit — de un clon recién bajado a un cerrador andando, local o en Railway.
Abre el simulador de chat en la terminal y corre el caso contra el cerrador, sin credenciales.
In chat-only mode, reply like a chat assistant without changing the current code base.
Помогает совместно прояснить задачу, проверить идею, найти корневую причину проблемы или выбрать подход без реализации. Используй, когда пользователь просит обсудить задачу, разобраться в проблеме, сравнить варианты или задаёт вопросы «что думаешь?» и «как лучше сделать?». Не используй, когда пользователь явно просит составить план, реализовать задачу, проверить изменения кода или сохранить знания проекта.
Interview-driven flow picker. Use when the user is unsure which skill/flow/pipeline fits — new project kickoff, cross-domain work, or a fuzzy situation. Reads the three routers live and recommends ONE flow. Not for tasks whose owner is already obvious.
Case Radar. Given a new thing (new tool/new concept/new ecosystem), scan the ecosystem to find interesting real-world cases, focusing on capturing "authentic assets" (screenshots/source code/demos) instead of GitHub homepage, and output a browsable HTML case collection. Triggered when users say "See what people are doing with X", "Scan the X ecosystem", "What new ways are there to use X in the market", "Show me authentic cases of X", or "/case-radar". Not suitable for: ① In-depth research with clear objectives (use long-research) ② Writing articles/creating PRDs (use writing-assistant / prd-doc-writer) ③ Pure knowledge-seeking without needing HTML (just ask directly).
Autonomous execution workflow for complex long-running tasks. This applies to scenarios where users have a complex or vague task (e.g., "Help me figure out X / Help me evaluate Y / Help me organize this pile of stuff / Help me compare N solutions / Help me run a research"), and expect the AI to decompose, execute, and verify the task on its own, only reaching out to the user at critical moments. It enables unattended autonomous execution for 1-2 hours through the process of "Task Confirmation → Task Queue → Batch Execution → Periodic Queue Verification → Triggered Reporting". It is triggered when users say phrases like "Help me figure out / Evaluate / Organize / Compare / Run a research / Run it on your own don't bother me / Long-running task / Run autonomously". **Not applicable to**: UI design (use design-exploration), to-do priority judgment (use priority-judge), article writing (use writing-assistant), backlog management (use backlog-manager), vision exploration (use vision-exploration), naming (use product-naming), implementation coding tasks with clear specs (code directly).
Converge vague requirements into a goal contract (scope / non-goals / success criteria / verification / stop conditions) that another AI can execute autonomously and be accepted. This skill only writes goal contracts, **never executes tasks for users**. Hard trigger condition: This goal is to be handed over to others for execution — subagent, Codex, another AI session, or another person. It is used to write goals, optimize goals, revise handoff prompts, or turn requests like "finish today, optimize as much as possible, help me research and execute" into task contracts that the executor won't guess randomly or overstep boundaries. Not applicable to: internal team requirement management and version breakdown (use issue-pool — it produces tasks for humans to start working on, not contracts for AI), interface design exploration (use design-exploration), PRD/acceptance criteria/test case documents (use prd-test-writer), framework planning and version roadmaps (use issue-pool), and situations where the user actually wants you to **do the task directly** — just do it directly instead of using this skill to turn the task into a document.
Coordinate OMP subagents on substantial work. Use when parallel discovery, specialist review, or clearly partitioned implementation will shorten or strengthen the result; skip trivial tasks.
Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.
Know a company completely. Opens by asking your goal and where your context lives (CRM? call recorder? team chat? email?), then routes to 4 modes - account deep-dive & plan (external + your internal history with them), org chart (who runs it), tech stack & wedge, competitive battlecard. Use for "tell me about <company>", "account plan for <company>", "org chart for <company>", "what's their tech stack", "battlecard for <competitor>", "how do we beat <X>", "research this account".