Loading...
Loading...
Found 469 Skills
Use when the user needs to perform multi-step operations with the MetaMask Agentic CLI such as onboarding, login, swapping tokens, bridging across chains, opening/closing/modifying perpetual positions, prediction market trading, or troubleshooting CLI issues.
Live developer experience audit. Uses the browse tool to actually TEST the developer experience: navigates docs, tries the getting started flow, times TTHW, screenshots error messages, evaluates CLI help text. Produces a DX scorecard with evidence. Compares against /plan-devex-review scores if they exist (the boomerang: plan said 3 minutes, reality says 8). Use when asked to "test the DX", "DX audit", "developer experience test", or "try the onboarding". Proactively suggest after shipping a developer-facing feature. (gstack) Voice triggers (speech-to-text aliases): "dx audit", "test the developer experience", "try the onboarding", "developer experience test".
You are a professional Customer Service Specialist and Communication Strategist. Use this skill when the user wants to write customer service scripts, support email templates, feedback responses, FAQ content, or help center articles. Activate when the user mentions "customer service," "support email," "support template," "help center," "knowledge base article," "FAQ for support," "chatbot script," "live chat script," "phone script," "customer feedback response," "review response," "refund email," "cancellation template," "late shipping response," "apology email," "product outage response," "billing email," "customer onboarding message," "troubleshooting guide," "password reset article," "support ticket," "macro," "saved reply," "customer service playbook," "internal support doc," "review reply," "3-star review," "negative review response," "positive review response," "customer loyalty message," "subscription cancellation script," "exchange template," "customer portal content," "chatbot flow," "in-app help copy," "social media response," "support documentation," or "customer service tone." Covers scripts for phone, chat, and messaging; email templates for all support scenarios; feedback and review responses; FAQ sections; and full help center articles with troubleshooting guides.
Help users improve retention and engagement metrics. Use when someone is dealing with churn, optimizing activation flows, building habit-forming products, or trying to increase user engagement and lifetime value.
Prime a codebase by reading every source file in full. Use when starting work on a new or unfamiliar project, or when the user asks to "learn the codebase", "read the codebase", "prime", or "get up to speed".
BYOK — register a custom LLM endpoint (Anthropic, OpenAI, Qwen, DeepSeek, etc.) with your own API key
Activated when users start a new novel project - Guides them through the seven-step methodology (constitution → specify → clarify → plan → tasks → write → analyze) with gentle prompts and explanations
Creates a new AEM Edge Delivery site from scratch — GitHub repo from the boilerplate, aem-code-sync installation, initial DA content (nav, footer, homepage), and a live preview URL. Use this skill whenever a user wants to create a new AEM Edge Delivery site and no repository or DA content exists yet.
Analyze an existing codebase with parallel mapper agents, creating codebase documentation, understanding brownfield projects, or mapping code structure. Triggers include "map codebase", "analyze codebase", "create project context", "document codebase", "understand code", and "codebase map".
Create a Founder Sales Sprint Pack (ICP wedge + target list, outreach sequences, diagnostic discovery script, decision-enablement assets to beat “no decision”, and a white-glove activation plan). Use for founder-led sales, early sales, first customers, and first 10 customers. Category: Sales & GTM.
Use this before touching code when you have a requirement for a specification or multi-step task
Create structured incident response runbooks with step-by-step procedures, escalation paths, and recovery actions. Use when building runbooks, responding to incidents, or establishing incident response procedures.