Skills
96,981 packaged capabilities and playbooks for agents. Install any of them with one command.
Testing & quality
Comprehensive design architecture review for Python backend applications. Use this skill when users ask you to review, analyze, or provide feedback on backend architecture designs, system design documents, or Python application architecture. Covers scalability, security, performance, database design, API design, microservices patterns, deployment architecture, and best practices.
Standalone quality review for Elastic integrations. Classifies files by domain, loads domain-specific skills and review checklists, applies cross-domain consistency rules, CEL version verification, API conformance, and severity calibration. Input-agnostic: works on local packages, PR diffs, or branch comparisons. Use when reviewing integration quality independently of any build or fix workflow.
Audit REST, GraphQL, and RPC APIs against the OWASP API Security Top 10 (2023). Use when the user mentions 'API security,' 'API audit,' 'BOLA,' 'broken object level authorization,' 'BFLA,' 'function-level authorization,' 'mass assignment,' 'API rate limiting,' 'GraphQL security,' 'REST security,' 'API authentication,' 'API authorization,' 'excessive data exposure,' or needs to review API endpoints for security weaknesses
Use when reviewing, fixing, or improving an EXISTING Elastic integration package. Covers quality reviews, targeted fixes (pipelines, field mappings, CEL programs, manifests, changelogs), full improvement passes, and minor adjustments. Use create-integration instead when creating a new package or adding a new data stream from scratch.
Analyze existing code and write comprehensive unit and integration tests for it. Detects the test framework, identifies untested code paths, and generates tests with proper mocking, edge cases, and assertions. Use when the user asks to add tests, improve coverage, or test a specific module.
Performs a lightweight pre-release readiness review of Atlassian Forge apps across manifest/module wiring, architecture, runtime compatibility, dependency posture, tests, deploy readiness, and obvious security, cost, or reliability smells. Use when the user asks "review my Forge app", "pre-deploy check", "is this app ready to ship", "review manifest", "general app review", "release readiness", or asks for a broad quality pass. Do not use for deep security audits/SAST/exploitability review, cost optimization, or diagnosing a known broken app; route those to forge-security-review, forge-cost-optimizer, or forge-debugger respectively.
Build browser automation and web scraping with Playwright on your local machine. Prevents 10 documented errors including CI timeout hangs, extension testing failures, and Ubuntu compatibility issues. Includes stealth mode for anti-bot bypass, authenticated sessions, infinite scroll handling, screenshot/PDF generation, and v1.57 Speedboard performance analysis. Use when: automating browsers, scraping protected sites, testing with real IPs, bypassing bot detection, generating screenshots/PDFs, or troubleshooting "target closed", "page.pause() hangs CI", "permission prompts block tests", or "Ubuntu 25.10 installation" errors.
Apifox API test cases: querying, creating, updating, deleting, categorizing and running test-case and test-data; handles test steps, assertions, variable extraction, pre- and post-processors, datasets, and issues such as "test steps created via the CLI do not show up in the frontend".
Methodically investigate a bug in 4 validated phases: locate/reproduce, 3 ranked root-cause hypotheses, targeted logs, minimal fix. Use on /investigue, or as soon as the user describes a symptom ("it crashes when…", "I see X but expect Y", "unexpected behavior", "why does it crash", "investigate this bug", "debug this", "analyze the bug"). Never propose an immediate fix — each phase stops and waits for explicit validation before proceeding to the next.
Move an idea up the fidelity ladder (content-first → wireframe → low-fi → high-fi → code) with a validation plan at each level, plus user-journey mapping and usability-testing scripts. Use when the user wants to prototype, wireframe, map a user flow, or plan/run usability testing
Unit testing for TypeScript/NestJS projects using Jest, @golevelup/ts-jest (DeepMocked/createMock), and in-memory databases, with AAA structure. Use whenever the user is working on `.spec.ts` files or asks to set up Jest, write/add tests for a service/usecase/controller/guard/interceptor/pipe/filter, mock dependencies, review test quality or coverage, run unit tests, debug failing or flaky tests, or optimize test performance and open handles.
Use Proxyman MCP to inspect and debug HTTP, HTTPS, and WebSocket traffic and operate the complete Proxyman MCP surface. Use for flows, API diagnosis, filtering, export, replay, Compose, debugging rules, WebSockets, recording, proxy and certificate control, code generation, or guided setup.
Provide structured code review guidance for catching defects and improving quality. Use when the user asks to "review this code", "check for issues", "PR review", "code quality check", or wants systematic code evaluation. Keywords: code review, PR, pull request, quality, defects, security, maintainability, performance.
Audit and improve SwiftUI runtime performance through code review and architecture. Use to diagnose slow rendering, janky scrolling, high CPU or memory usage, excessive view updates, or layout thrash in SwiftUI apps, and to provide guidance for user-run Instruments profiling when code review alone is insufficient.
Turn backend test ambiguity into one practical backend test packet. Use when the user needs API/service/repository/auth-flow coverage design, fixture or seed/reset strategy, container-vs-mock dependency choices, contract/API compatibility checks, or flaky backend-suite stabilization across local and CI.
Zero-context verification that every bibliographic entry in the paper is real, correctly attributed, and used in a context the cited paper actually supports — catching hallucinated authors, wrong years, fabricated venues, version mismatches, and wrong-context citations. Use when user says "审查引用", "check citations", "citation audit", "verify references", "引用核对", or before submission to ensure bibliography integrity.
Apifox import/export and quality gates: import native OpenAPI/Postman/Apifox formats and export native OpenAPI/HTML/Markdown/Postman/Apifox formats; validate spec completeness, tags grouping, and schema/body coverage before import, then verify counts, modules, and resource visibility afterward.
Use when a generated Scenario image needs a quality check or a brand-brief compliance verdict before it ships: pass/warn/fail scoring, on-brand review against a configured brief, QA gating a batch, pricing or refreshing a stored verdict, or iterating a generation until it clears the gate. Keywords: quality gate, quality check, QA, verdict, brief compliance, on-brand, brand brief, pass fail, score, review, asset_quality_gate_run.
WeChat Pay medical insurance payment (mobile medical insurance payment 2.0) integration solution, covering the full chain of medical insurance and self-pay mixed ordering, order query, medical insurance refund notification, and medical insurance payment callback, with five capabilities: solution selection, sample code, business quick reference, quality assessment, and troubleshooting. Use when the user mentions "医保支付", "移动医保支付2.0", "医保自费混合", "医保电子凭证", "医保混合收款", "医保退款通知", "医保挂号", "医保诊间支付", "医保住院结算", "医保药店购药", "互联网医院医保", "医保定点机构", or asks to "接入医保支付", "要医保下单接口示例代码", "排查医保支付问题".
Apifox CLI usage checks and version confirmation: use when commands succeed but nothing shows on the page, list/get cannot find something after creation, test runs fail, reports are missing, agentHints/help/actual behavior are inconsistent, or when you suspect the local CLI version is not the latest.
Apifox automated test execution, suites, and CI: test-suite, scheduled-task, runner, apifox run, execution parameters, iteration data, report uploads, and CI regression. For complex test-scenario step modeling, use apifox-test-scenario.
Review test code for quality, design, and completeness after implementing a feature or fixing a bug. Use when the user asks to "review my tests", "check my test quality", "are these tests good enough", "review testing", or after completing a feature implementation that includes tests. Also use when tests feel brittle, flaky, or superficial. Cross-references production code to find coverage gaps.
Apifox test scenario modeling: querying, creating, updating, deleting, and running test-scenario; importing APIs, single-API cases, or other scenario steps; adding scenario reference steps; complex step orchestration, chaining of API/condition/loop/wait/script/database steps, pre- and post-operations, variable references, assertions, extractors, and scenario debugging best practices. Use when users want to create or maintain complex automated test flows.
Use when planning, running, or learning from chaos engineering experiments. Triggers on “chaos experiment”, “fault injection”, “gameday”, “resilience test”, “blast radius”, “steady state”, “abort criteria”, “Chaos Toolkit”, “Chaos Mesh”, “Litmus”, “Gremlin”, “AWS FIS”, or any deliberate failure-injection question. Ships an experiment designer, blast-radius calculator, and postmortem generator (all stdlib Python), 4 references on chaos principles, experiment design, attack taxonomy, and tooling landscape, and a /chaos-experiment slash command. Composes with feature-flags-architect (kill switches as abort triggers) and kubernetes-operator (common chaos targets).
Run comprehensive accessibility audit (WCAG 2.1) on Webflow pages - checks buttons, forms, links, focus states, headings, keyboard navigation, and generates detailed reports with fixes. Requires Webflow Designer connection. Excludes image alt text (covered by asset-audit skill).
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.