
scala-testing-property
majk-p/scala-skills
Use this skill when writing property-based tests or checking type class laws in Scala using ScalaCheck and discipline. Covers property definition, generators, shrinking, conditional properties, law checking (Monoid, Functor, Applicative, Monad), MUnit integration, specs2 integration, stateful testing, and test configuration. Trigger when the user mentions property testing, ScalaCheck, generators, Arbitrary, laws, discipline, forAll, shrinking, or needs to verify algebraic properties of type class instances.

scala-testing
majk-p/scala-skills
Use this skill when writing tests in Scala and choosing a testing framework. Covers specs2 (BDD-style with matchers DSL), MUnit (minimal, IDE-friendly with rich diffs), and Weaver (effect-native, Typelevel ecosystem, parallel by default). Also covers property-based testing with ScalaCheck and law checking with Discipline. Trigger when the user mentions testing, unit tests, integration tests, test framework, specs2, MUnit, Weaver, ScalaTest, ScalaCheck, discipline, assertions, matchers, test suites, or needs to write any kind of test in Scala — even if they don't explicitly name the framework.

accessibility-wcag
majiayu000/claude-skill-registry
Build accessible web applications following WCAG 2.1/2.2 guidelines with proper semantic HTML, ARIA attributes, keyboard navigation, screen reader support, and inclusive design. Use when implementing ARIA labels and roles, ensuring keyboard navigation, supporting screen readers, providing text alternatives for images, managing focus, creating accessible forms, building inclusive UI components, testing with accessibility tools, meeting WCAG compliance levels, or designing for users with disabilities.
Go coding conventions, idiomatic patterns, and CLI commands reference. Follows Effective Go and Go Code Review Comments strictly. Trigger on any Go-related question — code style, error handling, concurrency, project structure, go mod, testing, etc.

golang-how-to
mgrubb/agent-skills-golang
Golang skills orchestrator — always active on any Golang coding, review, debug, or setup task. Reads the task context and loads the most relevant skills from mgrubb/agent-skills-golang, often multiple at once: writing a gRPC service loads golang-grpc + golang-testing + golang-error-handling; debugging a panic loads golang-troubleshooting + golang-safety; auditing security loads golang-security + golang-lint + golang-safety. Also: disambiguates competing clusters when two skills seem to overlap (performance vs benchmark vs troubleshooting, samber/lo vs mo vs ro, DI cluster, safety vs security), and configures CLAUDE.md or AGENTS.md to force-trigger skills in a project (/golang-how-to configure).
Implements concurrent Go patterns using goroutines and channels, designs and builds microservices with gRPC or REST, optimizes Go application performance with pprof, and enforces idiomatic Go with generics, interfaces, and robust error handling. Use when building Go applications requiring concurrent programming, microservices architecture, or high-performance systems. Invoke for goroutines, channels, Go generics, gRPC integration, CLI tools, benchmarks, or table-driven testing.
Implements concurrent Go patterns using goroutines and channels, designs and builds microservices with gRPC or REST, optimizes Go application performance with pprof, and enforces idiomatic Go with generics, interfaces, and robust error handling. Use when building Go applications requiring concurrent programming, microservices architecture, or high-performance systems. Invoke for goroutines, channels, Go generics, gRPC integration, CLI tools, benchmarks, or table-driven testing.

strawberry-django
mamamou/ai-coding-skills
Strawberry-Django best practices — DjangoOptimizerExtension, DataLoader, type-hint-first schemas, CRUD mutations, filters/pagination/Relay, permission extensions, security hardening, async/subscriptions, and testing. Load when working with strawberry-graphql-django.

terraform-engineer
neg0diay/opencode-skills
Use when implementing infrastructure as code with Terraform across AWS, Azure, or GCP. Invoke for module development (create reusable modules, manage module versioning), state management (migrate backends, import existing resources, resolve state conflicts), provider configuration, multi-environment workflows, and infrastructure testing.

grpc-web-pentest
abelrguezr/hacktricks-skills
Pentest gRPC-Web services and endpoints. Use this skill whenever the user mentions gRPC-Web, gRPC over HTTP, protobuf services, Envoy proxies, or wants to test/audit gRPC-Web APIs. Trigger for any gRPC-Web reconnaissance, payload manipulation, CORS testing, or JavaScript bundle analysis tasks.

