Testing
Unit tests, integration tests, test automation
fastmcp-python-tests
by Jamie-BitFlight
Write and evaluate effective Python tests using pytest. Use when writing tests, reviewing test code, debugging test failures, or improving test coverage. Covers test design, fixtures, parameterization, mocking, and async testing.
validation-protocol
by Jamie-BitFlight
Scientific validation protocol for verifying fixes work through observation, not assumption. Use when claiming a bug fix, code change, or implementation is complete. Enforces create-broken-state — define-success-criteria — apply-fix — verify-outcome workflow. Success equals observing intended behavior, not absence of errors.
create-artifact
by Jamie-BitFlight
Register a plan artifact via the MCP backlog server. Use when you produce a document or report that downstream agents or worktree-isolated environments need to retrieve — feature-context, codebase-analysis, architect, T0-baseline, TN-verification, or research artifacts. Triggers include "store an artifact", "register a plan artifact", "write a report to the backlog", "upload artifact content".
test-engineer
by nahisaho
test-engineer skill Trigger terms: testing, unit tests, integration tests, E2E tests, test cases, test coverage, test automation, test plan, test design, TDD, test-first Use when: User requests involve test engineer tasks.
constitution-enforcer
by nahisaho
Validates compliance with 9 Constitutional Articles and Phase -1 Gates before implementation. Trigger terms: constitution, governance, compliance, validation, constitutional compliance, Phase -1 Gates, simplicity gate, anti-abstraction gate, test-first, library-first, EARS compliance, governance validation, constitutional audit, compliance check, gate validation. Enforces all 9 Constitutional Articles with automated validation: - Article I: Library-First Principle - Article II: CLI Interface Mandate - Article III: Test-First Imperative - Article IV: EARS Requirements Format - Article V: Traceability Mandate - Article VI: Project Memory - Article VII: Simplicity Gate - Article VIII: Anti-Abstraction Gate - Article IX: Integration-First Testing Runs Phase -1 Gates before any implementation begins. Use when: validating project governance, checking constitutional compliance, or enforcing quality gates before implementation.
auth-system-setup
by TerminalSkills
When the user wants to set up authentication and authorization for a web application. Use when the user mentions "auth," "login," "OAuth," "SSO," "single sign-on," "role-based access," "RBAC," "permissions," "user roles," "access control," "authentication," or "authorization." Covers OAuth 2.0 provider integration, session management, and role/permission architecture. For JWT-specific tasks, see jwt-handler. For security review, see security-audit.
business-model-auditor
by shipshitdev
Use this skill when users need to stress test their business model, identify scale limitations, find bottlenecks, determine if they're trading time for money, or evaluate unit economics. Activates for "can this scale," "what breaks at 10x," or business model viability questions.
cofounder-evaluator
by shipshitdev
Use this skill when users need to evaluate potential co-founders, assess founder compatibility, design equity splits, or navigate co-founder relationships. Activates for "should I work with this person," "co-founder fit," "equity split," or founding team questions.
channel-validator
by shipshitdev
Use this skill when users need to validate their marketing channel strategy, assess channel focus, or determine lead gen priorities. Activates for "validate my channels," "am I on the right platforms," "should I focus on X or Y channel," or when assessing marketing spread.
fundraise-advisor
by shipshitdev
Use this skill when users need to raise funding, create a pitch deck, prepare for investor meetings, understand fundraising process, or navigate seed/pre-seed rounds. Activates for "how do I raise money," "pitch deck," "investors," or fundraising questions.
system-architect
by aj-geddes
Designs system architecture, selects tech stacks, defines components and interfaces, addresses non-functional requirements. Trigger words - architecture, system design, tech stack, components, scalability, security, API design, data model, NFR, patterns, microservices, monolith
interview-me
by mycelium-hq
Use when an ask is underspecified ("build me X" without who it's for, why now, or what success looks like), when a request is conventional rather than specific ("a dashboard", "make it faster" with no number), when Claude catches itself silently filling in ambiguous requirements before any plan, spec, or code exists, or when the user says "interview me", "grill me", "are we sure?", or "stress-test my thinking". Needs a live user; not for CI, scheduled runs, or autonomous loops.
doubt-driven-development
by mycelium-hq
'Use when correctness matters more than speed: about to commit non-trivial code, make an architectural call under uncertainty, work in unfamiliar code, or assert what the compiler cannot check (''this is safe'', ''thread-safe'', ''this scales'', ''matches the spec''). Strongest on high-stakes surfaces (production deploys, security-sensitive logic, data migrations, irreversible operations) and when the user asks to sanity-check, red-team, double-check, or get a second opinion on a decision.'
code-review
by iliaal
Performs two-stage code reviews (spec compliance, then code quality) with severity-ranked findings. Use when asked to "review code", "review this PR", "check this diff", "review before merge", or mentions reviewing, auditing, or critiquing code changes, pull requests, or diffs.
mpm-organize
by bobmatnyc
Organize project files with intelligent consolidation
Condition-Based Waiting
by bobmatnyc
Replace arbitrary timeouts with condition polling for reliable async tests
Dispatching Parallel Agents
by bobmatnyc
Use multiple Claude agents to investigate and fix independent problems concurrently
prep-meeting
by bobmatnyc
Prepares for meetings by gathering context about attendees, topics, and relevant data across connected tools. Produces an agenda with talking points, supporting data, and anticipated questions.
Root Cause Tracing
by bobmatnyc
Systematically trace bugs backward through call stack to find original trigger
rust-desktop-applications
by bobmatnyc
Build cross-platform desktop applications with Rust using Tauri framework and native GUI alternatives
Testing Anti-Patterns
by bobmatnyc
Never test mock behavior. Never add test-only methods to production classes. Understand dependencies before mocking.
slack-messaging
by obra
Use when asked to send or read Slack messages, check Slack channels, test Slack integrations, or interact with a Slack workspace from the command line.
esphome-devices
by tonylofgren
Use when user EXPLICITLY requests "ESPHome", "ESP32", "ESP8266", or device firmware. NOT for: Home automations (use home-assistant or node-red skill).
ha-integration-dev
by tonylofgren
Use when user EXPLICITLY requests "custom integration", "custom component", "Python for HA", "HACS", or "config_flow". NOT for: YAML automations (use home-assistant skill), Node-RED flows (use node-red skill), ESPHome device configs (use esphome skill).