Skills
The open registry for AI agent skills — structured prompts and workflows with recommended models, example prompts, and compatible tools.
Skills
8
Categories
9
Compatible tools
5
Contributors
1
Showing 1–8 of 8 skills
Translates requirements and user stories into behavior-driven development scenarios in Gherkin. Writes clear Given/When/Then steps, covers happy paths, edge cases, and negative cases, uses scenario outlines with examples for data-driven tests, and keeps steps declarative and reusable. Optionally scaffolds step definitions for Cucumber or Behave.
Produces structured test plans for features and releases. Defines scope and objectives, derives test cases from requirements and acceptance criteria, covers functional, edge, negative, performance, and accessibility cases, sets entry/exit criteria, and maps risk to test priority. Outputs a clear plan with a traceability matrix linking tests to requirements.
Diagnoses and fixes flaky tests by analyzing test code and CI failure history for common sources of nondeterminism such as time and timezone dependence, order dependence, shared mutable state, race conditions, and unmocked network calls. Proposes targeted fixes and quarantine strategies to keep the suite trustworthy.
Writes end-to-end UI tests with Playwright or Cypress that mirror real user journeys. Covers resilient selectors (roles/test-ids), network stubbing, auth setup, fixtures, waiting strategies that avoid flakiness, visual and accessibility assertions, and CI integration. Produces maintainable specs and a page-object structure.
Generates mock API servers and stubbed responses from OpenAPI specs, sample payloads, or natural-language descriptions. Produces realistic fixture data, configurable latency and error scenarios, and ready-to-run mock servers using tools like Prism, MSW, WireMock, or json-server so frontend and integration tests can proceed without the real backend.
Generates comprehensive load testing scripts and configurations for APIs. Supports k6, Locust, Artillery, and JMeter formats. Creates realistic traffic patterns, ramp-up scenarios, and threshold definitions. Includes analysis templates for identifying bottlenecks and capacity planning.
Generates comprehensive unit tests for existing code, covering happy paths, edge cases, error conditions, and boundary values. Follows testing best practices including the test pyramid, DAMP over DRY, and the Arrange-Act-Assert pattern. Adapts to the project's existing test framework and conventions.
Reviews web interfaces for WCAG 2.1 AA compliance. Identifies accessibility barriers including missing ARIA attributes, keyboard navigation issues, color contrast problems, and screen reader incompatibilities. Provides remediation code with proper semantic HTML.
Skills vs MCP servers
what's the difference?Skillsthe “what to do”
A skillA reusable, structured prompt/workflow with recommended models, an example prompt, and compatible tools. packages know-how — instructions, an example promptA ready-to-use prompt template that demonstrates how to invoke the skill., and recommended models — so an agent performs a task consistently. Skills add knowledge, not new connections.
MCP serversthe “how to connect”
An MCP serverModel Context Protocol server — a standard way to expose tools, resources, and prompts to AI agents and IDEs. gives an agent new capabilities by connecting it to real systems (databases, APIs, files) over a transportHow the client talks to the server: stdio (local process), SSE, or HTTP streaming.. MCP adds connections and actions, not task instructions.
Rule of thumb: reach for a skill when you need the model to do a task well, and an MCP server when you need it to reach a tool or system. They compose — a skill can rely on tools an MCP server provides.
Built a useful skill?
Submit a SKILL.md — it's open source and community-maintained.