Skills
96,770 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Design, build, and refine a QR code–based tracking system. This skill helps generate QR codes, define what happens when they are scanned, and track scan events (who, where, when, how) for marketing, operations, product flows, or internal tools.
Run a comprehensive quarterly CRM audit covering list health, bounce monitoring, data quality, scoring calibration, engagement metrics, and property cleanup. Produces a health report with quarter-over-quarter trend comparison.
Apply a brand-neutral Quiet Editorial UI edit style to an existing HyperFrames project. Use when someone asks to apply Quiet Editorial UI, use a quiet editorial editing style, add a refined editorial software look, restyle HyperFrames with serif-led editorial graphics, place elegant overlays in negative space or over footage, or use the same visual system for a full-frame graphic composition.
Student semester onboarding — clinic procedures, a tour of the tools, and practice exercises before real cases. Reads the manual the supervising teacher uploads during setup and teaches it interactively. Use when a new clinic student says "onboard me", "I'm new to the clinic", "start", or at the beginning of each semester; pass --card for a one-page reference card.
React Hook Form with Zod validation. Covers form setup, validation schemas, field components, error handling, and submission with shadcn/ui integration. USE WHEN: user mentions "React Hook Form", "RHF", "Zod validation", "shadcn/ui forms", "zodResolver", "FormField", asks about "form validation with Zod", "shadcn form components" DO NOT USE FOR: React 19 Server Actions - use `react-19` skill instead, basic form handling - use `react-forms` skill instead, controlled/uncontrolled patterns - use `react-forms` skill instead
React Hooks patterns, rules, and custom hook development. Covers all built-in hooks (useState, useEffect, useContext, etc.), performance hooks, and patterns for creating reusable custom hooks. USE WHEN: user mentions "custom hooks", "hook rules", "useState", "useEffect", "useReducer", "useCallback", "useMemo", asks about "hook dependencies", "creating hooks", "hook patterns" DO NOT USE FOR: React 19 use() hook - use `react-19` skill instead, Context API details - use `react-context` skill instead, form-specific hooks - use `react-forms` or `react-hook-form` skills instead
Guides authorized enterprise adversary simulation and red team operations—campaign planning, threat-informed objectives, MITRE ATT&CK–framed TTP selection, OPSEC and scope, purple-team coordination, detection validation narratives, executive reporting, and blue-team lessons learned. Emphasizes rules of engagement, written authorization, and no unauthorized targeting. Use for red team, adversary simulation, purple team, assumed breach exercise, MITRE ATT&CK campaign, detection gap assessment, or threat-informed emulation—not LLM/agent adversarial testing (ai-redteam), single-vector pentest deliverables only (web-pentester, network-pentester, penetration-tester as execution specialists), SOC alert triage (soc-analyst), or incident command (incident-responder).
Check regulatory feeds, report new items since the last check, and filter by an importance threshold. Use when the user says "check the reg feed", "what's new in regulation", "regulatory updates", when triggered from a scheduled job, or when manually pasting regulatory updates for classification and diff analysis.
Search community legal skills in watched registries, show matches with their descriptions, and offer the option to view the full SKILL.md before installing. Use when the user says "browse," "search skills," "find a skill for X," "what's available," or wants to add a new registry to the watch list.
Recommend community skills based on recent activity in other plugins. Checks whether the community has already built something relevant to a task and mentions it once, non-intrusively. Use when the user says "is there a community skill for this", "what else is available", or asks for skill recommendations; also runs as a passive part of other plugin workflows.
A guide on where to place repository interfaces. It explains why, in Clean Architecture, repository interfaces should be placed in the use case layer rather than the domain layer. Its focus is preventing coupling between domain models and repositories and enforcing design intent through structure. Triggers: activated by repository-placement-related requests such as "where should repositories go", "placement of repository interfaces", "repositories in the domain layer", or "repositories in Clean Architecture".
Polish market product price comparison: 20+ shops, shipping costs, manufacturer vs seller warranty, B2B/statutory warranty analysis, stock status, distribution chain. Export TXT/XLSX/HTML. Use when: looking for a product to buy, price comparison, where to buy cheapest. Triggers: cena, porównaj, gdzie kupić, najtaniej, sklep, price compare, best price, kup, ile kosztuje.
Deep web research with parallel investigators, multi-wave exploration, and structured synthesis. Spawns multiple web-researcher agents to explore different facets of a topic simultaneously, launches additional waves when gaps are identified, then synthesizes findings. Thoroughness: quick for factual lookups | medium for focused topics | thorough for comparisons/evaluations (waves continue while critical gaps remain) | very-thorough for comprehensive research (waves continue until satisficed). Auto-selects if not specified.
Use when planning features and need current API docs, library patterns, or external knowledge; when testing hypotheses about technology choices or claims; when verifying assumptions before design decisions - gathers well-sourced, current information from the internet to inform technical decisions
Application resilience patterns. Circuit breakers, retries with backoff, bulkheads, timeouts, fallbacks, and health checks. Polly (.NET), resilience4j (Java), cockatiel (Node.js). USE WHEN: user mentions "circuit breaker", "retry", "backoff", "bulkhead", "resilience", "fault tolerance", "Polly", "resilience4j", "fallback" DO NOT USE FOR: error handling basics - use language skills; monitoring - use `opentelemetry`
Use when results are valid but surprising, negative, unstable, or ambiguous — to decide debug/rerun/ablate/revise/park. Not for engineering failures like NaN/OOM (use experiment-debugger). Not for confound or claim-drift audit before locking results into the paper (use research-results-auditor).
Analyze user retention and churn using survival analysis, cohort analysis, and machine learning. Calculate retention rates, build survival curves, predict churn risk, and generate retention optimization strategies. Use when working with user subscription data, membership information, or when user mentions retention, churn, survival analysis, or customer lifetime value.
Plan or run a measured goal loop with anti-goal guardrails. Planning mode drafts metrics, discovery, and work structure without changing the workspace. When the user asks to run, delegate, automate, or resume the loop, execution mode may run bundled local helper scripts, write durable `.okra` records, spawn subagents, and optionally route writer work through an already-installed Codex or Claude CLI. Use for OKRs, metric-led improvement, bounded research, or progress that must preserve budget, quality, safety, trust, or another measured constraint. All actions remain inside the user's request and runtime permissions; the skill does not install tools, add credentials, grant authority, or contact external services on its own.
Manage the PR review iteration loop: poll for reviewer feedback, assess suggestions with evidence, implement fixes, resolve threads, and drive CI/CD to green. Works standalone on any PR (bug fix, refactor, hotfix, feature) or as a composable module invoked by /ship. Spec-aware when a SPEC.md is provided, but does not require one. Triggers: review, review loop, PR feedback, iterate on PR, resolve reviews, CI/CD resolution, green pipeline, address reviewer comments.
Review the changes since a fixed point (commit, branch, tag, or merge-base) along four independent axes — Standards, Spec, Architecture, and Divergent design — each run as a parallel sub-agent so contexts stay clean, then verified against false positives and reported side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
Use when Codex or code/plan review findings need Definition-of-Done scope triage, especially to separate must-fix issues from minimal hygiene, out-of-scope hardening, repeated noise, or self-induced refinements. Also use when codex-review-cycle invokes scope guard between validity checking and summary render. Do not use for single-shot lint or unrelated changes.
Design and audit Revenue Operations CRM governance covering account/contact/opportunity objects, lifecycle stages, source attribution, owner routing, required fields, forecast hygiene, pipeline stages, handoffs, duplicate management, integrations, permissions, automation, reporting, data quality, and change control. Use when revenue teams need one trustworthy operating system instead of spreadsheet truth.
Processes GDPR Article 16 right to rectification requests, covering verification of corrected data accuracy, notification to recipients under Article 19, timeline management, and completion of incomplete data. Activate for rectification, correction request, inaccurate data, Art. 16, data correction queries.
Orchestrates infrastructure cost estimation with tier-based or custom TPS sizing. Offers pre-configured tiers (Starter/Growth/Business/Enterprise) or custom TPS input. Skill discovers components, asks shared/dedicated for EACH, selects environment(s), reads actual Helm chart configs, then dispatches agent for accurate calculations.
Orchestrates the RLM repo workflow end-to-end with phase gates, locked artifacts, addenda, traceability, and automatic bootstrap/upsert of AGENTS/PLANS scaffolding. Trigger phrases: "Implement requirement <run-id>", "Run RLM Phase <N>", "resume requirement", "lock Phase <N>", "verify locks".
Ruby language conventions, idioms, and modern features (3.x+) for writing idiomatic Ruby code. Covers error handling patterns, performance optimization, and Ruby-specific idioms. Use when writing or reviewing pure Ruby code, using modern Ruby features (pattern matching, ractors, RBS), optimizing Ruby performance, or establishing Ruby conventions. For Rails-specific guidance use the rails skill. For design patterns use design-patterns-ruby. For testing use rspec. For code style use rubocop.
Entry point for the linguistics toolkit. Routes to the right linguistics skill based on your situation. Use when you say 'linguistics', 'how is this framed', 'what does this word really mean', 'what is implied here', 'what does this word carry', 'how has this term changed', or want language analysis applied without knowing which specific tool fits.
Analyzes what is implied rather than said — the gap between literal content and communicative meaning. Use when you say 'what does this really mean', 'what is this message actually doing', 'is this a threat', 'what is being implied here', 'what does this leave unsaid', 'why does this feel off even though it seems polite', or when a communication seems fine on the surface but something is wrong underneath.
Surface internal contradictions, conflicting requirements, and edge cases that expose hidden conflicts in a document, spec, plan, design, or set of requirements. Use when something feels off but you can't pinpoint why, before committing to a design, or when requirements have grown incrementally and may have drifted out of sync. TRIGGERS: 'consistency check', 'find contradictions', 'does this spec make sense', 'check for conflicts', 'something feels wrong here', reviewing requirements docs, technical specs, architecture plans, product briefs, or any document where internal coherence matters.
Builds and repairs persuasive arguments by surfacing the warrant, auditing evidence, addressing counterarguments, and identifying rhetorical substitutes. Use when an argument has holes, the case isn't landing, or evidence isn't connecting to the claim. Triggers: 'build an argument', 'argument structure', 'the argument isn't working', 'op-ed', 'persuasive writing', 'make the case for', 'my argument has holes', 'the evidence doesn't land'.
Engineers psychologically compelling characters by mapping want vs. need, wound, defence mechanism, and defining contradiction. Use when a character feels flat, underdeveloped, or unconvincing. Triggers: 'my character feels flat', 'character development', 'make this character feel real', 'this character isn't working', 'character work', 'how do I develop this character'.
Omnisend platform help — email campaigns, SMS marketing, web push notifications, marketing automation workflows, popups/forms, segmentation, product recommendations, reporting, Shopify/WooCommerce/BigCommerce integrations, API. Use when Omnisend emails aren't reaching inboxes, automation workflows aren't triggering, SMS campaigns aren't delivering, popups aren't converting, ecommerce integration isn't syncing orders, or Omnisend API calls are failing. Do NOT use for cross-platform email marketing strategy (use /sales-email-marketing), cross-platform SMS strategy (use /sales-sms-marketing), cross-platform deliverability (use /sales-deliverability), cross-platform push strategy (use /sales-push-notification), or connecting tools (use /sales-integration).
Guide for sanitizing git repositories by identifying and replacing sensitive information such as API keys, tokens, and credentials. This skill should be used when tasks involve removing secrets from codebases, sanitizing repositories before sharing, or replacing sensitive values with placeholders. Applies to tasks involving secret detection, credential removal, or repository cleanup for security purposes.
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.