Skills
96,770 packaged capabilities and playbooks for agents. Install any of them with one command.
Development
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 observable contract for a User Story so the TESTER and DEV can work in parallel without seeing each other: assemble the context package (HU + story ADRs + Tech Design section), define inputs, per-case outputs, errors, and non-negotiable names with the source of each line, list decisions the HU left open, and stop for human approval. Use when the LEAD takes a user story to build, or when asked to write, draft, or version the contract/spec of a user story
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
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.
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.
Writes, runs and debugs EventCatalog architecture fitness functions — TypeScript rules in `*.fitness.ts` files that check the documented architecture (ownership, naming, domain boundaries, dependencies, data access, schemas) and fail CI when it drifts. Turns an architecture rule described in plain language into a working fitness function, places it globally or beside the domain, system, service, message or data store it governs, runs `eventcatalog fitness check`, verifies the result, and wires it into CI. Use when user asks to "write a fitness function", "add an architecture rule", "enforce that every event has an owner", "check domain boundaries", "stop services sharing databases", "detect circular dependencies", "fail the build when the architecture breaks a rule", "run fitness checks in CI", or "why is my fitness function failing".
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
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
Install and configure a PostHog SDK in a repository you can read and edit, following PostHog's docs for the framework. Use when a user working in their codebase asks to add, install, or set up PostHog, product analytics, session replay, or a PostHog SDK. Covers finding the right docs page, installing the latest package, getting the project token and ingestion host from project-get, keeping them in the env file, server-side setup, identifying users, and verifying the change. If you can't access the user's code, as is common in ChatGPT on the web or Claude on the web, use installing-posthog-from-chat instead.
Lua best practices for FiveM resources built on ox_lib, the way Overextended structures its own resources. Use when reading or editing any .lua file or fxmanifest.lua, or when the user asks when to use require, lib.load or lib.loadJson, how to split a resource into modules, where config goes, or how to use cache, lib.onCache, lib.points, lib.callback or locales.
Use when creating or iterating on a project after the Make App requirements proposal is confirmed. Decide whether to generate the My Approvals navigation by default based on business entry, edit-and-save, or approval-processing capabilities. Also covers BPM, bpmDefinitionKey, approval creation fields, save and submit, submit and save, process status, and approval tags in detail titles. Handles generation conditions, runtime initiation configuration, saving and first initiation, and status display in business lists and details. Does not cover cancel/recall, installing the My Approvals npm package or implementing the task center, approval processing, approval history, the process designer, or Console approval management.
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.
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.
核验 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）。
Design and run a bespoke, auditable workflow for a task no narrower skill fits, such as a large migration, an ambitious multi-part change, or work the user reviews after stepping away. Scales rigor to the task, runs a hypothesis loop, and logs decisions. Use when the user asks you to figure it out, or for a large task no other workflow covers.
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.
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"
Make a bug in a TypeScript resource executable before fixing it, with a regression test that fails before the fix and passes after. Use only when the user asks for TDD, a failing test, or a regression test, or when the resource already has a test runner and the bug has an obvious cheap test target. Skip it when the test path is unclear, expensive or integration-heavy.
TypeScript best practices for FiveM resources and their NUI. Use when reading or editing any .ts or .tsx file or a .svelte file with <script lang="ts">, or when the user asks how to type net events, callbacks, exports, NUI messages or state bags.
Find why code is the way it is, through read-only investigators that search git history, PRs, issues and any docs or chat the agent can reach, then return a cited, confidence-weighted answer. Use when the user asks why something works this way, why a choice was made, where a number came from, or what a regression or postmortem traces back to, or when a skill such as architect calls for it.
Use GitLab from the terminal without registering an MCP server. Covers authenticating the zereight-mcp-gitlab CLI (PAT or OAuth device flow) and reading merge requests, diffs, discussions, issues, and pipelines. Use when the user asks about a GitLab MR/issue/pipeline and no GitLab MCP tools are available, or wants CLI-only setup.
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.
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.