Testing

integrated-reasoning-v2

by kimasplund

Meta-orchestrator that selects optimal reasoning patterns based on problem characteristics. Analyzes 11 dimensions and recommends ToT, BoT, SRC, HE, AR, DR, AT, RTR, or NDF patterns.

yn-be-developer-typescript

by marco-meini

Best practices, coding conventions, and patterns for backend projects using TypeScript. Use when writing code, tests, or new features in TypeScript backends with src/, Express, PostgreSQL/MongoDB, and Mocha+tsx.

customer-success-manager

by YPYT1

Use this agent when you need to optimize customer success operations for B2B enterprise clients. This agent specializes in customer health monitoring, expansion revenue identification, churn preven...

paywall-upgrade-cro

by kunhai-88

"创建或优化应用内付费墙、升级屏幕、追加销售模态框或功能门控时使用。触发词：paywall、upgrade screen、upgrade modal、upsell、feature gate、convert free to paid、freemium conversion、trial expiration screen、limit reached screen、plan upgrade prompt、in-app pricing。区别于公开定价页（见 page-cro）—本技能聚焦用户已体验价值后的应用内升级时刻。"

validating-agent-claims

by chrbailey

Epistemic verification framework for AI-generated assertions. Requires evidence before acting on LLM claims about code behavior, system state, API responses, or factual statements. Use when an AI agent makes claims that will drive decisions, before acting on research results, or when an agent asserts something is true without showing evidence.

jherr-dev-workflow

by adrianbrowning

Iterative development workflow based on "Make it work, Make it right, Make it fast" philosophy. Use when building software features, components, or systems from scratch. Guides Claude through three distinct phases - getting a working solution first, then refactoring for quality, and finally optimizing performance only when needed. Prevents premature optimization and over-engineering. Integrates seamlessly with TDD (Test-Driven Development) by mapping test phases to development phases.

pricing-strategy

by alexwelcing

Develop optimal pricing models and positioning for products/services

_workflow-data-pipeline

by TriNgo0108

Lifecycle for building data pipelines, analytics engineering, and data quality checks. Follow the phases sequentially.

aeo-spec-validator

by ivzc07

Validate that tasks are sufficiently defined before execution. Returns score 0-100.

qa

by AgustinAlbonico

"Alias corto para ejecutar pruebas E2E y QA manual. Usar cuando quieras probar la ultima funcionalidad implementada con /qa."

testing-e2e

by agdev

Expert guidance for writing resilient end-to-end tests that span multiple processes and components. Use this skill when reviewing, writing, or refactoring system-wide e2e tests. Covers user-facing scenarios, helper functions, data factories, ARIA-based selectors, and auto-retriable assertions. NOT for unit/integration tests - use testing-unit-integration skill instead. See references/playwright-resilience.md for detailed selector patterns.

IBM VPC File Pool CSI Driver — Build Skill

by neil1taylor

Do NOT skip leader election for the controller — two controllers allocating simultaneously will corrupt pool state.

ghwf2-spec

by ShotaIuchi

仕様書ドキュメントを作成

plan

by biruk741

Plan a complex coding task with adversarial review. Explores the codebase, asks clarifying questions, drafts a plan, then iterates with Codex for adversarial review against 10 quality criteria. Falls back to Claude-only if Codex unavailable. Does NOT create files — use /parallelize after.

dispatching-parallel-agents

by Cygnusfear

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

api-security-testing

by ncdevshiv

"API security testing workflow for REST and GraphQL APIs covering authentication, authorization, rate limiting, input validation, and security best practices."

assertion-helper

by Protagonistss

分析函数逻辑并生成合适的断言。

unit-test

by kyzooghost

Guidelines for writing and reviewing unit tests. Covers AAA pattern, test naming, determinism, mocking strategies, and reviewer responsibilities. Use when creating or updating .test. files, reviewing test PRs, or refactoring tests to improve clarity and coverage.

Systems Engineering Skill

by HowardKao-1130

scrum-delivery-lead

by garbray

Scrum Master & Engineering-Oriented Delivery Lead with hands-on frontend/backend development experience. Interprets Technical Design Documents, reviews UX/UI designs, and understands product requirements to ensure delivery clarity. Breaks features into well-scoped Scrum stories (max 3 story points, Fibonacci estimation). Stories are sliced for incremental value, minimal risk, fast feedback. For every ticket provides: clear description, explicit acceptance criteria, expected behavior, constraints, and test case expectations (happy path + edge cases). Ensures stories are implementation-ready, testable, aligned with technical/product goals. Enables team to execute efficiently while maintaining high quality and predictable velocity. Use when creating sprint stories, planning sprints, estimating work, or breaking down features into tickets.

Test Verification Skill

by contohmarie

For testing repository identity verification

auto-decide

by mbaranovski

'Use when facing multiple implementation options, design alternatives, or architectural choices during planning, brainstorming, or coding. Triggers: "which approach", "option A vs B", "we could either...", or any choice between implementation paths that would otherwise stall progress.'

barescript

by craigahobbs

Teaches a model how to write BareScript — language syntax, the built-in library, the include library, MarkdownUp client-rendered applications, and unit tests. Use this skill whenever the user asks you to write, read, modify, or review BareScript (.bare) code, a MarkdownUp Markdown application, a markdown-script code block, or any code that uses BareScript built-in functions (array*, object*, string*, data*, markdownPrint, elementModelRender, drawNew, etc.). Also use it when asked to write unit tests for BareScript code. Apply this skill even if the user does not say the word "BareScript" — recognize it from the .bare extension, the markdown-script fenced code block, or the function-naming style above.

Testing

by tachfineamnay

Jest unit tests, Playwright E2E tests, fixtures, and CI integration.