oauth
yafet-dev/bugbounty-codex-skills
Advanced OAuth security testing methodology for bug bounty and application security work. Use when testing or reviewing OAuth 2.0 authorization flows, redirect_uri validation, state or nonce binding, authorization code leakage, token leakage, account linking, OAuth CSRF, provider callback handling, mobile OAuth handoff, IDP/RP trust, email verification claims, token scope mismatch, OAuth SSRF, and open redirect chains leading to account takeover or data access.

stripe-cli
felipeoff/stripe-cli-skill
Stripe CLI operations for local development, webhook testing, fixture-based event simulation, API inspection, and sandbox resource management. Use when installing or verifying stripe CLI, logging in, forwarding webhook events (`stripe listen --forward-to`), triggering test events (`stripe trigger`), replaying/resending events, tailing request logs, or performing safe subscription/checkout debugging in Stripe sandbox environments.

jarvus-dbt
jarvusinnovations/agent-skills
Jarvus house conventions for writing, testing, and linting dbt projects — model layering and grain, what each stage may/may not do, the no-inner-joins and semantic-alias rules, the generic + quality-model + unit-test patterns, the sqlfluff config, and a credential-free multi-tenant CI gate. Use when building or reviewing dbt models, deciding materialization or test coverage, setting up dbt linting/CI, or when "dbt", "sqlfluff", "staging/intermediate/marts", "dbt test", or "TIDES" come up. This is the opinionated house layer ON TOP OF dbt-labs' first-party dbt skills (which cover the mechanics) — see "Relationship to other skills".

symfony-7-4-browser-kit
guillaumedelre/claude-skills
Symfony 7.4 BrowserKit component reference for simulating browser behavior in PHP. Use when writing functional tests, simulating HTTP client requests, crawling pages, clicking links, submitting forms, or working with cookies and history programmatically. Triggers on: BrowserKit, AbstractBrowser, HttpBrowser, functional testing, HTTP client simulation, crawling, CookieJar, browser history, submitForm, clickLink, jsonRequest, xmlHttpRequest.

documentation-bc-release-note-generator
fernandoartalf/al-copilot-skills-collection
Create well-structured Business Central release notes in the `docs/releasenotesmd/` folder from an approved spec, change-control note (CCN), or set of merged AL changes. Produces a single markdown release note with frontmatter (id, title, version, status, clientName, ccnNumber, issueNumber, releaseDate, releasedBy, module, createdDate, approvedDate), a fixed set of sections (Release Summary, Scope of Change, Change Request Details, Testing Setup, Testing Steps, Known Limitations, Approvals), and a sibling `*.releasenote.json` field map for downstream consumption by the `md-to-docx-converter` skill. No company, client, or publisher values are hardcoded — every identity field is either supplied by the user or read from the workspace `app.json`. Use whenever the user asks to create, draft, generate, or write a release note, RN, deployment note, change-request release document, or anything matching phrases such as "create release note", "draft release note for [client]", "generate RN from spec", "create release note for DSD-xxxx", "release note for this branch", or "prepare deployment documentation".

documentation-bc-phase-plan-generator
fernandoartalf/al-copilot-skills-collection
Create the full set of per-phase implementation plan files in the `openspec/plans/` folder from an approved Business Central technical spec, following the PLAN-PHASE template structure. For each phase listed in the spec's §8 Phase Overview, generates one `SPEC-NNN-phase-<N>-<phase-name>.plan.md` file with frontmatter (id, title, version, spec, user_story, ccn, phase, status, estimated_hours, branch, depends_on, related_docs, assignee, created_date, approved_date), and the mandatory body sections (References, Goal, Branch, Tasks as checkbox list each citing the AC it satisfies, Exit criteria, Out of scope for this phase, Notes for the AL Developer, Dependencies linking prerequisite phases and downstream consumers, Testing notes). All phases are generated in a single invocation so the developer has the full execution backlog after spec approval. Use whenever the user asks to create, draft, generate, or write phase plans, implementation plans, phase breakdown, plan files, task plans, or a development backlog for a spec, with trigger phrases such as "create phase plans for SPEC-NNN", "draft plan files", "generate the plans folder for the spec", "break SPEC-NNN into phase plans", "document the phases of [spec]", or "create plan files in openspec/plans".

