Skills
101,323 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Use this skill when users need to validate their marketing channel strategy, assess channel focus, or determine lead gen priorities. Activates for "validate my channels," "am I on the right platforms," "should I focus on X or Y channel," or when assessing marketing spread.
API reference for CoinMarketCap DEX endpoints including token lookup, pools, transactions, trending, and security analysis. Use this skill whenever the user mentions DEX API, asks about on-chain token data, wants to look up tokens by contract address, needs security/rug risk checks, or is building DEX integrations. This is the definitive reference for CMC DEX API questions. Trigger: "DEX API", "token by contract address", "CMC security API", "liquidity pool API", "/cmc-api-dex"
Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development. Use when the user writes, reviews, or refactors code and wants to apply cross-cutting, framework-agnostic conventions (naming, structure, typing, error handling, readability). For targeted React/Next advice, use react-best-practices; for Node/Express/API backends, use backend-patterns.
Turn every comment into a lead on autopilot. Claude watches your new comments, posts a friendly public reply (never a link), and DMs the commenter your lead magnet / resource — then logs them as a lead. Use when the user says "auto reply to comments", "DM everyone who comments", "comment to DM", "lead magnet automation", "turn comments into leads", "auto-respond", or "capture leads from a reel".
Turns limitations into creative fuel by strategically imposing constraints that force novel thinking, break habitual patterns, and reveal unexpected solutions. Covers resource constraints (budget/time/tools), format constraints (length/medium), rule-based constraints, and perspective constraints. Use when brainstorming feels stuck or generates obvious ideas, working with limited resources, designing with specific limitations, or when user mentions "think outside the box", "we're stuck", "same old ideas", "tight constraints", or "limited budget/time".
Use this skill when users need to remove customer friction, improve customer success, handle objections, design guarantees, or eliminate obstacles between customers and results. Activates for customer success issues, objection handling, or "customers can't get results" problems.
Turn a batch of ideas (or your content pillars) into a 2-week reel posting calendar with hooks, formats, and a daily plan. Use when the user says "content calendar", "posting schedule", "plan my content", "what should I post this week", "content plan", or "batch my reels"
Answer a question across a corpus of contract documents with verified citations. Use when the user asks what a contract says, which contracts have a clause, what changed between amendments, or any question that needs reading and citing across a set of contract files. The corpus must be on the local filesystem (see README).
Find the mistakes agents keep repeating in this repo and make each one impossible. Try architecture first, then types, then a lint whose error names the fix, then a test, and write docs last. Prove each check fails on a real past mistake. Repeat this each time the operator corrects you. Use for /correct.
Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform. Use for /create-verification-skill, "make a control skill for this repo", or when a project has no scripted way to prove UI/CLI/service behavior.
Transform audit data, performance reports, and structured analyses into polished visual deliverables. Generates presentation decks (PPTX), interactive HTML dashboards, or styled markdown reports with charts. Includes a customizable design system with forest green accent and warm cream backgrounds. Use when the user has analysis data and needs a visual deliverable.
Use when a user wants webcam, interview, or talking-head footage to look broadcast-quality — corrects exposure, white balance, skin tones, and overall color. Triggering symptoms include phrases like "my webcam footage looks dull", "skin tones look orange/green", "wash out background", "make the face pop", "match shots from two cameras", or any DaVinci Resolve color page question for talking-head content.
Adapts one base product demo into several vertical-specific variants (healthcare, finance, retail, or whatever segments the deal calls for) by analyzing the base demo's structure, working out how each vertical's real pain points map onto existing moments, then rewriting narration and on-screen text so the why-this-matters framing genuinely shifts per audience, not just the terminology. Each vertical is built on its own duplicated copy so the base demo stays intact. Use when the user says "make versions of this demo for healthcare, finance, and retail", "adapt this demo for different industries", "create vertical-specific variants of our demo", or "reframe this recording for three industries".
Condenses one full product demo into a single, continuous, social-ready teaser hitting a specific target runtime (default 60 seconds). This is compression, not selection: the whole demo's narrative arc (setup, each capability, the payoff) gets tightened into one coherent story, cutting dead air and repetition aggressively while preserving flow from beat to beat, rather than lifting out several separate highlight moments. Use when the user says "cut this demo down to 60 seconds", "make a short teaser from this full demo", "condense this into a social-ready clip", "give me a 30-second version of this demo", or "shrink this walkthrough into one tight clip for social".
When the user wants to publish on Dev.to, Hashnode, or other developer blogging platforms. Trigger phrases include "Dev.to," "Hashnode," "developer blog," "cross-posting," "technical blogging," "canonical URL," or "developer content platform."
Use when the user wants to integrate a Kafka client into an existing application or scaffold a Java Kafka client project (Maven or Gradle based) for Confluent Cloud, local Docker, or WarpStream. Covers the Apache Kafka Java clients (KafkaProducer/KafkaConsumer/KafkaShareConsumer) with Avro, JSON Schema, or Protobuf serializers. Also use when the user wants to optimize Java Kafka client configuration for WarpStream. Do NOT trigger for Kafka Streams apps (use kafka-streams-programming), Flink, connectors, or Kafka Python client (use developing-kafka-python-client).
Audit the Claude Code ecosystem — skill health and staleness, project activity pulse, CLAUDE.md instruction drift, Mac Mini service status. Use this skill whenever the user asks about ecosystem health, stale skills, abandoned projects, system status, infrastructure check, "what's broken", "what's stale", "how's my setup", or any request to review the state of their Claude Code environment. Also triggers on "/ecosystem", "audit my ecosystem", "ecosystem health", "ecosystem audit".
Create or redesign creative-studio, agency, photographer, artist, and portfolio websites where project work leads the story. Use for dark editorial shells, full-bleed campaign media, color-coded case-study chapters, oversized service typography, restrained project reveals, and a decisive contact finale.
Provides comprehensive guidance for Element Plus Vue 3 component library including installation, components, themes, internationalization, and API reference. Use when the user asks about Element Plus for Vue 3, needs to build Vue 3 applications with Element Plus, or customize component styles.
Use when the user asks to "optimize entity presence", reconcile an entity identity, or update canonical Knowledge Graph facts; audits and maintains machine-facing identity, sameAs, schema, disambiguation, and AI-recognition evidence through the entities registry. Not for page-level AI-citation readiness - use geo-content-optimizer; not for human-facing brand canon - use narrative-registry. 实体优化/知识图谱
Complete Frappe Framework development reference for building ERPNext apps. Use when creating custom DocTypes, controllers, hooks, REST APIs, form scripts, background jobs, or any Frappe/ERPNext development. Contains full API documentation for Document, Database, Controllers, Hooks, REST API, Form Scripts, Testing, and common patterns.
Event modeling facilitation for discovering and designing event-sourced systems using a structured 9-step workflow. Use when modeling domain workflows, designing event-sourced systems, writing Given/When/Then scenarios for commands or views, validating event models, or discussing event sourcing and domain-driven design. Triggers on: "model this workflow", "event model", "event sourcing", "what events do we need", "write GWT scenarios", "Given/When/Then", "validate the event model", "decompose into slices", "map this domain", "brainstorm events". Also activates for discovering domain actors, identifying automations, mapping integrations, or decomposing workflows into vertical slices. NOT for: implementing event store infrastructure, choosing databases, or writing application code.
Turn any complex topic or question into a short, plain-language explainer video: a hook, an analogy, a few essential parts, and a payoff, carried almost entirely by kinetic typography and keyframed shapes since there's usually no product or screen recording to lean on. Use when the user says "explain X simply", "make a video explaining how X works", "turn this concept into a video", or asks for a short explainer on something with no existing footage or article behind it.
Set up the Fallow app in Codex after the plugin is installed: check the fallow installation, choose the default analysis scope, run the first analysis, and show the user where the dashboard, the Code Health tab, @Fallow mentions and the config editor are. Use when the user chooses Set up for Fallow in Codex, or asks to onboard or configure the Fallow app. Do not use for setting up lint, format or CI tooling; use fallow-setup for that.
Turn release notes or a changelog entry into a tiered feature announcement video - a 60-90s big-launch cut with an animated hook, demo, and CTA, or a 20-30s quick-hit for minor releases - built around real demo footage of the feature. Use when the user says "make a feature announcement video", "we're shipping X, make a release video", "turn these release notes into a video", "changelog video", or "launch video for this new feature".
Use when working with utility functions in Frappe v14-v16. Covers frappe.utils.* for date/time, number/money, string, validation, and file path operations. Prevents reinventing stdlib alternatives that break timezone awareness, locale formatting, or multi-tenancy. Keywords: frappe.utils, nowdate, flt, cint, fmt_money, getdate,, date calculation, format number, money format, validate email, how to calculate days between. add_days, date_diff, validate_email, pretty_date, get_files_path.
Use when debugging or preventing errors in Frappe Document Controllers. Prevents autoname failures, validate loops, on_submit without is_submittable, wrong lifecycle hook choice, get_list permission errors, NestedSet errors, extend_doctype_class conflicts, missing super() calls, and recursion without flags. Covers error diagnosis by lifecycle phase for v14/v15/v16. Keywords: controller error, autoname, validate loop, on_submit, is_submittable,, save fails, validate error, on_submit not working, autoname broken, controller crash. get_list, NestedSet, extend_doctype_class, super, flags, recursion guard.
Use when writing unit tests, integration tests, creating test fixtures, or running tests with bench run-tests. Prevents flaky tests from missing fixtures, incorrect test isolation, and wrong test base classes. Covers frappe.tests.utils, IntegrationTestCase, UnitTestCase, test fixtures, bench run-tests flags, test naming conventions. Keywords: unit test, integration test, IntegrationTestCase, fixtures, bench run-tests, frappe.tests, test_*.py, how to write test, test fixtures, run tests, test fails, bench run-tests example.
Integrate Freemius monetization into a JavaScript/TypeScript backend — entitlement table, server-side checkout creation, purchase processing, and webhook license-lifecycle sync. Use when adding subscriptions, licensing, paywalls, or "unlock premium feature" gating to a SaaS/App/Web app whose backend is JS/TS (Hono, Express, Next.js, Fastify, serverless Fetch handlers). Covers the Freemius JS SDK (`@freemius/sdk`), not the frontend Checkout SDK.
Researches the market for a game concept as a forked analyst: genre health, comparable titles with sourced numbers, market sizing, audience, 2026 store conditions, positioning and a go/no-go call, saved to design/market-research/. Use for "market research", "competitive analysis", "is this game viable", "will this sell". Not for generating ideas (use game-brainstorm).
Manage GitLab incidents for issue tracking and incident management. Use when creating incidents, managing incident response, or linking incidents to issues. Triggers on incident, incident management, create incident, incident response.
Run the managed Orbit CLI through glab for remote graph queries and local code-graph workflows. Use when installing or updating Orbit, checking graph status, querying a remote Orbit graph, indexing or searching a local code graph, forwarding Orbit help, or troubleshooting managed-binary authentication. Triggers on orbit, knowledge graph, code graph, graph query, graph status, glab orbit, orbit-cli, orbit binary.
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.
