Skills
97,905 packaged capabilities and playbooks for agents. Install any of them with one command.
Development
Contextualizes the business of an existing system (brownfield) for AI-first work: builds the capability map (what the system does today), surfaces business rules hidden in code, and creates the business ↔ code glossary with the ARCH, all with evidence, then pauses for human approval. Use when the BA role starts on an existing system without a PRD or backlog, or when asked to document what a legacy system does, extract its business rules, or build a domain glossary
Contextualizes an existing repository (brownfield) for AI-first work on it: verifies how to start and test it, creates the CodeGraph index, reconstructs the actual layer map, documents inherited decisions as ADRs, assembles the pattern catalog (canon vs. legacy), the debt map and verifiable build rules, all with file:line evidence, then pauses for human approval. Use when the ARCH role starts on an existing codebase without a PRD, or when asked to contextualize, onboard, document, map or understand a legacy/brownfield repository before working on it
Find the mistakes agents keep repeating in this repo and make each one impossible. Try architecture first, then types, then a lint whose error names the fix, then a test, and write docs last. Prove each check fails on a real past mistake. Repeat this each time the operator corrects you. Use for /correct.
Debugs issues users encounter with Tuist-generated projects by reproducing the scenario locally, building Tuist from source when needed, and triaging whether it is a bug, misconfiguration, or something that needs team input. Use when users report generation failures, build errors after generation, or unexpected project behavior.
Work with the app's code in Dessn's cloud when there is no local checkout. Find a screen from the person's words, find the code behind it, explain how it's built, change it on a copy, look at the result, put it on a board beside the original, and undo, all through the Dessn MCP. Use when the user has no code locally (a PM or designer with Claude Desktop, claude.ai or Claude Code in an empty folder) and wants to understand, change or explore a screen of their Dessn project, such as "where does this text come from", "change the copy on the pricing page", "how is the empty state built", "make this friendlier and show me".
Bring the user's local UI changes onto the Dessn canvas. Push the files changed in their working tree to a copy of a Dessn frame, see the result in a real picture, and put the routes they changed on a page. Use when the user codes locally (Claude Code, Codex, Cursor on their own checkout) and wants their change on Dessn, "show my local change in Dessn", "push this branch's UI to the canvas", or "make frames of what I changed".
Guides day-to-day work in Tuist-generated Xcode workspaces, including generation, build and test commands, and buildable folders. Use when working in a Tuist-generated project or when users mention `tuist generate`, `xcodebuild test`, or generated workspaces.
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.
Use when studying a SaaS web product from the outside in order to rebuild, clone or copy it (ClickUp, Pipedrive, Notion, a CRM, a project tool), when documenting its UX, screens, components, data model, business rules or API through a browser the agent drives, when assessing what would block a clone from launching (permissioned integrations, regulation, certifications), or when an agent must explore a live SaaS account without damaging production data or notifying real people.
Prevent, detect, and repair AI coding slop and dirty engineering in repositories. Use for planning features, writing code, changing tests, reviewing pull requests, refactoring, hardening CI, debugging regressions, or auditing agent-generated changes. Enforces behavioral contracts, focused diffs, test integrity, repo conventions, security boundaries, and evidence-based completion.
Turn the changes in a git working tree into clean Conventional Commits: read the diff, run the repository's own check, stage by path, split unrelated changes into separate commits, write the message, and verify what landed. Use when: (1) the user wants to commit, save progress, record WIP or wrap up a finished task, (2) a working tree mixes unrelated changes that should become separate commits, (3) a change breaks existing usage and the release tooling must see it, (4) the user mentions: commit, commit this, commit my changes, save progress, WIP commit, conventional commit, commit message, git add, staged, untracked, BREAKING CHANGE, feat!, Co-Authored-By, pre-commit hook, "split this into commits". Carries the staging rules that keep secrets and build output out, the breaking-change markers that `bumpv` reads to choose a MAJOR release, the hook and amend rules, and a post-commit check that no attribution trailer landed. Any git repository and any stack; the repository's own check and documented conventions are the seam. Not a release tool, not a changelog writer and not a push or pull request flow
Look up MCU peripheral registers, bit fields, reset values, and addresses (based on CMSIS SVD), with sources and evidence labels for every finding. Supports address reverse lookup; register value decoding and write-value calculation; bit-field quick reference and bitmaps; interrupt number and NVIC enable hints; CMSIS-style macro generation; cross-chip and peripheral-level comparisons; address range queries; SVD quality checks; local chip inventory and environment checks; Markdown table output; and parsed-result caching. Use when the user asks about a register, bit field, reset value, peripheral base address, or interrupt number; wants to decode or compute a register value to write, generate register macros, compare register definitions across devices, or find or verify SVD files on the machine. Keywords: 寄存器、位域、复位值、SVD、外设地址、寄存器值、掩码、位图、中断号、IRQn、NVIC、宏定义、对比、整体对比、质量检查、SVD 位置、芯片清单、读改写、USART1->CR1、register、bitfield、mask、reset value、decode、interrupt. Not for: pin multiplexing, manual chapter search, errata lookup, or verifying register writes in code (use embedded-register-verify).
Align the current project's PRODUCT.md, DESIGN.md, GLOSSARY.md, and ARCHITECTURE.md after meaningful changes, and write the project Flow block on request. Use when the user says "update the docs", "sync the context", "keep the docs aligned", or "set up Flow here".
Merge a branch of Windows-first (and Android) work into the mac branch, making sure every change translates to macOS or is written down as not yet doing so. Use when the user asks to merge into mac, merge the mac branch, catch mac up, or bring Windows work over to mac. Follows merge-branch's review gate in full, then adds a mac-translation pass whose verdict for each change — translated, needs mac work, or deferred — is recorded in the project's platform catch-up tracker (CATCHUP.md unless the project keeps it elsewhere), so no Windows behaviour goes silently missing on a Mac.
Use the public `orca` CLI to operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, worktree comments, and the browser embedded inside the Orca app. Use when the user says "$orca-cli", "use orca cli", "Orca worktree", "child worktree", "cardStatus", "spawn codex/claude in a worktree", "read/wait/send Orca terminal", "terminal send", "full handoff", "handover", "give this to another agent", "another worktree", "Orca browser", "orca artifacts", "share HTML/Markdown", "public artifact link", or "control the browser inside Orca". Prefer this over raw `git worktree`, ad hoc PTYs, Playwright, or Computer Use when the task touches Orca-managed state. Use Computer Use for browser windows, webviews, or desktop UI outside Orca's embedded browser.
Initialize a new project from flow-next or flow-mono with verified setup, renamed identity, and an independent initial Git commit, while explore shapes the product. Use when the user says "start a Next.js project", "start a new project", or "start a monorepo".
Sync a repository's documentation with what its code actually says: versions, dependencies, commands, project structure and feature claims in README.md, CLAUDE.md, AGENTS.md and docs/, each verified against the manifest, lockfile, scripts and files before it is written, with human prose, tone and section order left as they are. Use when: (1) a dependency, framework or runtime version changed and the docs still name the old one, (2) scripts, Makefile targets or the directory layout changed, (3) a feature was added, renamed or removed and the docs may no longer match, (4) an agent instruction file tells agents to run a command that may not exist, (5) the user mentions: sync docs, update the README, docs are stale, docs out of date, outdated version in README, fix CLAUDE.md, AGENTS.md, package.json, lockfile, pyproject.toml, Cargo.toml, go.mod, "npm run lint" missing script, "docs: sync documentation with codebase state". Carries the ground-truth table per ecosystem, the rule for declared range against resolved version, the flag-don't-guess rule for unverifiable feature claims, and a three-part report of changed, verified and flagged. Works on any project type, Node, Rust, Python, Go or a repository with no manifest at all; the repository's own manifests and files are the seam. Not a changelog or version bump tool, not a doc writer for missing files, and not an audit of the code against the docs
Write the release descriptor and notes for the next release on a channel (stable, beta, nightly, or whatever the project names), following the project's own release-writing instructions. Use when the user asks for release notes, a changelog entry, a release descriptor, or “the next nightly / beta / stable.” Gathers what is published now and what this tree holds, lets the project's instructions choose the version and format, writes the file, and never publishes.
Researches evidence unavailable locally: external documentation, public repositories at specific refs, archives, and published dependency artifacts (JARs, source JARs, POMs, dependency graphs), reusing a persistent cache of Git clones and Maven artifacts. Use for library docs, upstream source and history, dependency source or metadata, or any question needing external evidence
Use when work arrives at the software factory at any lifecycle stage — a new request, an informational question, a CI failure on a delivered PR, review findings, a merge notification, or a reply to a factory question — and must be routed to the right factory skill, human gate, or follow-up context.
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.
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.”
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.
Publish the next stable release by the project's own stable process — check that the main branch is green, choose the version and write its notes (through write-release-notes), publish whatever platforms still go out by hand, then push the version tag once the user has the notes, watch the build and check what it published and which release is marked latest. Use when the user asks to release, cut, ship or publish a stable version, push a version tag, or invokes /release-stable. Stops at a red main branch or a missing instruction instead of guessing; never moves, deletes or force-pushes a version tag.
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.
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.
Explain how a resource or subsystem works, its runtime flow across client, server and NUI, and where things live, through read-only subagents. Use when the user asks how something works, where code should live or which layer owns it, or when a skill such as architect calls for it
Delete the comments in a diff that the code should make unnecessary, through a fresh read-only reviewer, then fix the code each deleted workaround comment was excusing. Use before a change goes to review, or when the user asks to strip comments from a diff.
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.
Sketch types, signatures and module structure before writing code, from several candidate designs on different models, then implement against the chosen sketch. Use when the user asks to architect or design something, or when a skill such as figure-it-out calls for it.
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.
Implement and debug research code, select suitable codebases, reproduce baselines, map mechanisms into model architecture, and optimize training from measurements. Use for 科研编码, 论文复现, codebase选型, 模型实现, 训练调试, 显存/吞吐优化, and research dependency conflicts. Experiment protocols belong to designer; campaign coordination belongs to orchestrator.
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.