Skills
99,448 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Review and improve responsive layouts across mobile, tablet, desktop, web apps, SaaS dashboards, marketing pages, and desktop-like utilities. Use when designing breakpoints, adaptive navigation, grids, density, sidebars, tables, modals, keyboard states, or layouts that must work from small screens to wide monitors.
Use this skill whenever the user wants to create, improve, optimize, review, or rewrite a resume, CV, curriculum vitae, or hoja de vida. Triggers include: any mention of 'resume', 'CV', 'curriculum', 'hoja de vida', 'job application', 'ATS optimization', 'resume review', 'cover letter', or requests to prepare documents for job applications. Also use when the user asks to tailor a resume to a specific job description, improve bullet points, add metrics/quantification, check ATS compatibility, translate a resume between languages, or create multiple versions of a resume. Use this skill even if the user just says 'help me get hired', 'optimize my application', 'I need to update my resume', or 'review my experience section'. Do NOT use for LinkedIn profile optimization, portfolio websites, or general document formatting unrelated to job applications.
Reverse engineer Xamarin and .NET MAUI mobile apps by extracting assemblies.blob and XALZ-compressed DLLs with pyxamstore, then decompiling with dnSpy or ILSpy. Use when an APK contains libmonodroid.so, libmonosgen, assemblies.blob, assemblies/*.dll, or libxamarin-app.so, when an IPA contains Mono assemblies, or when jadx shows only Xamarin bootstrap classes.
Analyze code quality based on "Clean Code" principles. Identify naming, function size, duplication, over-engineering, and magic number issues with severity ratings and refactoring suggestions. Use when the user requests code quality checks, refactoring advice, Clean Code analysis, code smell detection, or mentions terms like code review, code quality, refactoring check.
Review or refactor React / Next.js code for performance and reliability using a prioritized rule library (waterfalls, bundle size, server/client data fetching, re-renders, rendering). Use when writing React components, Next.js pages (App Router), optimizing bundle size, improving performance, or doing a React/Next.js performance review.
ALWAYS load before starting any task. Provides the 10-dimension weighted scoring rubric (0-10 scale) used to evaluate all implementations in WRFC loops. Dimensions include correctness, completeness, error handling, type safety, security, performance, maintainability, testing, accessibility, and documentation. Includes deterministic validation scripts and score thresholds for pass/revise/reject decisions.
Reads GitHub and GitLab and constructs unexecuted forge payloads for the other RHDH skills: parse an issue, pull request, or merge request reference, fetch issue detail, resolve a plugin workspace, inspect checks or pipelines, read repository files, or build the exact command for a GitHub pull request, GitLab merge request, comment, label, assignee, approval, or /publish write. Use for a forge URL, a bare #number, a !number merge request, "which workspace is this issue in", a stale statusCheckRollup, "why did that check fail", or safe gh, glab, and jq command construction.
Converts a legacy Backstage frontend plugin used by Red Hat Developer Hub to the New Frontend System (NFS): replace createPlugin and createRoutableExtension with createFrontendPlugin, PageBlueprint, EntityContentBlueprint, AppDrawerContentBlueprint and createFrontendModule; map RHDH app-config.dynamic.yaml mount points onto extensions; add the ./alpha export to package.json without breaking legacy consumers; and verify the migrated dynamic plugin in a real RHDH instance. Use for "migrate my plugin to NFS", Blueprint migration, createFrontendPlugin, compatWrapper, alpha versus colocated exports, translations moved into a createFrontendModule with pluginId app, RHDH operator app.extensions and app.routes.bindings, and ENABLE_STANDARD_MODULE_FEDERATION testing.
Generate a single self-contained HTML page that is genuinely visual AND interactive — charts, diagrams, motion, tabs, comparison toggles, click-to-expand, base64-inlined images, opinionated typography. Use whenever the user wants ANY rich visual artifact from arbitrary content: explainer, research write-up, PRD or spec page, pitch, internal one-pager, "make this less boring" rebuild, scroll-snap deck, landing-style summary, distilled report. Trigger phrasings: "make me a page about X", "turn this PDF/doc into something visual", "build me a deck/talk/pitch", "explain Y in a visual way", "make this readable", "give it some eye candy", "I want something I can show the team", "less boring version of this", "rebuild that page", "redo it with more visuals". Output is one .html file that renders identically when DM'd — CDN libraries (Tailwind, Chart.js, D3, GSAP, Mermaid, Lucide) load from stable jsdelivr/unpkg URLs; every image is base64-inlined. Not for plain Markdown docs (use technical-writer), not for code review (use reviewer), not for maintainable component code a team will edit over time (use frontend-design — rich-page produces one-shot HTML artifacts, not living software).
Build Roblox VFX to a pro standard headlessly - anime-style moves, slashes, beams, impacts, auras, ultimates, summons - authored as effect definitions you can judge frame by frame in a browser simulator of Roblox's own VFX instances, with a generated library of 2,000+ original textures, Blender meshes for anything the effect IS (weapons, creatures, craters, debris), a polish pass, a pre-recording gate and a hit system that makes the target react like a body, then exported as a Studio kit. Also harvests free Creator Store VFX packs you have taken into your own account into a searchable library of portable JSON recipes and emits them as a Luau runtime module (VFXKit). No harvested effects ship. Use whenever the user wants a Roblox particle effect, explosion, aura, hit effect, fire, smoke, sparks, magic or anime move made rather than dragged in by hand, wants effects that look professional rather than generic, wants to build a reusable VFX library from packs they own, or asks why their ParticleEmitter is invisible, never stops, or looks nothing like it did in the pack they copied it from.
Six-phase playbook for running ownership transitions in either direction — receiving work from another team (initiative handoffs from shepherds, frameworks from Platform, operational responsibilities from SRE), or originating a transition (handing off a built framework, transitioning a shepherded initiative, or moving operational responsibilities). Applies Bitwarden's Work Transition Playbook from whichever side a team is on. Use when a team is about to take on or hand off transferred work, when preparing materials or sessions, when the support period is underway, or when running a pulse check or retrospective on a handoff.
Expert in the Yudao (芋道源码) ruoyi-vue-pro backend framework. Suitable for backend development tasks in Spring Boot monolith projects: module development, writing Controller/Service/Mapper/DO/VO, MyBatis Plus data access, permission control, multi-tenancy, data permissions, Excel export, scheduled tasks, and more.
Entry point for the emotional intelligence toolkit. Routes to the right emotional skill based on your situation. Use when you say 'emotional', 'why are they behaving like this', 'what motivates them', 'why the resistance', 'what do they really want', 'trust issues', or want emotional/interpersonal reasoning applied without knowing which specific tool fits.
Draft and fill Y Combinator SAFE contract templates — valuation cap, discount, MFN, pro rata side letter. Standard startup fundraising documents for convertible equity. Produces signable DOCX files. Use when user says "SAFE," "simple agreement for future equity," "YC SAFE," "valuation cap," "seed round documents," or "fundraising paperwork." Includes lawyer-reviewed practice guides; see openagreements.org/editors.
Braze platform help — Canvas Flow journey orchestration, email/push/in-app/SMS/WhatsApp/Content Cards campaigns, BrazeAI (predictive, generative, agentic), Braze Data Platform (CDI, Currents), real-time segmentation, Catalogs, Feature Flags, transactional email API, Liquid templating, Connected Content, Braze Alloys integrations, SCIM, REST API. Use when Canvas flows aren't triggering correctly, segments not capturing the right users, Currents data not streaming to your warehouse, Braze API returning errors, or stuck migrating from Appboy. Do NOT use for building prospect lists (use /sales-prospect-list), designing outbound cadence strategy (use /sales-cadence), cross-platform deliverability (use /sales-deliverability), transactional email strategy (use /sales-transactional-email), push notification strategy (use /sales-push-notification), in-app messaging strategy (use /sales-in-app-messaging), or email marketing strategy (use /sales-email-marketing).
Pre-sales-call intelligence composite. Deep dives on the person AND their company before a sales call, then maps findings to your product to generate talking points, objection prep, and a call strategy. Goes beyond generic attendee research — this is sales-specific intelligence that helps SDRs, AEs, and founders walk into calls with a plan. Tool-agnostic — works with any CRM, research source, and calendar.
Groove.cm platform help — GroovePages, GrooveFunnels, GrooveSell, GrooveMail, GrooveAffiliate, GrooveMember, GrooveVideo, GrooveWebinar, GrooveBlog, GrooveKart, GrooveProof. Use when a Groove module isn't working right, GrooveMail emails aren't sending, GrooveSell checkout is losing buyers, GrooveAffiliate commissions aren't tracking, GrooveMember content isn't accessible, or GrooveWebinar events won't launch. Do NOT use for general funnel strategy (use /sales-funnel), general email marketing strategy (use /sales-email-marketing), general affiliate program design (use /sales-affiliate-program), general webinar strategy (use /sales-webinar), general membership strategy (use /sales-membership), or general checkout optimization (use /sales-checkout).
In-app messages and content cards — onboarding, feature announcements, surveys, promotions, persistent content feeds. Covers strategy, design, triggering, and analytics across Braze, Iterable, Intercom, Pendo, Appcues, Customer.io, MoEngage, Whatfix and Chameleon. Use when users aren't completing onboarding, in-app messages have low engagement, not sure which in-app messaging tool to pick, feature announcements go unnoticed, employees aren't adopting enterprise software, or unsure whether to use in-app messages vs push vs email for a use case. Do NOT use for push notifications (use /sales-push-notification), email marketing (use /sales-email-marketing), live chat widgets (use /sales-live-chat), or cold outbound (use /sales-cadence). For Braze-specific help, use /sales-braze.
Mailshake platform help — campaigns, Lead Catcher, recipients, senders, webhooks, API, analytics, integrations, deliverability settings. Use when Mailshake campaigns aren't getting replies, Lead Catcher is missing leads, recipients aren't importing correctly, sender accounts keep disconnecting, integrations aren't syncing, or API calls are failing. Do NOT use for building prospect lists (use /sales-prospect-list), enriching contacts (use /sales-enrich), designing cadence strategy (use /sales-cadence), or cross-platform deliverability (use /sales-deliverability).
When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," or "breadcrumb schema." For broader SEO issues, see seo-audit.
Work through the findings from a second-brain audit in batches, correcting stale facts and converting locations onto the state/event schema, driven by the markdown file of findings the audit left behind. Use after running second-brain-audit, when someone wants to fix the rest of their notes rather than one page, asks how to take the audit forward, has a list of contradicted or unsupported claims to work through, or needs a notes folder converted in bulk rather than one page at a time
Systematically reviews code for SQL injection, XSS, SSRF, broken access control, cryptographic failures, and other common OWASP Top 10 vulnerabilities, providing vulnerable code examples and ready-to-use remediation guidance. Trigger this skill when users ask for a security review, vulnerability scan, or penetration testing assistance, or mention keywords like OWASP, SQL injection, XSS, code audit, or security checklist.
Expert guide for prompting ByteDance's Seedance 2.0 AI video model (text-to-video, image-to-video, first/last-frame, multi-reference, and multi-shot generation with native synchronized audio). Use when the user wants to write, improve, or debug a Seedance 2.0 prompt; plan a shot; work with reference images/videos/audio; animate a start frame or interpolate first-and-last frames; direct camera moves, motion, and cinematic style; generate dialogue, sound effects, or music; keep a character consistent across shots; or understand Seedance 2.0's capabilities, specs, API model IDs, limits, and access routes (Dreamina, Volcano Ark, BytePlus, fal.ai, Replicate). Triggers on "Seedance", "Seedance 2.0", "ByteDance video model", "Dreamina video", "seedance prompt", "reference-to-video", "first and last frame video".
Build evidence-labeled semantic cores for SEO, LLM-readable architecture, and site information design. Use this skill when the user asks for semantic core, query clusters, search intents, audience segments, entity/topic maps, language or locale priorities, competitor/source evidence, pillar-topic planning, or a structured handoff before URL architecture and internal linking. It must mark unknown search volume, difficulty, and ranking data as unknown instead of inventing metrics.
Build an evidence-labeled semantic core and crawlable site structure from keyword harvests, existing content, or user-provided search-demand data. Use before SEO/LLM site architecture, concept prototypes, paid traffic planning, IA, or public-site redesign decisions.
Apply Semantic Versioning 2.0.0 (semver.org) to decide version bumps, validate version strings, and compare version precedence. Use whenever a task involves choosing the next version number, judging whether a change is a MAJOR/MINOR/PATCH bump, checking that a string is a well-formed version, ordering versions by precedence, or building a pre-release or build-metadata version. Often used as a building block by release, changelog, and publishing workflows — trigger whenever version numbers are being reasoned about, even if "semver" is never said.
Comprehensive SEO footprint analysis. Catalogs all content, pulls real SEO metrics (via Apify Semrush/Ahrefs scrapers or free web search probes), runs competitor analysis, builds topic/keyword and content-type gap matrices, and produces a prioritized recommendations report. The complete SEO audit for any company.
SEO content brief creation with keyword research, search intent analysis, and content structure. Covers SERP analysis, heading hierarchy, word count targets, and internal linking strategy. Use for: content briefs, SEO writing, blog strategy, content planning, keyword targeting. Triggers: seo content brief, content brief, seo brief, keyword research, search intent, content strategy, blog brief, seo writing, content planning, keyword targeting, serp analysis, content outline, seo article, blog seo
Create SEO content briefs for SaaS, apps, developer tools, utilities, marketplaces, games, and product-led websites across search intent, topic clusters, SERP differentiation, outline, internal links, conversion path, schema, freshness, and evidence. Use when planning content that should rank, convert, and support product positioning without becoming generic keyword stuffing.
Expert guide for Schema.org structured data and JSON-LD implementation. Use when creating schema markup, validating structured data, implementing rich results (FAQ, HowTo, Product, Article, LocalBusiness, Breadcrumb, Organization, etc.), troubleshooting rich snippet eligibility, or understanding Google's structured data requirements.
Load PROACTIVELY when task involves connecting external services or third-party APIs. Use when user says "add email sending", "integrate a CMS", "set up file uploads", "add analytics", or "connect to S3". Covers email services (Resend, SendGrid), CMS platforms (Sanity, Contentful, Payload), file upload solutions (UploadThing, Cloudinary, S3), analytics integration, webhook handling, error recovery, and credential management.
Configure which models pstack uses per role and at what reasoning budget. Detects your available models and writes an always-applied rule that overrides the skill defaults. Use for /setup-pstack, "configure pstack models", "pstack budget", or changing pstack's model choices.
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.