Loading...
Loading...
Found 3,053 Skills
Operate on @spec facts — implement them in code, then tag @implemented. Use when asked to implement facts, implement the spec, build from the fact sheet, make facts true, or work through unimplemented requirements.
Validate review completeness for one task in review and finalize the Nexus decision when probe next routes validate_reviews.
Researches any project idea against live data from GitHub and Dev.to to surface what already exists, how mature the space is, and where the real opportunity lives. Use when a developer describes something they want to build and wants to know if it's been done before. Triggers on phrases like "validate my idea", "has this been built", "is this already a thing", "what exists for X", "should I build this", "is this idea original", "check if my project exists", "what are the alternatives to what I want to build", "is the market saturated for X", or any request to research the competitive landscape before starting a project.
Submit a kid-facing English content PR to the football-english repo (zxkane/football-english). Use this whenever the user asks to "submit this week's quiz", "publish a weekly quiz", "submit a daily reading", "add today's reading", "publish a daily article", "open a daily PR", "open a quiz PR", or hands over essay paragraphs (with optional KET/PET points, vocabulary, audio, image, questions) and expects them to land in the kid-facing site. The repo publishes two kinds of content — weekly quizzes (essay + 3-20 graded questions, one per ISO week) and daily readings (essay + TTS audio + image + structured KET/PET points + optional 0-3 small questions, irregular cadence). This skill picks the right shape, writes the JSON, validates it, and opens the PR end-to-end. Trigger this skill even if the user doesn't use the words "quiz", "daily", or "PR" — any handover of essay paragraphs intended for this repo qualifies.
Skill Tester
Design failing tests for complex features using Independent Evaluation — dispatches a context-free agent that sees only the requirement spec and code paths (not the implementation approach), then returns executable failing tests. Use when starting TDD for a non-trivial feature, when the requirement is ambiguous enough that biased tests are a risk, or when the user asks for independent test design.
Create animated GIFs optimized for Slack with validators for size constraints and composable animation primitives.
Code review requires technical evaluation, not emotional performance.
Analyze a batch of functional specs from a ***plain spec file to determine which pairs conflict. Replaces the pair-by-pair `analyze-2-func-specs` flow when a caller wants to check many specs at once (e.g. a new spec against every existing spec, or a freshly inserted batch against itself).
Concept prototype — validate the core idea is worth designing before writing GDDs. Run right after /brainstorm and /setup-engine. Routes to HTML, Engine, or Paper path based on game type. Produces a throwaway build and a PROCEED/PIVOT/KILL verdict.
Use when validating that a real-world problem exists before defining JTBD or writing code. Triggers on "is there demand for this?", "how do I validate this idea?", "should we build this?", or before any MVP scope decision. Combines multiple signal sources to produce a Problem Statement with confidence level.
Validate your code changes through the no-mistakes pipeline - automated code review, tests, lint, docs, push, PR, and CI - before they reach upstream. Use when the user asks to run no-mistakes, gate or ship or validate their changes, push safely, asks you to do a task and then validate it, or invokes /no-mistakes.