Skills
99,064 packaged capabilities and playbooks for agents. Install any of them with one command.
Development
Build NHCX (India's National Health Claims Exchange) payer communication into an existing HMIS: receiving payer queries, notifications and notes on a pre-authorisation or claim, replying with text and documents, and acknowledging notifications, with the embedded NHCX gateway it needs. Use when a hospital system must answer insurer or PMJAY queries over NHCX.
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.
Working with the redis-docs MCP server (search / fetch / ask at redis.io/mcp)—how its index is shaped and how to read what it returns. Use when those tools are available and you are about to look something up in the Redis documentation, or when a result is confusing—fetch returned one short section instead of a page, several hits share one url, ids look like #sec:w1, metadata.version reads 1.0.0, a search came back empty, or ask was rate-limited or said the docs do not cover it. Also covers what redis.io does and does not index
Drive the user's own running browser and ScriptCat from the terminal with the `sctl` CLI: list and organize tabs, windows, bookmarks, history, cookies, downloads and extensions; read and operate pages (accessibility snapshot, click, fill, screenshot, run JavaScript); inspect console errors and network requests; send raw CDP commands or hand a CDP endpoint to Playwright/Puppeteer; and view, search, install, edit, enable, run or delete ScriptCat userscripts and read their logs. Use this skill whenever the user wants something done or looked at in their real browser — "what tabs do I have open", "open this page and click…", "why is this page throwing errors", "which request is failing", "run my Playwright script against my logged-in browser" — or mentions sctl, sctl Browser or ScriptCat, even if they never name the tool. Not for ordinary front-end coding that does not touch the user's browser, and not for developing the sctl repository itself.
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”.
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.”
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.
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 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.
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.
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.
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.
Guides the agent through enabling R8 in a Capacitor Android app so that it meets the Google Play DEX code optimization requirement (at least 25% obfuscation, optimization and shrinking from February 2027 for apps with more than 10 MB of DEX code). Covers `minifyEnabled true` with `proguard-android-optimize.txt` in `android/app/build.gradle`, the `-keep @interface com.getcapacitor.** { *; }` rule that prevents the startup crash in R8 full mode, per-plugin keep rules, resolving R8 'Missing class' build errors via `missing_rules.txt`, building a signed release APK with the debug keystore, and verifying with logcat, `mapping.txt` and the `r8.json` file inside the app bundle. Use when Play Console reports a DEX code optimization finding, when a Capacitor app crashes on startup after enabling `minifyEnabled`, or when R8 fails the release build. Do not use for iOS, resource shrinking, Capacitor plugin projects, Capacitor version upgrades, or non-Capacitor mobile frameworks.
Group a scope of Issues into Waves that can be implemented concurrently without stepping on each other — estimate what each Issue touches, exclude the ones that need a human, and print launch lines. Use when the user has several prepared Issues and wants to know which can run in parallel unattended
Explains Git to someone with no prior knowledge using the analogy of a logbook aboard a ship and its copy in the harbor (Albatros's Git service, code.aufwind.sh). Gets the repo from the harbor, guides them through their first entries (Commit) with good notes, sends them to the harbor (Push), and checks that the copy arrives on the Albatros server at ~/projekt. Rules: main only, stage only your own files individually, never force-push. Use this skill for “Git,” “GitHub,” “harbor,” “commit,” “push,” “pull,” “Repo,” “what is a repository,” “save my changes,” “push rejected,” and “conflict,” and before committing anything for the person.
Runs shell commands in the background with a fire-and-forget approach and delivers progress notify turns every 2 minutes plus one notify turn to the agent session when each finishes, through the `agent-shell` command (a separate Bun project, installed to `~/.local/bin`). Use when a long command, build, test run or server must keep going without blocking the session, with the result read only after the completion notify turn arrives. Do not use for a quick command that finishes inside one turn.
Design and change UI through an interactive shell. Turn a spec and a low-fidelity sketch, or an existing component, into a high-fidelity mock.html in the project's own style, iterate on it with the user, then implement it. Alternatively, open the shell over the running app so the user can inspect, comment on and restyle real elements, with changes going straight into code and tests. Use when the user invokes /building-ui, asks to mock up a new component or UI element from a sketch, change a component through a mock, implement an approved mock, or review or change the UI of the running app.
核验 C 代码里的 MCU 寄存器写入是否与芯片 SVD 一致：外设、寄存器、位域是否存在；值是否超位宽；枚举是否合法；是否写只读位；是否访问前未开时钟；是否硬编码地址。按“报 / 未判定 / 通过”分桶输出，并可生成复查清单。Use when reviewing embedded C init code, register writes, or AI-generated firmware registers; verify register writes against a chip SVD. 关键词：寄存器核验、寄存器检查、AI 生成代码、驱动复查、初始化代码检查、对拍、register check、verify register writes。不用于：HAL/LL 结构体配置语义（会进未判定）、外挂器件命令（Flash、传感器）、时序正确性、通用代码风格、寄存器事实查询（用 embedded-register-lookup）。
Delegate implementation work to external coding-agent CLIs (OpenAI Codex `codex exec`, Google Antigravity/Gemini `agy -p`, or any harness with an adapter) instead of Claude subagents, so heavy coding burns other providers' quota while Claude acts as foreman — planning, briefing, reviewing diffs and verifying. Use when the user invokes /foreman, asks to “use codex/gemini/agy as workers,” “save Claude quota/limits,” or “let another model do the coding while you review.” Workers run in isolated git worktrees via scripts/dispatch.sh.
Make an app work with Siri's model in iOS 27.3 / macOS 27.3 / visionOS 27.3, including an app with no App Intents yet. Use for: exposing intents to Siri as tools with @AppIntent(.tool) / ToolIntent, including @AppIntent(.tool, schema:); letting the model write parameter values with @AppEntity(.generable) / GenerableEntity; describing entity properties for Siri with @Property description: and hiding them with visibility: .internal; adding a Skills.skillsbundle with SKILL.md files that give Siri context for the app's tasks; running sirimetadataanalyzer (the Siri Metadata Analyzer) and fixing its findings; build errors from these macros; and titles and descriptions Siri's model reads. Also for 'make my app work with Siri', 'Siri AI', and 'Apple Intelligence'. For testing how Siri uses the app, use siri-evaluations. For general App Intents practice, use app-intents-specialist. For other iOS 26 / 27 App Intents APIs, use app-intents-whats-new-27.
Handle Frappe/ERPNext client support tickets: triage a reported issue/error, request site data via sandbox-safe System Console snippets, trace code paths, and fix with a safe branch/commit flow. Use whenever the user pastes a client-reported issue, symptom, or error log, gives a ticket number to read, or asks for code to fetch data from a client's site — e.g. "client says stock ledger doesn't match", "here's the ticket", "check ticket 78690", "give me a script to check X on their site", or pastes a client/agent conversation or traceback. Also use to refresh context from the latest communication — "check the latest client reply", "any new reply on the ticket", "refresh the thread"
Otimiza qualquer landing page ou aplicação web (React, Vite, Next.js, HTML) para atingir nota máxima (98-100) no Google Lighthouse 13 em Performance, Accessibility, Best Practices, SEO e Agentic Browsing, aplicando técnicas avançadas de SEO, AEO (Answer Engine Optimization) e GEO (Generative Engine Optimization para ChatGPT, Perplexity, Claude e Gemini). Use quando o usuário pedir para melhorar SEO, AEO, GEO, ser encontrado por IAs/buscadores, criar llms.txt/ard.json ou bater nota 100 no Google Lighthouse.
Use when a factory run must post its changes — check out the run branch, commit a step's allowlisted paths, push only that branch, and open or reuse one draft MR/PR with milestone/assignee ownership. Also the shared home for factory run contracts (executor, tracker integration, lanes, brief and provider templates).
SSoT design draft: clarify the objects, permitted changes and invariants, and separate architectural and business responsibilities before writing the formal VDM. Read ssot first, then this skill; use for drafting or restructuring a design, not for implementing, checking or reviewing specifications.
Build two-way Google Calendar sync for a booking or scheduling app: hosts connect their Google account with OAuth, events on the calendars they choose block their availability, kept current by push notifications and a renewal cron, and confirmed bookings are written to their calendar as events, with Google Meet links when asked. Use when: (1) an app with bookings, appointments, classes or shifts must respect staff's Google Calendar busy time or put bookings into it, (2) an existing calendar sync shows phantom busy time, missed or duplicate events, group sessions blocked after the first booking, sync that stopped without an error, or users stuck after revoking access, (3) the user mentions: Google Calendar integration, two-way calendar sync, connect Google Calendar, busy time, free/busy, events.watch, push notifications, X-Goog-Channel-Token, channel renewal, calendar.events scope, refresh token, invalid_grant, offline access, PKCE, Google Meet link, conferenceData, extendedProperties, hangoutLink. Carries a dependency-free Google client on fetch, a pure busy-time mapper and diff, single-flight sync, idempotent booking events, make-before-break channel renewal, derived health per calendar, Firestore and Supabase stores, and a 32-test node:test suite run under four process time zones. Next.js App Router route handlers, with an Express adapter for other Node servers; storage, auth and the booking source are seams. Not Outlook or Microsoft 365 (microsoft-calendar-sync), not slot generation (time-slot-generator), not a calendar UI, not ICS feeds
Build two-way Microsoft 365 / Outlook calendar sync for a booking or scheduling backend over Microsoft Graph: hosts connect their Microsoft account with OAuth, events on chosen calendars block their availability (change-notification subscriptions plus a renewal cron), and confirmed bookings are written to their calendar as events, with Teams meeting links. Use when: (1) an app with bookings, appointments, classes or shifts must respect staff's Outlook busy time or put bookings into their Outlook calendar, (2) an existing Outlook or Graph calendar integration stops working an hour after connecting, never receives notifications, ignores vacations, duplicates events or loses its subscriptions, (3) the user mentions: Outlook calendar integration, Microsoft 365 calendar, Office 365 calendar sync, Microsoft Graph calendar, Entra ID app registration, Calendars.ReadWrite, calendarView, change notifications, Graph subscription, clientState, validationToken, lifecycleNotificationUrl, subscriptionRemoved, MSAL refresh token, AADSTS700082, invalid_grant, interaction_required, singleValueExtendedProperties, teamsForBusiness, showAs, isAllDay, mailboxSettings timeZone. Carries a dependency-free Graph client on fetch, a pure busy-time mapper that anchors all-day events to the mailbox zone, single-flight sync, booking events found again by an extended-property marker, in-place subscription renewal that replaces lost subscriptions, derived health per calendar, Firestore and Supabase stores, and a 43-test node:test suite run under four process time zones. TypeScript for Next.js App Router route handlers, with an Express adapter for any other Node server; storage, auth and the booking source are seams behind CalendarStore, authenticate and BookingSource. Not Google Calendar, not Exchange on-premises (EWS), not a calendar UI.
This skill should be used when the user asks to "create MongoDB model", "define Beanie document", "write MongoDB query", "create aggregation pipeline", "run database migration", "index MongoDB collection", or mentions Beanie, Motor, MongoDB documents, or async database operations. Provides MongoDB/Beanie ODM patterns for FastAPI.
This skill should be used when the user asks to "implement FSD", "use Feature-Sliced Design", "organize architecture", "structure project folders", "set up FSD layers", "create feature slices", "refactor to FSD", "add FSD structure", or mentions "feature slices", "layered architecture", "FSD methodology", "architectural organization", "views layer", "entities layer", "shared layer", "Next.js with FSD", or "Turborepo FSD structure". Provides comprehensive guidance for implementing Feature-Sliced Design methodology in Next.js applications with custom 'views' layer naming.
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.