Skills
101,174 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Swap, bridge, and deposit on Polygon using the Polygon Agent CLI. Covers same-chain token swaps, cross-chain bridging, yield deposits into Aave v3 and Morpho vaults, and withdrawals from those positions. Write commands preview by default; add --broadcast (or enable `agent mode auto`) to execute.
Audit a brand's social positioning from its profile, offer, customer proof, and competitor material. Use when the user says "audit our positioning", "review our profile", "why do we sound like everyone else", or "what should our social message be". NOT for inventing a new identity from intuition or writing a post; use audience-personas and social-proof-mining first, then hand approved positioning to the content skills.
Unified poster and standalone image generation skill with hard routing. Produces one or more final poster/image assets as requested, using mandatory HTML-based layout for information-heavy posters and image-first generation only for strictly visual assets.
Run PostgreSQL queries for testing, debugging, and performance analysis. Use when you need to query the database directly, run EXPLAIN ANALYZE, compare query results, or test SQL optimizations. Always pass a target — `--prod` or `--dev` — because prod and dev are different databases and the default is prod. Always uses read-only connections unless explicitly directed otherwise.
Design pricing for a product. Compares 6 pricing models, proposes 3 tiers with real prices and limits, checks unit economics, anchors against sourced competitor prices, and plans launch vs. scale pricing. Use when a founder asks what to charge or how to structure plans.
Audit the whole product across code, quality, process, docs, roadmap, and tooling; it owns the repo-wide bug hunt, security research, and broken-version investigation (scoped and budgeted per dimension, as distinct from `review-change`'s change-scoped review). Persist one severity-ranked, F-numbered report with proposals; never fix or file work. Triggers: "product-audit", "audit the product", "full health check", "are we product-ready", "CTO review".
It's 11pm before your launch. Your PH page is ready but you have no idea what actually moves the ranking algorithm. Upvotes? Comments? Time-of-day? This is the hour-by-hour operations manual from someone who's coached 30+ #1 finishes. What's inside: • Ranking algorithm deep-dive (it's not just upvotes — weighted factors decoded) • Launch day minute-by-minute checklist (PST timing, first 3 hours are critical) • Voter mobilization strategies (ethical, anti-spam-safe approaches) • Asset preparation templates (gallery, tagline ≤60 chars, maker comments) • Post-launch 72h momentum plan (convert PH traffic → retained users) Built from: 30+ PH #1 daily wins, 10+ weekly top 3, 2 monthly top 5. 3,000-5,000+ upvotes per launch. Triggers: "Product Hunt" | "PH launch" | "Product Hunt #1" | "PH ranking" | "Product Hunt strategy" | "PH upvotes" | "launch day" | "PH打榜" | "Product Hunt攻略" | "PH ranking algorithm"
Prompt engineering frameworks for building, testing, versioning, and evaluating prompts: chain-of-thought, few-shot, regression testing, and rubrics. Use when designing production prompts, running A/B tests, or building prompt libraries.
Build React Native 0.76+ apps with Expo SDK 52. Covers mandatory New Architecture (0.82+), React 19 changes (propTypes/forwardRef removal), new CSS (display: contents, mixBlendMode, outline), Swift iOS template, and DevTools migration. Use when: building Expo apps, migrating to New Architecture, or troubleshooting "Fabric component not found", "propTypes not a function", "TurboModule not registered", or Swift AppDelegate errors.
Diagnoses and fixes a paper's argument architecture and narrative flow, independent of any venue. Checks whether the story is built in the right order, whether each section does its job, whether the intro promises what the body delivers, and whether the contribution -> evidence -> conclusion arc holds — then produces a restructuring plan (move / merge / split / cut sections) the author approves BEFORE anything is rewritten. Use when a researcher says "the structure is off", "it doesn't flow", "reviewers said it's hard to follow / disorganized / the story is unclear", "my intro over-promises", "related work is in the wrong place", "this section doesn't belong here", "reorganize my paper", "fix the narrative", or "the contributions don't match the results". Distinct from tailor-to-venue (venue/track fit, page limits, templates) and polish-prose (sentence-level wording). Bundles outline_extract.py to print the section tree + each section's opening sentence so the architecture is reviewable at a glance.
Anchors predictions in historical reality by identifying a class of similar past events and using their statistical frequency as a baseline (outside view) before analyzing case-specific details. Use when starting a forecast, establishing base rates, testing "this time is different" claims, or when user mentions reference classes, outside view, base rates, or starting a new prediction.
Create and edit Remotion videos with domain-specific knowledge. TRIGGERS - Use this skill when: - User mentions "Remotion" in their request - User references a Remotion project path (remotion-videos/*, contains remotion.config.ts) - User asks to create, animate, or edit video content in a Remotion context - User wants to build compositions, animations, or video sequences in React Always invoke this skill BEFORE writing any Remotion code.
Review LLM prompts against the prompt-engineering skill's principles — leading with where each line came from — and report the findings without modifying files. Use when reviewing prompt quality, auditing a prompt, evaluating a system prompt, or checking whether prompt issues are high-confidence and fixable.
Resource recommendation article generator with multi-turn workflow and domain adaptation. Creates structured articles with verifiable data, proper formatting, and professional style. Use when user explicitly requests to generate/write/create a recommendation article (生成/写/创建 + 推荐文章/资源列表). Must include both action + article intent. Don't trigger on simple questions like "推荐几个工具".
ROS 2 engineering: rclcpp/rclpy, colcon/ament, launch, QoS/DDS, tf2/URDF, ros2_control, Nav2, MoveIt 2, sensors, runtime/artifact provenance, and hardware safety. Use for development, review, debugging, and ROS 1 migration to ROS 2. Not for general C++/Python, unrelated middleware, or web/mobile tasks.
When the user wants to design a sales compensation plan, set quotas, build accelerators, model plan costs, handle clawbacks, or create SPIFs. Trigger phrases: 'design a comp plan,' 'set sales quotas,' 'build accelerators,' 'sales compensation,' 'OTE structure,' 'SPIF design,' 'commission structure,' 'how much should I pay my sales team,' 'sales bonus,' 'variable compensation.' For quota-setting inputs from forecast data, see forecast. For pipeline data that informs quota realism, see pipeline-review.
Detect Remote Code Execution (RCE) vulnerabilities in a codebase using a three-phase approach: recon (find dangerous execution sinks), batched verify (trace user input to sinks in parallel subagents, 3 sinks each), and merge (consolidate batch results). Covers OS command injection, eval-like sinks, and unsafe deserialization. Requires sast/architecture.md (run sast-analysis first). Outputs findings to sast/rce-results.md. Use when asked to find RCE, command injection, or unsafe deserialization bugs.
Composes and polishes professional scientific correspondence -- emails to collaborators, journal cover letters, and responses to peer reviewers -- ensuring clear communication, appropriate tone, explicit asks, and professional formatting for academic contexts. Use when writing or polishing scientific emails, cover letters to editors, reviewer responses, or when user mentions email to collaborator, cover letter to journal, reviewer response, or professional scientific correspondence.
Authentication, authorization, and API security implementation. Use when building user systems, protecting APIs, or implementing access control. Covers OAuth 2.1/OIDC, JWT patterns, sessions, Passkeys/WebAuthn, RBAC/ABAC/ReBAC, policy engines (OPA, Casbin, SpiceDB), managed auth (Clerk, Auth0), self-hosted (Keycloak, Ory), and API security best practices.
Review Bun runtime security audit patterns. Use for auditing Bun-specific vulnerabilities including shell injection, SQL injection, server security, and process spawning. Use proactively when reviewing Bun apps (bun.lockb, bunfig.toml, or bun:* imports present). Examples: - user: "Review this Bun shell script" → audit `$` usage and argument injection - user: "Check my bun:sqlite queries" → verify `sql` tagged template usage - user: "Audit my Bun.serve() setup" → check path traversal and request limits - user: "Is my Bun.spawn() usage safe?" → audit command injection and input validation - user: "Review WebSocket security in Bun" → check authentication before upgrade
Verified prompt templates and structures for Seedance 2.5 / 2.0 video generation, distilled from the highest-performing published cases on goodcase.ai. Use when the user asks to write, revise, or review a Seedance video prompt, or asks how to prompt Seedance for a specific kind of shot (narrative short, ad/commercial, UGC talk-to-camera, dialogue with lip-sync, action, product reveal, retro home video, travel film, pet or animal lead, comedy skit, horror, fantasy or sci-fi spectacle, 3D cartoon, car spot, fashion film, sports, storyboard image to video, and similar). Also use when the user names Seedance, 即梦视频, or Seedance 2.5/2.0 directly.
Use when complex problems require systematic step-by-step reasoning with ability to revise thoughts, branch into alternative approaches, or dynamically adjust scope. Ideal for multi-stage analysis, design planning, problem decomposition, or tasks with initially unclear scope.
Initialize the design system or create new UI components with accessibility, Tailwind/shadcn integration, and documentation. Use when setting up the initial design system, adding component categories, or creating complex UI components that need design review.
Generate Mermaid diagrams from Salesforce metadata and architecture. Reads org metadata, Apex classes, Flow XML, and object definitions to produce ERDs, class diagrams, sequence diagrams, flow visualizations, and deployment dependency graphs. Activate on "diagram", "visualize", "ERD", "sequence diagram", "class diagram", "flowchart", "data model", or "architecture diagram". DO NOT activate for PNG/SVG image rendering or non-Salesforce systems.
Scaffold Lightning Web Components with HTML templates, JS controllers, CSS with SLDS compliance, js-meta.xml config, and Jest tests. Use when asked about Lightning Web Components, LWC, component scaffolding, or Jest tests for LWC. Activate on .js-meta.xml files, mentions of "LWC", "Lightning Web Component", "wire adapter", "lightning component", or "@api/@wire/@track decorators".
James Bach's HTSM Product Factors (SFDIPOT) analysis for comprehensive test strategy generation. Use when analyzing requirements, epics, or user stories to generate prioritized test ideas across Structure, Function, Data, Interfaces, Platform, Operations, and Time dimensions.
Audit any live Shopify store or product page for Google Merchant Center Misrepresentation policy risks by crawling public pages. Use when a merchant was suspended, is preparing a GMC submission, or wants a public-page compliance sweep before appeal or launch.
SolidJS 2.0 implementation and API explanations, including React comparisons, async patterns, stores, DOM, and server functions. Use for code or questions targeting solid-js major 2. For a requested 1.x conversion use solidjs-v2-migration; for a diff review use solidjs-v2-reviewer.
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.