Skills
101,323 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Move items only, reword nothing; realign a listing whose order has gone arbitrary (a list, table, catalog, sections, an enum) into a logical sequence under one stated principle. Nothing is added or removed. Use when the user names a listing, or a scope holding one, whose order no longer helps a reader follow the set, or when a pipeline the user invoked passes that scope on. Acts only inside that scope.
Fix code in a named change or file list so it matches the conventions its own repository already keeps: run the project's configured formatter and linter in fix mode through the project's own toolchain, then fix by hand what no tool decides (naming, import order, file layout, error style) toward the dominant pattern in neighbouring files, behavior preserved, and ask with counts where the repository keeps two competing conventions. Use for 'make this match the codebase', formatter or linter setup, naming consistency, or a style pass on a change under review. Acts only inside the change or files the user names.
Read one stated intent, pick and order the installed skills that serve it, show that order, then run the steps the session may run and stop where a person must act. Use when someone states a goal but does not know which skills serve it or in what order, asks which skills to use, or wants a job that needs several skills run end to end. Typing /paperthin lands here.
Split one onboarding recording into a multi-part video sequence sized and paced for embedding in separate onboarding drip emails: email 1 covers setup, email 2 the core workflow, email 3 an advanced tip. Each part is promoted to its own standalone project with a short animated framing card so it works whether or not the recipient watched an earlier email. Clueso does not send email or manage a drip sequence; it produces the video clips only, and the user wires them into their own email service provider. Use when the user says "split this recording into an onboarding email video series", "turn this into a multi-part email video sequence", "make short clips for our onboarding drip campaign", or "cut this demo into parts for our email drip".
Turns a screen recording into a searchable help-center article, built as a real, live article inside a Clueso project: a clear title, a one-line summary of what the reader will accomplish, numbered steps naming the real control and the resulting outcome, and supporting screenshots pulled from the recording (or a generated image standing in wherever a captured frame doesn't actually convey the point). The article is the primary deliverable; a polished companion video built from the same recording is optional and secondary here. Use when the user says "generate a help article from this recording", "turn this screen capture into a searchable doc", "make a knowledge-base article from this screen recording", or "write me a help-center article from this walkthrough".
From one screen recording, always produces both a polished video and a full step-by-step help article: two equal, always-built deliverables rather than one primary format with the other optional, with the article built as a real, live article inside a Clueso project. Use this instead of recording-to-help-article specifically when the team needs both formats by default. If the user already has an existing Clueso article, the finished video and written steps can be attached to and merged into that one instead of a new project. Use when the user says "turn this recording into a video and a help doc", "I need both a video and written steps from this capture, no matter what", "make a guide and a video from this recording, I want both every time", or "give me a polished video plus documentation from this screen recording".
Verify that cited references actually exist and that their metadata matches, using the runnable scripts this skill ships for CrossRef, Semantic Scholar, arXiv, and PubMed. Use when the bibliography must be checked against live sources rather than inspected locally: detecting fabricated or hallucinated citations, confirming that DOIs resolve, and matching title, authors, venue, and year against the record. Also covers the underlying verification principles and reference-audit best practices. For an offline hygiene pass over a .bib or .tex file, run citation-verifier first; for whether a real source supports the sentence citing it, run claim-source-verification.
When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy. Also use when the user mentions 'referral,' 'affiliate,' 'ambassador,' 'word of mouth,' 'viral loop,' 'refer a friend,' 'partner program,' 'referral incentive,' 'how to get referrals,' 'customers referring customers,' or 'affiliate payout.' Use this whenever someone wants existing users or partners to bring in new customers. For launch-specific virality, see launch.
Replace a help article's outdated screenshots with current captures at the same steps, keeping the article's text and structure untouched. Use when the user says "the screenshots in this article are outdated", "refresh the screenshots", "update the images in our help doc", "the UI changed and the article still shows the old design", or "swap in current screenshots".
Set up and operate Rekor — a headless system of record for AI agents. Use when: installing the `rekor` CLI, authenticating, creating a base, defining record_types, working in preview and promoting to production, managing config as code (rekor pull/push), upserting or querying records (Filter DSL or SQL), managing relationships, storing versioned files or attachments (incl. S3 mounts), configuring inbound webhooks, triggers, batch operations, or seed fixtures for agent evals, backing a record_type with an external API (external sources, executors), storing credentials in the secret vault, importing or exporting tool definitions across providers (OpenAI/Anthropic/Google/MCP), creating curated MCP Factory toolsets and Actions, scoping API tokens, modeling record_types and toolsets so LLM agents use them reliably, or interpreting any Rekor concept (base, record_type, record, relationship, preview/production, promotion, external_id).
Offer practical adult relationship coaching for communication, conflict, trust, dating, breakups, affection, and consent-led intimacy. Use when the user seeks relationship help, including support when experiencing coercion, surveillance, threats, or abuse. Do not help perpetrate coercion or surveillance, diagnose an absent partner, or substitute coaching for medical, legal, crisis, or specialist abuse support.
Full security audit for public repositories across 12 attack surfaces: git history, secrets, CI/CD, containers, dependencies, licenses. Triggers on: "push to GitHub", "make repo public", "open source this", "is this safe to push", "release audit", "secret leaks".
Turn one finished video into a channel kit - a captioned, resized social cut of the strongest 15–30 seconds, a looping GIF of the key interaction for newsletters and in-app embeds, and the embed-ready full version. Use when the user says "cut this for LinkedIn", "make a social version of this video", "turn this demo into a GIF for the newsletter", "repurpose this video for our channels", or "I need short cuts of this for socials and the changelog".
Design, exercise, and evidence graceful degradation, disaster recovery, and restoration behavior across systems and dependencies. Covers failure-mode analysis, RTO/RPO decision records, restore testing, game days, failover drills, data integrity verification, and recovery communication. Do not use for live incident command or incident response; route to site-reliability-engineering for those. Do not use for infrastructure implementation details; route to platform-engineering.
Clone an existing 16:9 Clueso video into a vertical (9:16) or square (1:1) canvas for Reels, TikTok, Shorts, or feed posts, then reflow every element (backgrounds, text, logos, cursors and spotlights) so nothing crops badly, floats off-frame, or points at the wrong spot after the resize. Use when the user says "repurpose this explainer as a vertical short", "turn this into a Reel", "make a TikTok version of this demo", "resize this for Instagram Stories", "give me a square version for the feed", or "I need this in 9:16".
Respond to Google, Yelp, and industry reviews in the owner's voice -- gracious on the 5-stars, masterful on the 1-stars. Handles the angry customer, the unfair review, the fake review, and the one that mentions a legal or health issue. Every response written for the thousand future customers reading it.
Use when reviewing/judging a published, consumer-facing API reference an integrating developer calls an API from — deciding if they can integrate from it. A gate, not authoring. Judges against a single-sourced 11-condition usability + contract-consistency bar: getting-started + auth reach a first call; every api-spec operation (incl. events/webhooks) is documented with purpose + typed params + a worked example + errors; errors first-class; rate-limits + pagination documented where applicable; versioning + deprecation/sunset stated; the reference is CONSISTENT WITH THE HANDED-IN api-spec (no drift, no fabricated endpoint — the load-bearing check); samples runnable; an amendment re-syncs to the changed contract. Emits exactly `VERDICT: approve|revise` plus actionable findings; approves a proportionally-sized reference, revises on a named gap. Not authoring it, not the end-user user-guide, not the developer-adoption guide, not the engineering api-spec (reviewing-api-spec).
Use when reviewing or judging a finished or amended developer guide — the adoption + integration narrative for a developer-tool product (SDK/library/CLI/framework/API platform). Decides whether a developer can install, integrate, and operate the tool from the guide alone. A gate, not authoring. Judges it against a single-sourced 14-condition adoptability + accuracy bar: a signposted start-here + a verifiable first success; concepts before recipes; how-tos cover the handed-in scenarios; samples runnable + accurate to the CURRENT tool (no fabricated/stale endpoints); LINKS INTO the api-reference, never duplicates it; Diataxis modes typed; a troubleshooting path; an amend reviewed delta-scoped. Emits exactly `VERDICT: approve|revise` + actionable findings; approves a guide meeting the bar (no false-revise on a thin one), revises only on a named gap. Not for authoring it, the end-user user-guide, the endpoint catalog (api-reference review), or engineering design docs (design-review).
Use when reviewing/judging a test plan / QA verification plan — deciding whether a tester can execute it and every behavior is covered. A gate, not authoring. Judges it against a single-sourced 10-condition bar: every handed-in upstream behavior (feature-spec/api-spec ops+errors, else PRD) has >=1 TRACEABLE case; functional levels fit; entry/exit testable (coverage floor + open-defect threshold); environments + test data specified; each case has preconditions + steps + observable result (a metric-threshold-on-a-dataset for ML) + traces-to; the catalog is RISK-WEIGHTED (coverage gap, padded/thin, OR combinatorial blow-up = a finding); each warranted non-functional type (perf/security/WCAG 2.2 AA/compat/i18n) carries a target; an amend is reviewed delta-scoped; nothing fabricated. Emits exactly `VERDICT: approve|revise` + actionable findings; approves a proportionally-sized plan, revises only on a named gap. Not for authoring it, the release runbook, design-review, or the test scripts.
Revolut X account, transaction, order, and trade queries. Use when the user asks to “check my balances”, “sub-accounts”, “sub-account balances”, “transaction history”, “deposits”, “withdrawals”, “buys”, “sells”, “sends”, “receives”, “transaction details”, “transaction fees”, “view open orders”, “order history”, “TWAP order”, “order fills”, “my trades”, “trade history”, “trading volume”, “trade volume”, or runs revx account, revx transaction, revx order open, revx order history, revx order get, revx order fills, or revx trade commands
Scan a project and inventory what is available for QA work - project type, languages, frameworks, manual `*.test.md` cases, automated tests and automated references, and how Testomat.io is reachable (token, MCP, project settings). Use this skill whenever analyzing a codebase for test planning, detecting test frameworks, counting tests, or preparing for test automation. Specifically, when the user mentions "scan project", "what tests exist", "how many tests", "analyze codebase", "detect frameworks", "test matrix", or needs an inventory before a QA workflow.
Generate structured data markup (JSON-LD) for rich results, AI search visibility, and enhanced SERP features. Supports Article, FAQ, HowTo, Product, Review, LocalBusiness, Event, BreadcrumbList, Person, Organization, and more. Use when the user needs schema markup, structured data, rich snippets, JSON-LD, or wants to improve search appearance.
Teach a concept, mechanism, or process as an educational animation with labeled diagrams, step-by-step cause-and-effect scenes, and measured teacherly narration. Use when the user says "science-style animation", "educational animation about X", "explain how X works with a diagram video", "teaching video for this concept", "animate this process", or has a concept, system, or workflow they want taught visually to learners.
Plan authorized security reviews with threat modeling, architecture and dependency audits, and vulnerability classification. Use for scoped defensive security assessment. Do not use for offensive operations, unauthorized testing, or security control implementation.
Enforces Built for Shopify (BFS) quality standards during Shopify app development. Use when building, reviewing, or auditing Shopify apps for BFS compliance, or when the user mentions Built for Shopify, BFS, app quality, or app store requirements.
Keep a reviewable decision trail for long-running or unattended work: a TSV log with one row per decision (what, why, evidence, result). Local by default; commit it when a reviewer needs the trail to trust the result. Use for /show-me-your-work, autonomous or multi-phase runs, or work a human reviews after stepping away.
Signals scout for PostHog workflows. Looks at the workflows whose owner asked for suggestions, reads each email step's per-version delivery metrics, and proposes one concrete change a person can approve, filed through the workflows suggestions API. It files no report and emits no signal: the suggestion on the workflow page is the output.
Pipeline orchestrator that classifies incoming coding tasks and routes them through the correct combination of skills at the right depth. Implements two feedback loops: the inner loop (detect, verify, recover) runs within a session via plan-interview, intent-framed-agent, session-context, context-surfing, verify-gate, self-healing (active recovery on failure), simplify-and-harden, and self-improvement. The outer loop (inspect, encode, regress-test) runs across sessions via learning-aggregator, self-improvement, and eval-creator. pre-flight-check bridges the two by surfacing accumulated knowledge — past heals and learnings — at session start. Handles standard, orchestrated-batch, CI, and outer-loop pipeline variants. Does not replace individual skills; dispatches to them.
Audit and refine a skill repository, a single skill, a workflow framework, or an eval set. Covers design quality, context engineering, purpose fit, evidence discipline, and boundary clarity — the structural dimensions that assertion-based testing does not reach. When a target_repo is provided, continues into compatibility review, extraction, and integration planning. Complements skill-creator by providing deep design-level judgment after functional tests pass.
Use this skill whenever a user wants to create a presentation outline, slide deck structure, storyboard slides, or plan a deck for any context (talk, boardroom, email report). Also use when the user mentions "help me structure my presentation", "slide outline", "storyboard my deck", "presentation flow", "plan my slides", "key message for my deck", "pyramid principle for slides", "what slides should I include", or "help me tell a story with slides". This skill walks through a complete, interactive process in two phases: Phase 1 (setup → key message → storyboard) saves a slide-outline.md; Phase 2 (interactive per-slide copy drafting → polish) saves a slide-copy.md that is linked from slide-outline.md. Trigger even when the user only mentions a vague intent like "I need to present X to my team" or "help me put together a board deck".
Turn an uploaded slide deck (PPT) into a narrated video that doesn't feel like a deck: slide text rewritten into spoken narration instead of read aloud, slides that don't earn screen time cut or merged, motion added to the slides that matter, and clean transitions at section boundaries. Use when the user says "turn this deck into a video", "convert my PowerPoint to video", "narrate these slides", "make a video from this presentation", or uploads a deck and wants a video version.
Send transactional emails and SMS via SMTP2GO API. Covers authentication, /email/send and /email/mime endpoints, template management, attachments (base64/URL), webhooks for delivery events, statistics, and suppressions. Use when sending emails from Cloudflare Workers, building notifications, tracking delivery status, handling bounces. Prevents auth errors, attachment encoding issues.
Use when you need to locate and prepare already-approved customer evidence for a social campaign, profile, post, or sales-adjacent explanation. Trigger phrases include "find proof we can use", "what customer evidence supports this?", "mine testimonials", "turn these outcomes into social proof", and "which quote backs this claim?". Do not use this to fabricate testimonials, imply endorsement, expose private customer information, or turn a single anecdote into a performance promise; use social-listening for broad feedback patterns and positioning-audit for the message itself.
GitHub Spec-Kit integration for constitution-based spec-driven development. 7-phase workflow (constitution, specify, clarify, plan, tasks, analyze, implement). Use when working with spec-kit CLI, .specify/ directories, or creating specifications with constitution-driven development. Triggered by "spec-kit", "speckit", "constitution", "specify", references to .specify/ directory, or spec-kit commands.
Consolidate duplicate files or directories into one canonical home after approval, held as an identity by this machine's filesystem: hardlink, symlink, junction, or bind mount, with bytes, ACLs, owner and mode, named streams, xattrs and kept timestamps preserved. Use when consumers need the same bytes at several paths and textual references cannot serve them, when asked to hardlink, symlink, junction or bind-mount duplicate copies, or to dedupe identical files or trees on disk without breaking their readers.
Contextual help and onboarding for the swain skill ecosystem. Use when users ask about swain — what skills exist, how to use them, what artifacts are available, how workflows connect, or when they need a quick reference. Also invoked after swain-init to orient new users. Triggers on: 'how do I...', 'what is...', 'help', 'what can swain do', 'show me the commands', 'I'm confused', 'where do I start', any question about swain skills, artifacts, or workflows, and after project onboarding completes.
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.