blog-writer
tomstools11/blog-writer
This skill should be used when writing blog posts, articles, or long-form content in the writer's distinctive writing style. It produces authentic, opinionated content that matches the writer's voice—direct, conversational, and grounded in personal experience. The skill handles the complete workflow from research review through Notion publication. Use this skill for drafting blog posts, thought leadership pieces, or any writing meant to reflect the writer's perspective on AI, productivity, sales, marketing, or technology topics.

maestro-pipeline-test
reinamaccredy/maestro
Run a full end-to-end smoke test of all maestro CLI commands in a single session. Use this skill when testing the maestro pipeline, verifying tool installation, validating a maestro setup, or checking that all tool groups work (feature, plan, task, memory, meta, graph, handoff, search). Trigger on "test maestro", "smoke test", "pipeline test", "verify all tools", "run pipeline test", or whenever the user wants to confirm maestro is functioning correctly -- even if they just say "does it work?" in a maestro context.

fs-web-security
fernandoserra/skills
Audita una aplicación web contra el OWASP Web Security Testing Guide (WSTG) mediante revisión estática de código/configuración y checks pasivos no destructivos contra una URL. Cubre las 12 categorías del WSTG (info gathering, config, identidad, auth, autorización, sesión, input validation, error handling, criptografía, lógica de negocio, client-side, API). Usar cuando el usuario pida una auditoría de seguridad web, un análisis OWASP/WSTG, o revisar vulnerabilidades de una app/API web.

design-sprint
mikesmayer/claude-business-skills
Run a structured 5-day process to prototype, test, and validate product ideas with real users. Use when the user mentions "design sprint", "validate in a week", "rapid prototype", "test with users", "de-risk before building", "GV sprint", "prototype testing", or "design workshop". Also trigger when a team needs to make a critical product decision quickly, resolve stakeholder disagreements, or test risky ideas before investing in development. Covers mapping, sketching, deciding, prototyping, and testing. For ongoing experimentation, see lean-startup. For customer job analysis, see jobs-to-be-done.

guarding-destructive-operations
wdm0006/python-skills
Add and review preconditions on operations that delete, overwrite, rewrite history, or resolve a caller-supplied name to a filesystem path — refusing instead of warning, placing the guard ahead of the first mutation, structural classification rather than string-prefix matching, name validation plus resolved-path containment as two independent checks, why a guard on the destructive path is invisible to the dry-run, and mutation-testing each half separately. Use when writing or reviewing a `--rebuild`/`--reset`/`--purge` command, a bulk delete, a history rewrite, an `rm -rf`-shaped step, or any code that turns an argument into a file path.

self-hosted-release
appwrite/appwrite
Enforce Appwrite self-hosted release readiness checks. Use when validating a self-hosted RC or final release, running fresh Docker Compose install tests, testing realistic e2e workflows, discovering the previous stable release baseline, upgrading seeded data from the previous self-hosted release, verifying migrations, compatibility filters, release metadata, installer behavior, or deciding whether a self-hosted release is safe to publish.

testing-react
iliaal/ai-skills
Writes and reviews React/TypeScript tests using Vitest and React Testing Library. Use when "write react tests", "review tests", "check tests", "vitest", "component test", "hook test", "RTL", "testing library", "snapshot test", or testing/reviewing React components, hooks, and utilities.
**WORKFLOW SKILL** - Evaluate AI agent skills using structured benchmarks with YAML specs, fixture isolation, and pluggable validators. USE FOR: run waza, waza help, run eval, run benchmark, evaluate skill, test agent, generate eval suite, init eval, compare results, score agent, agent evaluation, skill testing, cross-model comparison. DO NOT USE FOR: improving skill frontmatter (use waza dev), creating new skills from scratch (use skill-creator), token counting or budget checks (use waza tokens). INVOKES: Copilot SDK executor, mock engine, code/regex validators. FOR SINGLE OPERATIONS: use waza run directly for a single benchmark.

sota-javascript-typescript
martinholovsky/sota-skills
State-of-the-art JavaScript and TypeScript engineering (2026) for both writing and auditing code. Covers strict TypeScript configuration and type design, language idioms and pitfalls, async patterns, Node.js backends, JS/TS-specific security (XSS, prototype pollution, supply chain, injection), frontend/React and Node performance, and testing/tooling. Use whenever building, reviewing, refactoring, or security-auditing code involving JavaScript, TypeScript, Node, npm, React, frontend code, tsconfig, package.json, vitest, or any .ts/.tsx/.js/.mjs files.

