Loading...
Loading...
Found 2,769 Skills
Verify AI claims against source documents using the DeepCitation API
Side role: find and correct bad signals, earn leaderboard points per Publisher-approved correction (max 3/day)
Working Backwards PRFAQ challenge to forge product concepts. Use when the user requests to 'create a PRFAQ', 'work backwards', or 'run the PRFAQ challenge'.
Diff-aware AI browser testing — analyzes git changes, generates targeted test plans, and executes them via agent-browser. Reads git diff to determine what changed, maps changes to affected pages via route map, generates a test plan scoped to the diff, and runs it with pass/fail reporting. Use when testing UI changes, verifying PRs before merge, running regression checks on changed components, or validating that recent code changes don't break the user-facing experience.
Run tests against a validated RootSpec specification and report results. Use this when a user wants to run tests, check what's passing, get a test report, or verify their implementation works.
ZeroBounce integration. Manage data, records, and automate workflows. Use when the user wants to interact with ZeroBounce data.
Validates and scores Claude Code skill packages for quality, completeness, and best practices compliance. Tests Python scripts, checks YAML frontmatter, and generates quality reports. Use when creating new skills, validating skill packages, or auditing skill quality.
Create domain-specific quality checklists validating spec completeness and clarity
Guides contributors from a PM skill idea to a complete Skill Implementation Packet aligned with pm-skills conventions. Runs gap analysis, validates through a Why Gate, classifies by type and phase, generates draft files, and writes to a staging area for review before promotion.
Use when OpenSpec artifacts have been generated by /opsx:propose and need review before implementation begins — validates proposal scope, spec completeness, design decisions, and task executability
Create, refine, review, critique, or iterate on low-fidelity grey wireframes under `stardust/wireframes/**/*.html` — structure, hierarchy, section order, spatial relationships, annotations, section metadata (`data-section`/`data-intent`/`data-layout`), and multi-page fragment/reuse mapping (`data-fragment*`). Rendered from briefings. No brand required. Optional stage: users can skip to `/stardust:prototype` for branded layout directly. Use when the user wants to validate page structure before visual design, annotate a wireframe, mark reusable fragments across pages, when the user asks to change, refine, refactor, review, improve, polish, critique, or iterate on structure, section order, or block placement, or whenever the user asks to modify a file under `stardust/wireframes/**/*.html`.
Implement one task or scoped change: make the change, add valuable tests, and verify it works.