Skills
100,928 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Use when picking a software architecture style or pattern for a system — phrases like "what architecture should we use", "monolith vs microservices", "should we go event-driven", "is this a CQRS situation", "do we need a saga here", "should we use hexagonal architecture", "what's the right architectural style for this problem". Diagnostic mode that routes a stated problem to the relevant architecture skill or rules patterns out.
Use when discussing layered architecture (n-tier) — phrases like "layered architecture", "n-tier", "presentation / business / persistence layers", "should we go layered", "leaky layer", "sinkhole anti-pattern", "open vs closed layers". Defines the layered style with its strict top-down dependency rule, the open/closed layer concept, and the most common failure modes.
Use when designing or reviewing a microservices architecture — phrases like "microservices", "should we split this service", "service boundaries", "bounded context per service", "API gateway", "backend for frontend", "BFF", "service mesh", "microservices vs monolith", "database per service", "data ownership". Defines microservices as independently deployable services aligned with business capabilities — and the discipline of resisting the style until the monolith proves inadequate.
Use when migrating a legacy system incrementally — phrases like "strangler fig", "strangler pattern", "incremental migration", "monolith to microservices", "rewrite without big bang", "replace legacy in place", "facade in front of the legacy system", "anticorruption layer". Defines Fowler's Strangler Fig as the migration discipline of gradually replacing legacy functionality behind a stable facade, never doing a big-bang rewrite.
MySQL and MariaDB specifics for Atlas: dev database and URL scope (schema vs server), character sets and collations, users, roles and grants, enum and set columns, generated columns, foreign-key indexes, functional and prefix indexes, triggers and stored programs, table copies and MY lint checks, partial migration failures (no transactional DDL), GET_LOCK, managed services (RDS, Aurora, Cloud SQL, Azure), schema and migration tests, and custom lint rules. Use with the atlas skill whenever Atlas manages a MySQL or MariaDB database
Guided onboarding of a repository onto Atlas, one verified stage at a time: plan the units and the workflow, define the schema as code, set up the migration workflow, add CI with the Atlas Registry, deploy to staging, and promote to production. Each stage ends on a check the agent runs itself, such as a dry run with no changes or a deployment recorded in Atlas Cloud. Use when the user asks to onboard, adopt, or set up Atlas for a project or a team, or to resume an onboarding
Ranks where code complexity concentrates in a git repository (cyclomatic complexity, nesting, fan-out, mutable state) and scores CRAP change risk from a coverage file. Read-only. Use when the user says "find complexity hotspots", or when asked for complexity hotspots or change risk. Not for test value; use auditing-tests.
Audit PHP web application source for critical vulnerabilities using PHP's specific sink and footgun catalog — object injection via unserialize and phar:// POP chains, type-juggling and magic-hash auth bypass, LFI/RFI through php:// and phar:// wrappers, dynamic includes and extract()/superglobal trust, SQL injection in string-built and legacy mysql_* queries, command-execution sinks, and SSRF. Use when reviewing a PHP codebase, a WordPress/Magento/Laravel app, or a plugin for exploitable bugs. Defers general audit methodology to auditing-code-for-vulnerabilities.
Use when adding DPoP (Demonstrating Proof-of-Possession) token binding to protect API calls with device-bound, sender-constrained access tokens that cannot be replayed if stolen. Also use when a user says "bind tokens to the client", "prevent token theft", or "sender-constrained tokens".
Use when the work spans several files or replaces a framework, language, auth, storage, or API layer (rewrites and migrations included), and the user wants it to end up working and tested. Asks only what is missing, writes a spec with acceptance criteria, then runs and verifies it in the background. Not for questions, small edits, or an existing Seed (use run)
Unified entry skill for awiki-cli, providing agent identity and IM capabilities, including direct messaging, group chat, and attachment send/receive; future support for end-to-end encrypted communication, and responsible for routing related tasks, minimal loading, safety rules, and confirmation rules.
Use when researching, compiling, or assessing best practices for any AWS service, building HA/DR/security checklists from official AWS documentation, or checking whether live AWS resources follow official recommendations. Requires aws-knowledge-mcp-server. Triggers on "best practices", "compile checklist", "summarize HA/DR best practices", "what are the best practices for", "find all best practices", "check my cluster", "audit my redis", "assess my redis", "assessment", "是否符合最佳实践", "检查现有资源", "查找最佳实践", "编译检查清单", "总结最佳实践", "帮我查找", "汇总成表", "帮我检查", "审计一下", "评估一下".
Provides AWS CloudFormation patterns for Lambda functions, layers, API Gateway integration, event sources, cold start optimization, monitoring, logging, template validation, and deployment workflows. Use when creating Lambda functions with CloudFormation, configuring event sources, implementing cold start optimization, managing layers, integrating with API Gateway, and deploying Lambda infrastructure.
Provides AWS CloudFormation patterns for Amazon S3. Use when creating S3 buckets, policies, versioning, lifecycle rules, and implementing template structure with Parameters, Outputs, Mappings, Conditions, and cross-stack references.
Expert knowledge for Azure AI Face development including troubleshooting, best practices, decision making, limits & quotas, security, and integrations & coding patterns. Use when using Face detection, identification, verification, liveness, PersonGroup/Directory, or Face API quotas, and other Azure AI Face related development tasks. Not for Azure AI Vision (use azure-ai-vision), Azure AI Custom Vision (use azure-custom-vision), Azure AI Video Indexer (use azure-video-indexer), Azure AI Document Intelligence (use azure-document-intelligence).
Diagnose the single B2B sales constraint currently limiting pipeline or revenue and route to the right repair workflow. Use when sales feels stuck, pipeline is weak, leads ghost, outbound is not working, conversion is unclear, or the team is debating whether to fix reach, messaging, follow-up timing, or trust.
Comprehensive backend development guide for Node.js/Express/TypeScript microservices. Use when creating routes, controllers, services, repositories, middleware, or working with Express APIs, Prisma database access, Sentry error tracking, Zod validation, unifiedConfig, dependency injection, or async patterns. Covers layered architecture (routes → controllers → services → repositories), BaseController pattern, error handling, performance monitoring, testing strategies, and migration from legacy patterns.
Feed what a finished cycle taught back through the sources that produced it: measure the lesson, question the requirements it touches, land it in one owner, refresh that owner to a clean v0, cut its padding and realign its listings, each pass only when it applies. Use after a correction, a request the user had to repeat, a failed or disappointing cycle, or a cleanup pass over a repository's docs, rules or skills, when the lesson has to change the sources rather than sit in a memo.
Reference for all Bitwarden workflow linter (bwwl) rules. Covers all 10 linter rules split into two categories: mechanical rules that can be applied automatically (name_capitalized, permissions_exist, pinned_job_runner, step_pinned, underscore_outputs, job_environment_prefix, check_pr_target) and judgment rules requiring user input (name_exists, step_approved, run_actionlint). Use the workflow-audit skill to run the linter and report findings, and the workflow-fix skill to apply fixes. <example> User: What does the step_pinned rule check for? Action: Consult this skill for the rule definition and fix procedure </example> <example> User: How do I fix a permissions_exist finding? Action: Consult this skill for the fix procedure </example>
Get the team's Requirements-level backlog (Product Backlog Items and Bugs) filtered to Active items assigned to the current user. Shows parent/child hierarchy and sorts by priority. Use this skill when the user wants to see their backlog items, sprint assignments, or work they own on a team board.
Author production-grade prompts for Bolna outbound and inbound voice agents (Hindi/English/Hinglish), and diagnose-and-fix existing prompts from call transcripts. Use this skill whenever the user describes a calling-bot or voice-agent use case (e.g. lead qualification, recruitment screening, appointment booking, onboarding calls, renewal/collection calls, NPS, surveys), pastes a Bolna or voice-agent transcript and asks for improvements, asks for an Indian-language calling script, or mentions Bolna, GPT-4.1 mini voice agents, IVR scripts, telecaller bots, or similar — even if they do not name "Bolna" explicitly. This skill produces output in a very specific structure (numbered sections, Hindi-first/English-second scripted lines, paragraph-prose instructions, YAML FAQs, JSON context blocks) and that structure is non-negotiable, so always consult this skill before drafting any voice-agent prompt.
Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
Content planning engine: Give it a business goal to produce a full content plan; a person reviews only one seed sheet, and the rest is derived mechanically. Covers FB, IG, short videos (TikTok / Reels), and 小红书, for Malaysian Chinese small-business owners. Five entry points: plan a content run ("帮我规划这个月的内容", "这一档要发几支", "我该发什么内容", "plan my content"); diagnose without planning first ("我的内容为什么没人看"); collect customers' exact words in the materials library ("我捞到几条客人的话", "客人讲了一句"); log results ("记一下成绩", "这篇的数据"); review ("复盘一下", "这几周跑得怎样"). Not for: writing a single post (that does not need the whole pipeline; just write it); paid-ad creative testing (this engine handles only organic content, with entirely different allocation logic); brand strategy itself (the engine consumes brand strategy outputs, not produces brand strategy).
Manage and operate BrowserWing — an intelligent browser automation platform. Install dependencies, configure LLM, create/manage/execute automation scripts, use AI-driven exploration to generate scripts, browse the script marketplace, and troubleshoot issues.
Ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman.
Retrieve Coinbase Design System (CDS) documentation: setup, installation, theming, tokens, and per-component APIs/examples. Use this skill whenever the task involves CDS components, design-system rules, theming, or choosing between web and mobile CDS packages, even if the user only says "use CDS" or names a component. Always start from the docs route index, then fetch only the pages you need to reason and implement correctly. Prefer the CDS MCP server (`list-cds-routes`, `get-cds-doc`); if MCP is unavailable, use curl against https://cds.coinbase.com/llms/....
The 20 principles of UX and animation, extended with Emil Kowalski's animation rules, Interface Craft's motion techniques and more laws of UX, as one procedure for building or reviewing how an interface moves, responds and gets people through a task. Use when adding or reviewing animation, transitions, gestures, micro-interactions, loading and optimistic states, feedback, targets, menus, forms, onboarding or multi-step flows. Triggers on: animate, motion, transition, easing, duration, spring, bounce, stagger, enter, exit, modal, drawer, popover, tooltip, toast, icon swap, press, hover, drag, rubber band, arc, anticipation, squash and stretch, follow-through, compound motion, storyboard, reduced motion, jank, feels slow, optimistic UI, hit area, Fitts's law, Hick's law, Miller's law, Doherty threshold, Postel's law, Jakob's law, proximity, similarity, Von Restorff, serial position, peak-end, Zeigarnik, goal gradient, Tesler's law, Parkinson's law, Occam's razor, Pareto, progressive disclosure, defaults, undo.
Connect a ChatGPT or Claude account and sync its conversation history into the brain automatically. Cookie paste-in is the primary lane; sync is incremental (watermark + trailing-window gap-heal), and can run on a schedule via autopilot or host cron. Distinct from the export-file lane (that lives in conversation-archive) — this is the LIVE, account-connected, auto-scraping path.
Comprehensive citation management for academic research. Search Google Scholar and PubMed for papers, extract accurate metadata, validate citations, and generate properly formatted BibTeX entries. This skill should be used when you need to find papers, verify citation information, convert DOIs to BibTeX, or ensure reference accuracy in scientific writing.
View the live Mihomo proxy chain of local processes. Use when the user asks which proxy Claude, Codex, Gemini, ChatGPT, a browser, or another process goes through. Read-only. For profile topology and writes use clash-doctor; for egress IP quality use ip-check.
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.