vercel-flags
openai/plugins
Vercel Flags guidance — feature flags platform with unified dashboard, Flags Explorer, gradual rollouts, A/B testing, and provider adapters. Use when implementing feature flags, experimentation, or staged rollouts.
Comprehensive guide for working with SQLModel, PostgreSQL, and SQLAlchemy in FastAPI projects. Use when working with database operations in FastAPI including: (1) Defining SQLModel models and relationships, (2) Database connection and session management, (3) CRUD operations, (4) Query patterns and filtering, (5) Database migrations with Alembic, (6) Testing with SQLite, (7) Performance optimization and connection pooling, (8) Transaction management and error handling, (9) Advanced features like cascading deletes, soft deletes, and event listeners, (10) FastAPI integration patterns. Covers both basic and advanced database patterns for production-ready FastAPI applications.

testing-coach
community-access/accessibility-agents
Accessibility testing coach for web applications. Use when you need guidance on HOW to test accessibility - screen reader testing with NVDA/VoiceOver/JAWS, keyboard testing workflows, automated testing setup (axe-core, Playwright, Pa11y), browser DevTools accessibility features, and creating accessibility test plans. Does not write product code - teaches and guides testing practices.

systematic-qa
pedronauck/skills
Executes full-project QA like a real user by discovering the repository verification contract, running build, lint, test, and startup commands, exercising core workflows end-to-end, creating realistic fixtures when needed, fixing root-cause regressions, and rerunning the full gate. Use when validating a branch, release candidate, migration, refactor, or risky commit. Do not use for static code review only, one-off unit test edits, or architecture brainstorming without execution.

react-performance
citypaul/.dotfiles
Make React and Next.js performance changes that are measured, evidence-backed, and behaviorally safe. Routes to the right rule catalogue — vercel-react-best-practices for the 72 prioritized React/Next rules, vercel-composition-patterns for component API shape, next-best-practices for App Router semantics, core-web-vitals and performance for field metrics and non-React budgets — then governs how a rule is applied here: baseline first, one hypothesis at a time, behavior tests unchanged and green, and the house functional and typing rules winning where a micro-optimization would trade them away. Use when React or Next.js feels slow, when a bundle, waterfall, re-render, or hydration problem is suspected, when reviewing a diff for performance, or when a performance rule appears to conflict with immutability, TDD, or type-safety guidance. For rendering-tier decisions and browser-observable proof see front-end-testing and react-testing; for flow logic driving the re-renders see xstate.

dev-node
manisuec/node-skills
Provides domain-specific best practices for Node.js development with JavaScript, covering async patterns, error handling, streams, modules, testing, performance, caching, logging, and more. Use when the user needs guidance on error handling, graceful shutdown, flaky tests, profiling, or environment configuration in Node.js. Helps configure package.json scripts, handle module resolution and import extensions, and apply robust patterns across the full Node.js stack.

generate-tests
inv08/scala-unit-tests-skills
Use when the user asks to generate, create, or write unit tests for Scala code. Analyzes the target code, produces a structured test case list for review, then generates test code. Supports Scala with ZIO Test (ZIOSpecDefault) and ScalaTest (AnyFunSpec), mockito-scala, and zio-mock.

playwright-skill
majiayu000/claude-skill-registry
Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions, validate web functionality, or perform any browser-based testing.

elixir-best-practices
thaddeusjiang/coding-skills
Elixir and Phoenix best practices for interactive development, debugging, testing, and routine code changes. Use when writing, reviewing, or troubleshooting Elixir application code, Mix tasks, Ecto code, or Phoenix features.

golang-pro
doyoonear/skills-and-agents
Implements concurrent Go patterns using goroutines and channels, designs and builds microservices with gRPC or REST, optimizes Go application performance with pprof, and enforces idiomatic Go with generics, interfaces, and robust error handling. Use when building Go applications requiring concurrent programming, microservices architecture, or high-performance systems. Invoke for goroutines, channels, Go generics, gRPC integration, CLI tools, benchmarks, or table-driven testing.