Skills
100,928 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Use when a slice is scoped but not yet designed — run the pre-design research round and persist its evidence artefact — or when a consuming skill's staleness advisory reports drift. Produces a cited, verification-legended research.md that design and plan load-bear instead of recall.
Use when the user wants to prepare code for open-source release, create reproducible research artifacts, or structure a repository for publication. Triggers on phrases like "publish code", "open source release", "reproducibility", "research repository", "code release", or "prepare for publication".
Use when a pull request or merge request has review comments to inspect, address, or answer, whether from a person or an automated reviewer on GitHub, GitLab, or Bitbucket. This skill handles feedback already received; it does not perform a new code review.
Documentation consistency reviewer that checks alignment between code implementation and documentation. Use when user requests reviewing documentation vs code consistency, checking if README/docs are outdated, verifying API documentation accuracy. Applicable for (1) reviewing README vs implementation consistency (2) checking if docs/ directory content is outdated (3) verifying API/config documentation accuracy (4) generating documentation consistency reports. Trigger words include doc review, documentation consistency, check outdated docs, verify docs.
Use when orchestrating a code review workflow across multiple LLMs or agents, synthesizing review findings, producing checklist-driven fix scopes, applying selected fixes, running regression tests, independently verifying fixes, updating review status, or keeping code review process artifacts isolated under code_review/.
Review cryptographic implementations and protocol usage for misuse — weak primitives, nonce and IV handling, key management, authentication of ciphertext, randomness, timing side channels, TLS and JWT configuration, and password storage. Use when auditing code that encrypts, signs, hashes, or authenticates, or when assessing TLS and token configurations.
Reviews a technical design document or RFC adversarially in fresh-context read-only subagents, one per lens, (coverage, decisions, edge cases, consistency, risks, citations, scope) and returns one merged report with a verdict. Use when the user says "review this design doc", or when asked to review a design doc, RFC, or technical design. Not for code diffs; use reviewing-code.
Analyzes and updates the `FROM` base images, Node headers, Go toolchain, and `rpms.lock.yaml` files in rhdh, rhdh-operator, and rhdh-must-gather; pins plugin-catalog `builder.Containerfile` / `.nvm/` / `konflux.additional-tags`; and bumps overlays `versions.json` `node` on `main` or a `release-1.10` branch. Use for weekly base-image maintenance, a UBI or RHEL bump, an RPM lockfile refresh, asking "which base images are out of date", node-v*-headers.tar.gz, catalog builder FROM, builder PipelineRun BASE_IMAGES, catalog release suffix, overlays Node version, UBI minor skew inside a Containerfile, or an OpenShift clients `N-el9-beta` / `4.21-el9-beta` RPM 404
Resolves the environment the other RHDH skills start from and hands back one JSON document: which RHDH repositories are checked out and where — rhdh, rhdh-operator, rhdh-plugins, rhdh-plugin-export-overlays, rhdh-plugin-catalog, rhdh-cli, rhdh-chart, rhdh-local, backstage and the rest — which tools are on PATH, and the target RHDH and Backstage versions with the source that produced them. Also owns the `rhdh` CLI behind workspace status, worklogs, and todos. Use for RHDH orientation, "where is my rhdh checkout", "which Backstage version goes with RHDH 1.10", `rhdh status`, `rhdh doctor`, `rhdh config`, `rhdh workspace`, `rhdh log`, `rhdh todo`, and for the read-only context another RHDH skill needs before it starts. Read-only — implementation work belongs to the domain skill that owns the requested outcome.
This skill should be used when designing, running, validating, or auditing statistical experiments on personal or observational time-series data (health metrics, speech/text corpora, behavioral logs, diaries, n-of-1 self-tracking). It enforces pre-registration, exact permutation tests, FDR discipline, data-validation gates, adversarial code review, and cross-validation with external models. Triggers on "design an experiment", "test this hypothesis on my data", "is this correlation real", "audit these findings", "pre-register", "validate this dataset", or any n-of-1 / quantified-self analysis request.
Mines a session transcript, past agent sessions, or named sources such as PR review comments for durable learnings, then proposes approval-gated edits to skills, AGENTS.md, or docs and tracker issues. Use when the user says "retro", or when the user explicitly asks for a retrospective. Never infer from session end or friction.
Design a Rust public API — trait design, generics versus dyn, sealed traits, what is exported, and which changes break semver. Use when designing or reviewing a crate public surface, when choosing between a generic parameter and a trait object, when adding a trait method or enum variant to a released crate, or when the user asks whether a change is a breaking change.
Pick the concurrency model from the workload shape — rayon for data parallelism, scoped threads for borrowed stack data, channels for handoff, shared state last — and use the weakest correct atomic ordering. Use when writing or reviewing threaded Rust, when Mutex, RwLock, atomics, or manual Send/Sync appear, when a deadlock or data race is suspected, or when the user asks how to parallelize Rust code.
When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps.' Use this for any document or asset that helps a sales team close deals. For competitor comparison pages and battle cards, see competitor-alternatives. For marketing website copy, see copywriting. For cold outreach emails, see cold-email.
Builds automations connecting Qwilr to CRM and other tools via API, Zapier, or native integrations. Use when reps manually copy deal data into proposals, Qwilr and your CRM are out of sync, proposal status isn't updating in Salesforce or HubSpot, you want proposals auto-created when deals hit a stage, or webhooks aren't triggering on proposal views or acceptance. Do NOT use for writing proposal content (use /sales-proposal-page), designing reusable templates (use /sales-proposal-template), or interpreting engagement signals (use /sales-proposal-analytics).
Build slide decks and presentations for research talks. Use this for making PowerPoint slides, conference presentations, seminar talks, research presentations, thesis defense slides, or any scientific talk. Provides slide structure, design templates, timing guidance, and visual validation. Works with PowerPoint and LaTeX Beamer.
Comprehensive scriptwriting skill for creating engaging, natural scripts across all mediums including educational videos, podcasts, presentations, documentaries, and narrative content. This skill should be used when developing scripts for any spoken or visual medium, applying storytelling principles, educational scaffolding, and natural human speech patterns while avoiding AI writing clichés.
Turn a user-provided video into an Apple-style, scroll-driven website with smooth canvas video scrubbing, optimized WebP frame sequences, progressive loading, and responsive motion. Use for cinematic product reveals, landing pages, scrollytelling, image-sequence animation, and scroll-controlled video; also optimize generated frame assets.
【Internal suite skill · Users usually don’t need to call it directly in the full workflow; simply tell the orchestrator short-drama-director what you need, and it will route to this skill automatically】【漫剧老李 V7.5.0-SLIM suite · Subskill】Specialized engine for the asset-locking phase: extract three lists from the script (character appearance / props / settings) → produce according to material form (M0 appearance dossier paraphrase block / M1 image-generation prompts + image numbers + 《Material Patch Sheet》 · default / M2 batch image generation and locking), and manage spatial continuity of settings, single-instance locks for props, and crowd direction. This package does not hold images—the user generates them on external platforms; this engine must not request images or block downstream steps due to missing images. Trigger words: break down assets, asset extraction, asset catalog, image-generation prompts, character asset board, setting prompts, prop prompts, three lists, nine-grid setting image, character portrait, setting continuity, prop continuity errors, crowd direction, material form, patch sheet, I don’t have images. This skill is part of a suite; the complete workflow starts with the orchestrator short-drama-director.
[Internal suite skill · Users usually don’t need to invoke this directly in the full workflow; state your needs to the coordinator short-drama-director, which routes them here automatically] [漫剧老李 V7.5.0-SLIM suite · subskill] Director decision engine (storyboard selection criteria layer): situation mapping E01~E15 + 80/15/5 weighting mechanism + emotional anchor chart + A/B dual-state whitelist of composition pitfalls. Answers “what shot should this scene use?” and provides selection criteria for the storyboard engine. Triggers: situation mapping, what camera angle to use for this scene, emotional anchor, beat sheet, pitfalls, composition pitfalls, can we use a centered frontal shot, what shot should this use. This skill is part of the suite; enter the complete workflow through coordinator short-drama-director.
[Internal suite skill · Users usually don’t need to invoke this directly in the full workflow; state your needs to the coordinator short-drama-director, which routes them here automatically] [漫剧老李 V7.5.0-SLIM suite · subskill] Specialist engine for finished-video quality checks and continuity management: cross-shot/cross-episode consistency logs, editing transitions and Seedance 15-second segmentation gate, sound design templates, post-production music and sound design (BGM Cue Sheet/music search terms/AI music prompts/copyright checks), and automated output checks. **The consistency gate adjusts its judgment to the asset format** (M0/M1 compare against text records; only M2 performs image-level verification; this package does not hold images, so do not request images or make false verification claims). Triggers: review, quality check, continuity check, watch footage, shot-by-shot review, recheck after dialogue diagnosis, editing transitions, segmentation check, sound design, automated check, add BGM, post-production music, find music, Suno prompts, music copyright, asset format. This skill is part of the suite; enter the complete workflow through coordinator short-drama-director.
[Internal suite skill · Users usually don’t need to invoke this directly in the full workflow; state your needs to the coordinator short-drama-director, which routes them here automatically] [漫剧老李 V7.5.0-SLIM suite · subskill] Specialist engine for realistic live-action combat—designs action and produces Seedance 2.5/2.0 prompts for modern fighting, police chases, suspenseful assassinations, comedy fights, child-oriented fights, and small-group battles (1v2/1v3/2v2/3v3): R1 restrained realism mode, 11-link action dynamics chain, realistic combat move library (19 martial arts / 36 kicking techniques / 36 grappling techniques), three defensive states and large evasions, multi-person combat blocking, realistic force feedback, and compliance conversion. Triggers: live-action fighting, realistic combat, modern fighting, police chase, suspenseful assassination, comedy fighting, MMA, group battle, one against many, outnumbered fight. Suite members: coordinator short-drama-director (authority on system and feed formats) + sd-decision-engine (decisions) + sd-script-engine (scripts) + sd-asset-engine (assets) + sd-storyboard-engine (dramatic scene storyboards) + sd-combat-engine (general fight scenes) + sd-xuanhuan-engine (fantasy fight scenes) + sd-real-engine (realistic live-action · this skill) + sd-feed-engine (feeding) + sd-qc-engine (quality control).
【Internal suite skill · Users usually don’t need to call it directly in the full workflow; simply tell the orchestrator short-drama-director what you need, and it will route to this skill automatically】【漫剧老李 V7.5.0-SLIM suite · Subskill】Specialized engine for fantasy and xianxia fight scenes—generates fight-scene storyboards and prompts for fantasy cultivation, xianxia duels, supernatural powers, and high-energy Chinese animation: golden fight-scene granularity (2–3-second whole-second cuts, one action and one response per shot), two-way offense-defense power exchanges (preventing opponents from becoming punching bags), four spatial-closure protocols for finishing moves, a four-part scale kit and image geometry, 13 three-layer composite elements, a combined magic-and-martial-arts move library, and dual physical parameter libraries for realism and cultivation. Trigger words: fantasy combat, xianxia duels, spell clashes, ten thousand swords return to the origin, sword formations, magic formations, dharma forms, battles of gods and demons, ultimate finishing moves, xianxia cultivation. Suite members: orchestrator short-drama-director (authority for system locks and input format) + sd-decision-engine (decisions) + sd-script-engine (scripts) + sd-asset-engine (assets) + sd-storyboard-engine (dramatic-scene storyboards) + sd-combat-engine (general combat scenes) + sd-xuanhuan-engine (fantasy combat · this skill) + sd-real-engine (live-action realism) + sd-feed-engine (feeding) + sd-qc-engine (quality control).
Query and operate connected Google Search Console properties through NotFair MCP. Use for live GSC query or page performance, clicks, impressions, CTR, position, traffic changes, indexing status, URL inspection, sitemap reads or approved sitemap submission/removal, and Search Console MCP setup. Route full-site SEO audits to seo-analysis.
Run OWASP LLM Top 10 security assessments against live Agentforce agents. TRIGGER when: user asks for security testing, OWASP scan, red-teaming, penetration testing, security grade, vulnerability assessment, prompt injection test, data leakage test, excessive agency test, security posture check, or hardening recommendations. DO NOT TRIGGER when: user runs functional smoke tests or batch tests (use testing-agentforce); performs static safety review of .agent file content (use developing-agentforce Section 15); analyzes production session traces (use observing-agentforce); writes or modifies .agent files.
Every shot carries its own timecode and shows one visible change on a body. The dread comes from the chain — a look, veins, a bite, the next person — and the ending seals a door without settling anything. Use when the user wants a Seedance 2.5 / 2.0 video prompt for this kind of clip (Horror and suspense; 中文触发词: 恐怖悬疑短片, 恐怖, 悬疑, 惊悚), or asks how published cases of this type were prompted. Read references/cases.md before drafting.
The period feel comes from camera defects and one tiny everyday incident. Write the camcorder's autofocus hunting, exposure shifts and handheld shake as an explicit list, keep the story small, and the clip reads as a real old tape. Use when the user wants a Seedance 2.5 / 2.0 video prompt for this kind of clip (Early-2000s DV home video; 中文触发词: 早年 DV 家庭录像, DV, 家庭录像, VHS, 复古, 年代感), or asks how published cases of this type were prompted. Read references/cases.md before drafting.
One traveller moves through a place scene by scene, each scene carrying its own timecode, its own location and one short line. The polish is bought with film grain and golden-hour light. Use when the user wants a Seedance 2.5 / 2.0 video prompt for this kind of clip (Cinematic travel vlog montage; 中文触发词: 电影感旅行漫游, 旅拍, 城市漫游, 旅行), or asks how published cases of this type were prompted. Read references/cases.md before drafting
Provides comprehensive guidance for Selenium WebDriver including browser automation, element location, waits, and test frameworks. Use when the user asks about Selenium, needs to automate web browsers, write Selenium tests, or work with Selenium WebDriver.
Main senior UI/UX orchestration skill. Use this skill whenever the user asks to build, refactor, audit, critique, plan, or validate web app UI, SaaS dashboards, internal tools, landing pages, product pages, screenshots, Figma designs, Figma MCP workflows, design-to-code, code-to-canvas, design-system sync, Stitch/AI UI exploration, three-direction design exploration, cursor reveal effects, responsive behavior, accessibility, visual quality, senior UI/UX/SEO/LLM council decisions, wiki context gates, or UI skill-system workflows. Routes work to webapp-ui-skill, marketing-site-skill, ux-audit-skill, design-critic-skill, ui-ux-pro-max, stitch-design-bridge, senior-figma-orchestrator, cursor-reveal-hero, image-layer-alignment-validator, task-plan-v2-orchestrator, obsidian-wiki-ingest, and shared validation tools while enforcing local-first privacy, one central chair, no fake tools, evidence reporting, and visual verification.
Walk a user through deploying a self-hosted Sesame broker into their own AWS account. Use when the user says "help me onboard Sesame", "deploy Sesame to my AWS", "set up the Sesame self-host broker", or "install Sesame on our infrastructure". You handle prerequisites (AWS CLI + login), explain exactly what each value is and how to get it (with clickable links for the Google step), run an interactive dry-run to capture everything, summarize the inputs, then run the real deploy. Never ask the user to paste secrets into the chat — they type those into the CLI's hidden prompts.
Bring your own SIP trunk to Bolna (BYOT) for AI voice agents. Create a trunk with gateways, IP-based or user/password auth, UDP/TCP/TLS transport, optional SDES (SRTP) media encryption, add DID numbers, and wire them to agents for inbound or outbound calls. Use with Twilio Elastic SIP, Plivo Zentrunk, Telnyx, Vonage, Zadarma, DIDWW, or any standards-compliant trunk. Covers IP whitelisting (`13.200.45.61`), origination URI setup, and the classic SRTP-mismatch / UDP-fragmentation / TLS-without-SDES diagnostic flow.
Complete workflow for migrating an existing frontend application to SGDS web components. Use this skill when a user wants to migrate from another UI library (MUI, Chakra UI, shadcn/ui, Ant Design, Vuetify, Angular Material, Bootstrap, etc.) to SGDS, or asks how to start using SGDS in an existing project. Covers four phases: (1) scan the current frontend tech stack, (2) install and configure SGDS with font, foundation CSS, and utilities, (3) migrate tests (Path A: Vitest + Playwright, or Path B: patch existing Jest/RTL), (4) replace old styling systems with SGDS v3 utilities, plus a post-migration verification checklist. React fully supported.
Pitch your business idea to a Shark Tank-style panel of 5 Claude sharks who only want to say no. Each investor grills it with their three hardest questions, a founder Claude answers only from what you told it, then each investor decides IN or OUT with a practice offer and what would change their mind. Use when the user wants honest feedback on a business, product or side-hustle idea, says Claude thinks every idea is great, asks "would investors fund this", wants to practice a pitch, or says "pitch" or "shark tank".
Maintain the existing May Shorts teaching compositions using their legacy face-mode, scene-overlay, and karaoke-caption patterns. Use only when working on those examples or explicitly requesting this legacy scaffold. For new reels, Shorts, or short advertisements, use short-form-edit.
Design of satisfaction beats and face-slapping scenes for Chinese web novels. Use when the user wants to design face-slapping, hiding one's strength, showing off, comeback, revenge, or crushing the villain, or complains that the plot "isn't satisfying enough / is too bland / readers say there are no payoff moments". Produces a three-part payoff loop and a four-beat face-slap structure, and ensures payoff escalation without repetition.
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.