Skills
101,174 packaged capabilities and playbooks for agents. Install any of them with one command.
All
AWS Startups reference content — Activate FAQs, credits guide, programs, partner offers, sample architectures, and hundreds of learning articles covering generative AI, cloud architecture, cost optimization, security, fundraising, go-to-market, and real-world startup case studies. Use when the user asks factual questions about AWS Activate (eligibility, credits, programs, providers), wants a sample architecture or solution guide, or needs an AWS-curated learning article on a specific startup topic. For copy-paste AI prompts (RAG chatbot, MVP scaffold, security baseline, GPU quota, etc.), see the prompt-library-for-startups skill. Do not use for: account-specific lookups (credits balance, Activate membership status, application status), real-time event listings beyond the events stub, or content not present in the bundled `references/` tree.
This skill should be used when the user asks to "share memory between agents", "KV cache compaction for multi-agent", "orchestrator worker context", "latent briefing", "reduce worker tokens", "cross-agent memory without summarization", or discusses Attention Matching compaction, recursive language models with workers, or token explosion in hierarchical agents.
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
Explore and interpret football data, and judge players or teams from stats: rankings, 'who is the best', 'is he a poor finisher', comparisons, headlines and social posts about stats. Use for match events, team and player comparisons and tactical patterns, at the user's level.
Optimize podcast content for search engines using transcripts, structured show notes, and strategic keyword targeting to drive organic discovery. Use when: Launching a new podcast and planning for discoverability; Adding transcripts to existing episodes for SEO benefit; Optimizing show notes for search traffic; Building topical authority through podcast content; Increasing organic traffic to podcast landing pages.
Generates Protractor E2E tests for Angular/AngularJS apps in JS/TS. NOTE: Protractor is officially deprecated — recommend Playwright or Cypress. Use when user mentions "Protractor", "element(by.model())", "Angular E2E". Triggers on: "Protractor", "element(by.model)", "Angular E2E test", "protractor.conf".
Short-video hook (opening) type selection and writing, Chinese name “钩子” (hook). Use when coming up with or writing hooks, when stuck on hook ideas, designing a hook for the first 5 seconds, writing a video or spoken-script opening, or when the user asks how to make a video opening, wants opening templates or hook types, or asks for a hook. Also use during ra-洗稿 script rewriting and topic development. Provides a scenario-based taxonomy of 7 hook types with a decision flow, prerequisites, sentence templates, and common mistakes. To diagnose and optimize an existing hook draft, use dbs-hook instead; this skill selects the type, while dbs-hook polishes its execution.
Capture professional-quality remote interviews using double-ender technique and dedicated recording platforms for podcasts, media, and content production. Use when: Setting up remote podcast interviews with guests; Recording media interviews across distances; Creating customer interview content; Producing expert interviews for thought leadership; Conducting research interviews with high audio quality.
Translate an existing Remotion (React-based) video composition into a HyperFrames HTML composition. Use ONLY when the user explicitly asks to port, convert, migrate, translate, or rewrite a Remotion composition as HyperFrames (e.g. "port my Remotion project to HyperFrames"). Do NOT use when (a) authoring a NEW HyperFrames composition (even if A/B-testing a Remotion video); (b) Remotion is mentioned in passing; (c) Remotion code is shared as reference, not for translation; (d) the user wants "the same video as my Remotion one" without explicitly asking to migrate the source — treat as a fresh HyperFrames build. When in doubt, default to the `hyperframes` skill. Detects unsupported patterns (useState, useEffect side effects, async calculateMetadata, third-party React component libraries, `@remotion/lambda`) and recommends the runtime interop escape hatch instead of a lossy translation.
Process large codebases (>100 files) using the Recursive Language Model pattern. Orchestrates parallel sub-agents to map-reduce across files without context rot. Use when: analyzing large repositories; auditing security or auth across many files; finding patterns across 50+ files; processing large log files or data dumps.
Analyze product screenshots to extract feature lists and generate development task checklists. Use when: (1) Analyzing competitor product screenshots for feature extraction, (2) Generating PRD/task lists from UI designs, (3) Batch analyzing multiple app screens, (4) Conducting competitive analysis from visual references.
Read-only audit of a repository's SDD harness for FAXINA E DERIVA: inventories commands, agents, skills, hooks, settings, and scripts of ANY engine (Claude Code, Codex, Kimi CLI: reads CLAUDE.md and AGENTS.md, .claude/, .agents/, and .codex/), measures references, recency, duplication, and drift between docs and code, and generates a single report AUDITORIA_SDD_<data>.md without changing anything. Invoke when someone says "the harness has grown too much", "what does nobody use here", "do the docs still match the code?", or asks for a harness cleanup (`.claude/`, `.agents/`, or `.codex/`). ⚠️ Boundary: this skill asks WHAT IS LEFT OVER AND WHAT HAS DRIFTED (hygiene). For SECURITY — easter egg, malicious code, backdoor, exfiltration, invisible unicode in third-party material you are about to install — use the rdd-audita-harness skill. Excess is not a threat; both are read-only and complement each other.
Configure security headers to defend against clickjacking, XSS, MIME confusion, and SSL stripping attacks. Use this skill to set up Content-Security-Policy, X-Frame-Options, HSTS, configure middleware headers, or understand browser security features. Triggers include "security headers", "CSP", "content security policy", "X-Frame-Options", "HSTS", "clickjacking", "MIME confusion", and "middleware headers"
Follow-up Signals scout for the inbox itself. Attaches a check to each newly resolved report, spot-checks a couple of settled fixes with fresh probes, answers the checks it is dispatched for, and reports when a fix didn't hold, plus a gated escalation check on dismissed reports.
Create, improve, and test skills for the z-schema JSON Schema validator library. Use this skill whenever the user wants to create a new skill from scratch, turn a workflow into a reusable skill, update or refine an existing skill, write test cases for a skill, or organize reference material for a skill. Also use when someone mentions "skill", "SKILL.md", or wants to document a z-schema workflow for reuse by humans or AI agents.
Stellar smart contract development (Rust, soroban-sdk). Entry point with project setup, contract anatomy, and build/deploy workflow, routing to three companion files in this directory — development.md (storage/TTL, authorization, cross-contract calls, tokens, events, errors, upgrades, fees, troubleshooting), testing.md (unit, fuzz, property, fork, mutation, integration), and security.md (vulnerability classes, checklists, tooling, audits). Use when writing, testing, reviewing, securing, debugging, or shipping Stellar smart contracts, including anything the user calls "Soroban" — Soroban contracts, soroban-sdk, Soroban auth/storage/TTL errors, SEP-41 tokens, or SAC integration from contract code.
Test if your solution actually solves the validated problem before building the full product. Master the art of showing concepts and prototypes to get honest feedback on solution fit. Use when: **After problem interviews** to test if your solution addresses validated problems; **Before building MVP** to validate core value proposition; **Prototype testing** to get feedback on concepts and mockups; **Feature validation** to test if new features solve real problems; **Pivoting** to test alterna...
Review diffs, branches, and PRs for contracts, correctness, security, architecture, tests, and operational risk. Use when the user requests a code review or change assessment; read-only unless explicitly asked to make corrections
Use when the user is working on who can sign in to Spree 6 and what they may do—staff roles and permission keys, secret-key scopes, registering permission scopes for an extension, 403 errors with `required_permission` / `required_scope`, storefront ownership rules (`Spree::Storefront::AccessPolicy`), custom login strategies (SSO, OIDC, Auth0/Okta/Entra/Firebase), JWT audiences, or swapping the customer/admin user class. Common phrasings include “Spree roles”, “staff permissions”, “add a role”, “read_orders permission”, “Spree.permissions.register_scope”, “API key scopes”, “403 Missing permission”, “who can see this order”, “SSO for the dashboard”, “OIDC login”, “custom authentication strategy”, “Spree.customer_class”, “admin_user_class”, “CanCanCan in Spree 6”. Spree 6.
Use when working with how Spree 6 gets goods to the customer — fulfillments (`ful_`), delivery methods, delivery zones, delivery profiles and origin groups, delivery rates, calculators and carrier rate providers (EasyPost, freight), order routing and stock splitters, partial fulfillment and splitting, shipping labels, tracking/deliveries, carrier tracking webhooks, pickup and digital delivery. Common phrasings include "shipping method", "no delivery rates at checkout", "ship from the nearest warehouse", "custom shipping calculator", "live carrier rates", "mark as shipped", "partial shipment", "tracking number", "carrier webhook", "click and collect", "3PL / WMS integration", "fulfillment stuck unfulfilled", "add a fulfillment status", "fulfillment.fulfilled event", "Spree::Shipment". Returns/exchanges/claims live in spree-returns; stock counts, reservations and transfers in spree-inventory.
Use when working with stock in Spree 6 — StockLevel counters (count_on_hand, allocated_count, reserved_count, incoming_count, available/purchasable), stock locations (kind, pickup_enabled, returns_enabled), stock movements and their kinds, checkout stock reservations and their expiry job, backorders, inventory tracking on/off, bulk stock sync from an ERP/WMS (bulk_upsert), stock transfers, suppliers, purchase orders and stock receipts, the spree:stock:recount_levels task, and stock_level events. Common phrasings include "stock count is wrong", "oversold", "sync inventory from ERP", "update stock via API", "reserve stock at checkout", "stock reservation expired", "backorder", "restock", "move stock between warehouses", "purchase order", "receive a delivery", "incoming stock", "StockItem", "count_on_hand", "out of stock".
Tailwind CSS plugins — official plugins and custom plugin development. PROACTIVELY activate for: (1) @tailwindcss/typography (prose), (2) @tailwindcss/forms, (3) @tailwindcss/aspect-ratio (now built-in), (4) @tailwindcss/container-queries, (5) writing custom plugins via plugin() API, (6) addUtilities, addComponents, addVariant from plugin API, (7) third-party plugins (tailwindcss-animate, tailwind-merge), (8) in-CSS @utility and @variant in v4 (often replaces JS plugins), (9) plugin migration from v3 JS API to v4 CSS API. Provides: official plugin install/setup, plugin API reference, custom plugin examples, and v3-to-v4 plugin migration guide.
Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
Test React components with Testing Library patterns. Covers queries (getBy/findBy/queryBy), user-event interactions, async testing (findBy vs waitFor), accessibility testing, and MSW integration for API mocking. Use when: testing React components, simulating user interactions, testing forms, mocking API calls with MSW, or writing accessible tests. Keywords: testing-library, react testing library, getByRole, user-event, waitFor, MSW, screen.
Removes invisible Unicode, zero-width and tag characters, unusual whitespace, and textual AI provenance/watermarks from text the user owns or is authorized to process, and provides a best-effort statistical rewriting workflow. Applies to Traditional Chinese, Simplified Chinese, English, Markdown, HTML, and plain text; use when the user says "去文字浮水印", "去 Claude 浮水印", "清理不可見字元", "清除 AI provenance", or asks to check text markings. Text watermarks are a different problem from file C2PA/EXIF metadata and visible image watermarks; this skill does not handle the latter two directly.
Use when a Three.js scene has performance problems: low FPS, memory leaks, too many draw calls, or high GPU memory usage. Prevents the common mistake of forgetting dispose(), creating objects in the render loop, or not using InstancedMesh for repeated objects. Covers disposal patterns, draw call optimization, InstancedMesh, LOD, texture compression, renderer.info, Stats.js profiling. Keywords: performance, memory leak, dispose, draw calls, FPS, slow, optimization, InstancedMesh, LOD, renderer.info, Stats, profiling, laggy, low FPS, stuttering, browser freezes.
TypeGPU and raw WebGPU adapter patterns for HyperFrames. Use when creating GPU-rendered compositions with TypeGPU, raw WebGPU, WGSL fragment shaders, compute pipelines, liquid glass effects, particle systems, or any canvas layer driven by navigator.gpu that responds to HyperFrames hf-seek events.
Sumi (formerly ux-ui-mastery), a UX/UI design-intelligence skill suite from Phazur Labs: a router skill plus deep skills for cognitive psychology UX, Nielsen Norman Group heuristics, UX research methods, interaction and motion design, accessibility and inclusive design, mobile and desktop UX, cross-cultural i18n UX, agentic AI and generative UX, ambient/zero UI, spatial and voice UX, design systems and tokens, component code, and reference-grounded visual design.
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.