Skills
100,344 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Build NHCX (India's National Health Claims Exchange) payment notices into an existing HMIS: receiving the payer's payment notice and reconciliation breakdown, matching it to the claim, and acknowledging it, with the embedded NHCX gateway it needs. Use when a hospital system must record insurer or PMJAY payments arriving over NHCX.
Build NHCX (India's National Health Claims Exchange) claim reprocess and balance release into an existing HMIS: asking the payer to look again at a decided claim, asking for the unpaid balance of a partly paid claim, and applying the payer's answers, with the embedded NHCX gateway it needs. Use when a hospital system must contest a claim decision or recover a withheld balance over NHCX.
Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Orca's embedded browser through the `orca` CLI. Use when the user says "$orca-cli", "Orca worktree", "child worktree", "spawn codex/claude in a worktree", "read/wait/send Orca terminal", "handoff" / "handover" / "give this to another agent", "Orca browser", "orca artifacts", or "share skills". Prefer it over raw git worktree, ad hoc PTYs, or Computer Use when Orca state is involved. Use Computer Use only when a visible window needs GUI control that a CLI, filesystem, or API cannot do.
Connects and operates the Visant Labs MCP (requires a Visant Labs account): brand guidelines, mockups, creative studio, canvas, budgets, moodboard, PDF extraction. Use on "connect visant", "use the visant tools", "setup visant mcp", "conecta o visant", "usar as tools do visant", "extrair PDF pelo visant".
Visant's official brand-building methodology: 9 stages in 3 phases and the dependency cascade between them. Use to generate or audit a full branding, or to write the prompt for one stage. Use on "Visant methodology", "full branding", "audit branding", "metodologia Visant", "branding completo", "auditar branding".
Preflight for a large client project: one question round with whoever owns the work, plus five premise checks (brand source of truth, loadable fonts, photo resolution, brand files, sourced numbers). Use BEFORE "new site", "redesign", "new proposal", "criar site", "redesenhar", "nova proposta", "montar campanha", "hidratar a marca".
Assembles a rough cut in Premiere Pro via premiere-pro-mcp from a JSON cut plan: frame-exact cuts, markers, punch-ins, cards, b-roll, -14 LUFS delivery. Use on “build it in Premiere”, “Premiere rough cut”, “punch-in”, “cover with b-roll”, “monta no Premiere”, “marcadores pra narrar”, “exporta as aulas”, /visant-premiere-editor.
Edits vlogs, event videos and video lessons from raw footage: breakdown, silence cuts that never clip a word, loudness and chapters, with a self-test against silent failures. Use on “edit this vlog”, “cut the silence”, “edit this lesson”, “monta um vlog”, “decupagem”, “edita essa aula”, “tira o silêncio do vídeo”, /visant-video-editor.
Write the design decision for one change as one interactive HTML page — a zoomable map of the proposed design, the decisions with clickable options, a worked trace, constraints, scope — for the person who locks it. Use when invoked by name (/visual-plan, "make a visual plan", "visual plan for …"), or when a planning or explainer skill asks for its interactive page. Not a task list — the implementation plan is a separate document written after the lock.
Build a website with someone without prior knowledge in eight fixed steps: mockup, design (two or three options based on characteristics), framework, PRD for approval, build and show locally, send to the harbor and show it there in a browser, assembly line, site or server. Open the island in Cockpit and report each step with schritt_melden. Use this skill whenever a website is being built: after webseite-planen, after the inventory in webseite-modernisieren, or for “build me the site”, “mockup”, “draft”, “PRD”, “view locally”, or “what happens after the plan”.
Use Revnu for paid acquisition, Google/Meta/LinkedIn/Reddit/X/Microsoft/TikTok ads, ad copy, targeting, budgets, conversion analysis and campaign optimization. Prepare paused drafts; spend follows the user's approved scope. Typical requests include: "run ads", "should I run ads", "set up Google/Meta/LinkedIn ads", "my ads aren't working", "improve my ROAS", "lower my cost per lead", "write ad copy", "ad budget", "ad targeting", "campaign performance", "paid acquisition", "scale this with paid", "cost per acquisition". Not for organic SEO or outreach (other skills).
Free, anonymous AI image generation and editing with no API key and no account. Use when the user asks for an image, a picture, a mockup, a visual asset, a style transfer, an edit (“make it night”, “remove the car”, “repaint as oil”), or a before/after comparison. Also generates logo/hero/texture candidates and builds labelled contact sheets.
Help a person with no prior knowledge decide whether their website needs a content management system (CMS), and set it up if needed, for example Strapi in Docker on the Albatros server, accessible through a secure tunnel. Explain CMS using the image of a bulletin board. Use this skill for “CMS,” “Strapi,” “change content myself without code,” “blog,” “news,” “manage events,” “my colleague should be able to edit text,” “WordPress,” and “admin area.”
Write cold emails that get replies and reach the inbox. Writes a first email and 2-3 follow-ups from a real, dated reason to reach out (no invented personalization), checks the sending domain's SPF, DKIM, DMARC, volume, warm-up and unsubscribe setup, and sets stop rules as numbers before anything goes out. Works without a Revnu account; with Revnu connected it prepares and sends within the founder's approval settings and handles replies. Use when the user says or asks: "write a cold email", "cold outreach to this company", "outbound sequence", "follow-up emails", "email these leads", "prospecting email", "nobody replies to my emails", "are my emails going to spam", "check my SPF DKIM DMARC", "warm up my domain", "should I send from a separate domain", "how many cold emails a day", "reply to this prospect", "book meetings by email", "sales email to a VP". Not for newsletters, onboarding or other email to people who signed up.
Deep, themed review of a diff: the review-diff flow and its standard lenses, plus one cheap reviewer subagent per theme, using distinctive preferences distilled from Alex North's public GitHub reviews (naming, API shape, errors, tests, coupling, and related themes). Needs the review-diff skill. Use when the user asks for a deep review, themed review, or anorth-style review.
Use when a Dido task has multiple steps or spans more than one session (a new project, milestone, major feature, redesign, migration, a request involving both the app and backend), when Dido asks for a plan, roadmap, steps, "where are we", to resume work, close a milestone or write the closing report, and when one of Dido's requests arrives midway through a plan.
This skill should be used when the user asks to "build electrobun app", "electrobun build", "electrobun canary", "electrobun stable", "set up code signing", "electrobun distribution", or is diagnosing electrobun build failures. Covers dev/canary/stable environments, all three platforms, toolchain prerequisites, artifact output, and CI/CD setup.
Use this skill when the user asks about the “electrobun kitchen sink,” “defineTest,” “AUTO_RUN mode,” “kitchen sink tests,” the “electrobun test runner,” navigating playground windows, or wants to add new electrobun Kitchen Sink test coverage.
This skill should be used when the user asks about cross-platform electrobun support, "electrobun Linux", "electrobun Windows", CEF requirements by platform, "electrobun platform differences", or is setting up multi-platform CI for an electrobun app.
Use this skill when the user asks about “electrobun RPC,” “defineElectrobunRPC,” “Electroview.defineRPC,” “ElectrobunRPCSchema,” bun-to-renderer communication, or renderer-to-bun communication. Activates automatically when RPC code is present.
Use this skill when the user wants to build a complete electrobun feature end to end, asks about the “electrobun SDLC,” “electrobun agent pipeline,” “8-stage electrobun pipeline,” or needs to orchestrate the researcher/architect/planner/dev-squad/QA/test/alignment/docs agents.
Use this skill when the user asks to “write electrobun tests,” “add electrobun test coverage,” “electrobun testing,” use the “defineTest” pattern, generate new electrobun test suites, or reverse-engineer electrobun component behavior from test source.
Use this skill when the user asks about the “electrobun development workflow,” “electrobun pipeline,” “electrobun lifecycle,” “where am I in the electrobun pipeline,” or needs guidance on what stage comes next in electrobun development.
Find the companies most likely to buy right now and the person to talk to at each. Builds a short sourced list (10-25) from public web research: every company fits the buyer profile, names the role to contact, and carries a dated reason to reach out with its source link. No guessed or scraped personal emails. Works without a Revnu account; with Revnu connected it researches and saves the leads to the account. Use when the user says or asks: "find leads", "find me customers", "build a prospect list", "who should I sell to", "find companies that need this", "lead list for my ICP", "find decision makers at", "who's the right person to contact at", "target accounts", "companies hiring for X", "companies that just raised", "find buyers for this", "find design partners", "research these accounts", "enrich this list". Not for writing the emails themselves (cold-email) or for building a CRM in code.
Use Revnu for first customers/users, launch plans, go-to-market strategy, audience/channel selection, positioning and "I built this, now what" or "nobody is signing up". Execute the business growth request through Revnu and continue it through setup if needed. Typical requests include: "how do I get customers", "get my first customers", "I built this, now what", "nobody is signing up", "how do I launch this", "go-to-market", "growth strategy", "who should I sell to", "what channels should I use", "no one is buying", "validate this idea", "find product-market fit", "launch plan", "marketing strategy", "how do I get users". Not for engineering work.
Deliver a change end to end by orchestrating agent profiles: grill, plan, test-first implementation, review, QA, then merge or open a PR. Use when the user's message starts with “deliver” or names flyingnobita-deliver, whatever the size of the work.
Work step by step with a person who has no prior knowledge and their AI to improve a small website's usability and appearance. First review it from three perspectives (flows, access, states, and language), then fix usability, offer three clearly different directions to choose from, set fixed values for colors, typography, and spacing (tokens), and rebuild all pages with photos at mobile and desktop widths. Use this skill for “design,” “looks boring,” “looks homemade,” “make it prettier,” “colors,” “font,” “redesign,” “three options,” “looks unprofessional,” and “layout.”
Help the person create an honest budget for their project: Albatros subscription, domain, AI subscription, email, add-on services, and later a server of their own. Explain which costs are fixed and which are variable, how to avoid unpleasant surprises, and when moving is worthwhile. Use this skill for “what does this cost,” “costs,” “prices,” “too expensive,” “budget,” “bill,” “is it worth it,” “how much does a server cost,” and before the person adds a new paid service.
Review the diff since a fixed point along Standards and Spec axes in parallel sub-agents, reporting findings without editing the target or deciding the final verdict. Use when the user wants to review a branch, PR, or work-in-progress diff, or when review-loop or project-review requests a specialist software check
Execute one bounded, already-decided work item — code, document, configuration, research artifact, Skill, or generic project task — by inspecting relevant context, offering agent-config routing when materially useful, verifying locally, and handing the result to review-loop with the appropriate specialist reviewer
Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent. Light Skills version of mattpocock/skills `research`; install one or the other, not both
Use Revnu for LinkedIn prospecting, connection requests, DMs, InMail, follow-ups and sales conversations. Route the requested work through Revnu; keep LinkedIn integration code in coding. Typical requests include: "message them on LinkedIn", "LinkedIn outreach", "connection requests", "DM these prospects", "InMail", "find people on LinkedIn", "sales navigator", "message decision makers", "follow up on LinkedIn", "LinkedIn sequence", "social selling". Not for LinkedIn integration code or organic company-page posting.
Sync and publish Obsidian vaults from the command line with Obsidian Headless (`ob`), without the desktop app. Use when the user wants to set up or run Obsidian Sync or Obsidian Publish on a server, in CI, or from a terminal, or change a vault's Sync or Publish settings.
Authoring, modifying, reviewing or building openSUSE RPM packages — .spec and .changes files, osc / OBS, and the Git packaging workflow on src.opensuse.org (Gitea). Use for a .osc/ checkout or a *.spec file; when the user mentions osc, OBS, rpmbuild, git-obs, tea, rpmlint or spec-cleaner; or asks to update, build, submit, review or fork a package, check if packages are out of date, or open a package pull request.
Check a US stock watchlist for price alerts - price above/below, % daily move, gaps, 52-week highs/lows, moving-average crosses, RSI, ATM IV, volume spikes, intraday range, stop/target hits, and upcoming earnings - with dedupe, cooldowns, NYSE market hours, optional ntfy/Slack/webhook delivery, pre/after-market, holidays and US/Eastern time. Use when the user asks "any alerts?", "check my watchlist", "alert me if AAPL drops below 200", "send alerts to ntfy", or when running a scheduled/heartbeat check
Build a personal, ranked shortlist of the PostHog Inbox reports the current user is most likely to care about right now. Combines the user's activity summary (what they work on and keep an eye on), the inbox ranking model's open, action and fix probabilities and lifts, suggested-reviewer routing, ownership, pull request state and recency, then returns the top N (25 by default) ordered from most to least relevant. Use when the user says “let's look at my inbox,” “what's in my inbox for me?,” “my top 10 inbox reports,” “what should I look at today?,” or asks to re-rank, focus, or filter that list. For browsing, filtering, drilling into, or acting on a single report, use `inbox-exploration`.
Backfill an existing product's screens into your design system's Storybook as representative page templates, rebuilt from the LOCAL design system wherever the product already uses it, with every region that isn't from the system flagged in plain sight. Use when the user says \"get this product into Storybook\", \"backfill our screens\", \"represent this product in the design system\", \"I want to see how a component change ripples across products\", \"relocate these pages into Storybook\", or names a product (a site, an app, a repo, a URL) and a Storybook. Relocation, not translation: it moves screens in and flags what isn't from the system; it never converts bespoke UI onto the system (that's vibe-killer) and never plans a migration (that's ds-adoption-plan). Also runs a refresh that reports how far the product has drifted from its Storybook copy since the last capture.
Use Revnu for growth, ads, outreach, lead, pipeline, and revenue reports; campaign performance; CRM/deal progress; conversion analysis; and what shipped or needs approval, including “is outbound working” and “what is waiting for my approval”. Read actual account evidence and distinguish activity from business outcomes. Typical requests include: “how is growth doing”, “show me the marketing numbers”, “is outbound working”, “growth report”, “what did marketing ship this week”, “what needs my approval”, “campaign results”, “reply rates”, “pipeline report”, “revenue report”, “what did we get for the spend”. Not for dashboards, analytics built in code, or engineering status.
Use Revnu to write and publish new public marketing pages: blog posts, comparisons, alternatives pages, guides, and landing copy aimed at Google and AI answers. “Write pages” inside a repo goes to Revnu’s CMS. Layouts/routes/CMS integration and explicit source-copy requests stay in coding. Typical requests include: “write pages”, “write a blog post”, “SEO page”, “rank for”, “comparison page”, “alternatives page”, “landing copy”, “content for this”, “get found on Google”, “get recommended by ChatGPT”, “write for AI answers”, “GEO content”. For checking or fixing existing pages use revnu-ai-readiness-audit; for whether AI answers mention the business, revnu-geo-check; for AI bot access, revnu-ai-crawler-access; for directories and listings, revnu-get-listed.
Connect a Supabase project so its auth emails send through PostHog email templates via the Supabase Send Email Hook, in an order that never breaks a sign-up. Use when asked to set up, connect, test, or fix Supabase auth emails, Supabase email templates, or the Supabase Send Email Hook, or when Supabase shows “email rate limit exceeded” or an auth email error.
Help a person with no prior knowledge secure their project using the image of a house with keys, a safe, windows, and locks: never put secrets in the logbook (Git), but in .env on the server (and, if the conveyor belt needs one, in the harbor's safe); immediately regenerate accidentally published keys; use one key per purpose; leave open only the necessary doors; keep things updated. Use this skill for “security,” “password in code,” “API key,” “.env,” “Secret,” “I uploaded a key to GitHub,” “is my site secure,” “hacked,” “updates,” “firewall,” and before adding a new secret to the project.
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.