Catalog
Every x402, MPP, MCP, and skill listing we've indexed, normalized, and enriched.
stably-verify
Verify that an application works correctly using `stably verify`. Use when an AI agent has made code changes and needs to validate the feature works in a real browser. The command describes expected behavior in plain English and reports a PASS/FAIL/INCONCLUSIVE verdict — no test
stably-sdk-setup
Expert setup assistant for the Stably Playwright SDK. Use this skill when installing Stably SDK in a new project, migrating from @playwright/test, or configuring Stably reporter for CI/CD. Triggers on tasks like "setup stably", "install stably sdk", or "configure playwright with
stably-sdk-rules
AI rules for writing tests with Stably Playwright SDK. Use this skill when writing or modifying Playwright tests with Stably AI features. Covers when to use Playwright vs Stably methods, plus minimal patterns for aiAssert, extract, getLocatorsByAI, agent.act, Inbox, and Google au
playwright-test-data-isolation
Playwright-first strategy for shared DB + shared test accounts. Use when E2E tests collide in QA/staging, need safe parallelism, or require deterministic cleanup without touching baseline data. Covers per-test ownership, namespacing, ID-based teardown, serial shared-state suites,
github-actions-setup
Setup assistant for running Stably Playwright tests in GitHub Actions CI/CD. Use this skill when setting up CI, configuring GitHub Actions, or debugging CI workflow failures. Triggers on "setup github actions", "CI setup", "github actions for tests", "configure CI", "run tests in
spec-writer
Create a comprehensive Product Requirements Document from conversation and repo context. Use when the user wants a PRD, product spec, feature requirements, or similar documentation.
spec-to-plan
Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices.
slice-the-spec
Turn a PRD into a Kanban-ready backlog of vertically sliced issues, with clear dependencies and HITL/AFK flags.
script-writer
Script-writer that drafts presentations, essays, emails, and slides using only the cognitive and persuasive heuristics from Patrick Winston's "How to Speak" lecture, rejecting conventional writing advice in favor of Winston's evidence-based rules.
incremental-tdd
Test-driven development with a strict red-green-refactor loop, vertical slices, and deep modules. Use to build features or fix bugs using TDD.
grill-master
Relentlessly interview the user when they want to learn about a topic, plan, or design until you both reach a shared, testable understanding, before any planning or implementation.
git-workflow
Guided Git workflow assistant. Helps with branching strategies, writing conventional commits, opening pull requests, resolving merge conflicts, and keeping history clean. TRIGGER when the user writes /git-workflow or asks for help with Git, branches, commits, PRs, or merge confli
english-humanizer
Detects and removes AI-generated writing patterns from English text. Rewrites content to sound natural, authentic, and genuinely human.
domain-glossary
Extract a DDD-style ubiquitous language glossary from the current conversation.
deep-codebase-audit
Find deepening opportunities in a codebase, surfacing architectural friction and proposing refactors that turn shallow modules into deep ones. Use when the user wants to improve architecture, make a codebase more testable, consolidate tightly-coupled modules, or make it safer for
code-review
Performs a thorough code review of the current changes or a specified file / pull request. Covers correctness, security, performance, readability, and adherence to project conventions. Outputs prioritised, actionable feedback. TRIGGER when the user writes /code-review or asks for
risingwave
Use when working with RisingWave — streaming SQL database, materialized views, sources, sinks, CDC from PostgreSQL/MySQL, Kafka ingestion, time windows (TUMBLE/HOP/SESSION), watermarks, EMIT ON WINDOW CLOSE, port 4566, risingwave-mcp, event streaming pipeline design, real-time an
risingwave-best-practices
Use when designing RisingWave schemas, writing materialized views, configuring sources or sinks, optimizing streaming SQL performance, troubleshooting slow backfills, setting up CDC, designing time-windowed aggregations, or reviewing a RisingWave streaming pipeline
zoom-out
Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.
write-a-skill
Create new agent skills with proper structure and progressive disclosure. Use when user wants to create, write, or build a new skill, or asks "make a skill for X".
visual-validate
Validate UI changes in a real browser using Chrome DevTools or Playwright MCP. Takes screenshots, compares before/after, exercises interactions, captures console errors. Use when user asks to "visual validate", "/hb:visual-validate", "check the UI", "screenshot before/after", or
validate-code
Validate code quality: auto-fix formatting/lint, verify types, run tests. Use when user asks to "validate code", "/validate-code", "check code", or wants to validate before committing. Don't use for committing, pushing, or writing new tests.
testing
Run the test suite and report results. Use when user asks to "run tests", "/test", "/testing", "execute tests", or requests running the test suite. Don't use for writing new tests (use `tdd`), checking coverage (use `coverage`), validating lint + types + tests together (use `vali
tdd
Guides test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants test-first development, or requests TDD workflow. Don't use for writing tests after implementation, adding tests to exist