Skills
99,448 packaged capabilities and playbooks for agents. Install any of them with one command.
Development
Build a voting/poll dApp on Midnight Network using the Kuira Android SDK — Compact smart contract with create/cast/close circuits, passkey-derived identity, embedded wallet, Compose UI, reactive ledger reads via observeLedger(), and on-device ZK proving. Use when building a poll or voting dApp targeting Android.
Arco Design Vue UI component library reference for Vue 3 and `@arco-design/web-vue`. Use when the user asks to build Vue pages, create Vue UIs, write front-end code with Arco Vue, develop Vue dashboards or apps, or mentions Arco Design Vue, `@arco-design/web-vue`, `a-button`, `a-table`, `a-form`, `a-modal`, `a-select`, `Message`, or any Arco Vue component name. Covers installation, global registration, on-demand import, theming, internationalization, Vue 3 Composition API conventions, component props/events/slots, examples, forms, tables, modals, navigation, data entry, data display, feedback, and responsive layout.
Creating and maintaining CLAUDE.md project memory files and .claude/rules/ rule files that provide non-obvious codebase context. Use when (1) creating a new CLAUDE.md for a project, (2) adding architectural patterns or design decisions to existing CLAUDE.md, (3) capturing project-specific conventions that aren't obvious from code inspection, (4) organising instructions into path-scoped rule files.
Use when authoring a PRD (product requirements document) for a software or product project — turning a product idea into a comprehensive, plannable requirements doc. Guides the producer through the METHOD, not the outline: grounding the problem in evidence (jobs-to-be-done), defining measurable success metrics with guardrails, drawing a defensible MVP boundary, specifying functional + a non-functional taxonomy with numeric targets, writing testable acceptance criteria, keeping the problem→goal→metric→feature→AC chain traceable, naming dependencies, and surfacing risks + open questions — to a bar an engineer can plan milestones from. Also amends an existing PRD as a versioned, changelogged delta. Composes with a separate PRD template tool (the section structure) and a deep-research capability. Not for reviewing a finished PRD and not for authoring other document types.
Receive and verify Anthropic Claude Managed Agents (CMA) webhooks. Use when setting up Claude Managed Agents webhook handlers, debugging signature verification, or handling agent session and vault events like session.status_idled, session.status_terminated, session.thread_created, vault.created, or vault_credential.refresh_failed.
Code review checklists, PR review patterns, feedback techniques, and review automation. Use when user asks to "review this code", "code review checklist", "PR review template", "review best practices", "write review feedback", "review this PR", "how to give feedback on code", "PR too large", "split this PR", "review turnaround time", "automated code review", "CODEOWNERS", "pair review", "when to request changes", "code review tool", "review security", "design review", "performance review", "test coverage review", or any code review and feedback tasks.
Within an isolated scope, implement a confirmed Comet GitHub Issue or review blocker through its owning Native or Classic workflow, risk-matched tests, generated Runtime checks, and careful delivery. Use when the user explicitly asks to fix a verified Issue or PR problem.
Use when building notifications with Courier across email, SMS, push, in-app inbox, Slack, Teams, or WhatsApp. Covers transactional messages (password reset, OTP, orders, billing), growth notifications (onboarding, engagement, referral), multi-channel routing, preferences and topics, reliability and webhooks, journeys (multi-step notification sequences via API), template CRUD and Elemental content, routing strategies, provider configuration, the Courier CLI and MCP server, and migrations from Knock, Novu, or other notification systems.
Use this skill when wiring the DOCA SHA Offload Engine (an OpenSSL ENGINE) into an existing OpenSSL pipeline to offload one-shot SHA-1, SHA-256, or SHA-512 (EVP_Digest) onto DOCA SHA hardware without rewriting against doca-sha. Covers engine load mechanics (`openssl engine dynamic`, `set_pci_addr` ctrl, `-engine_impl`), the SHA-224 negative test that proves offload engaged, the message-size window where offload beats CPU SHA, and engine-vs-library selection. Trigger even when the user does not say "DOCA SHA Offload Engine" or "OpenSSL ENGINE" — typical implicit phrasings: "speed up openssl SHA on BlueField", "offload SHA without code changes", "is openssl using the accelerator or falling back to software", "prove DOCA SHA actually ran", "openssl dgst hashed but I'm not sure it was offloaded". Refuse and route elsewhere for new SHA pipelines (use doca-sha), MD5 / SHA-3 / SHA-224 / HMAC-SHA offload, incremental hashing via chained `EVP_DigestUpdate`, or OpenSSL PROVIDER authoring.
Build a time-lock vault dApp on Midnight Network — users lock unshielded NIGHT tokens in a Compact smart contract until a Unix timestamp, then the beneficiary releases them. Covers locker.compact (blockTimeGte unlock), Next.js frontend, 1AM wallet integration, low-level deploy/call, indexer polling, and ZK asset hosting. Use for token vesting, liquidity locks, escrow-style lockups, or any "lock until date" dApp on Midnight. Triggers: locker dApp, token lock, time vault, vesting schedule, lockup, release tokens, blockTime deadline, receiveUnshielded/sendUnshielded vault. Also use when debugging unlock timing, beneficiary auth, or extending the payment-dapp wallet/provider pattern.
Build a zero-knowledge loan application on Midnight Network — privately evaluate credit score, income, and employment tenure inside a Compact circuit with Schnorr attestation, record only loan outcomes on-chain, and wire attestation API + CLI + optional Next.js frontend. Covers zkloan-credit-scorer.compact (witness-derived identity, tiered eligibility, PIN migration, admin governance), Jubjub Schnorr verification, attestation provider registration, and low-level deploy/call via 1AM wallet. Use for private credit scoring, attested witness data, lending dApps, or teaching disclose()/witness patterns with off-chain trusted signers. Triggers: ZK loan, credit scorer, attestation API, Schnorr signature Compact, requestLoan, private credit score, loan eligibility tiers, PIN identity, zkloan. Also use when extending leaderboard-dapp or locker-dapp wallet/provider patterns to multi-service monorepos.
Build and refactor Flutter widgets, forms with stale-safe asynchronous validation and duplicate-submit handling, widget previews, component APIs, and UI state boundaries. Use alone for form behavior over existing services; add networking or concurrency only when their infrastructure changes, and route visual polish, responsive layout, navigation, animation, and performance to their specialists.
Use when designing multi-app Frappe architectures, deciding whether to split functionality into separate apps, or implementing cross-app communication patterns. Prevents monolithic app sprawl, circular dependencies between apps, and broken override chains. Covers multi-app architecture decisions, app dependency management, cross-app hooks, override patterns, when to split vs extend, shared DocType strategies. Keywords: architecture, multi-app, app splitting, cross-app, dependencies, override, extend, monolith, modular, how to structure frappe apps, when to split apps, app design, multi-app planning..
Use when receiving vague or unclear ERPNext/Frappe development requests that need interpretation. Transforms requirements like 'make invoice auto-calculate' or 'add approval workflow' into concrete technical specifications. Determines which Frappe mechanisms to use and maps to the full 61-skill catalog. Keywords: vague requirement, clarify scope, translate business need, technical spec, implementation plan, what does this mean, unclear requirement, translate to code, how to build this.
GitHub CLI workflows for repositories, issues, pull requests, actions, releases, projects, and API calls. Use when creating PRs, reviewing code, triaging issues, triggering workflows, publishing releases, managing projects, verifying attestations, or querying the GitHub API. Use for gh cli, github automation, code review, release management.
Manage glab CLI configuration settings including defaults, preferences, and per-host settings. Use when configuring glab behavior, setting defaults, or viewing current configuration. Triggers on config, configuration, settings, glab settings, set default.
Use when the user wants to learn Godot while building — teaching mode that explains the concept, the editor setup, and what to verify, instead of just delivering code. Triggers on "teach me", "explain as we go", "I'm learning Godot", "guide me", "walk me through", "help me understand".
P4 phase skill for Headless Ghidra selected function substitution. Use after P3 when an approved batch of functions should have metadata applied, be decompiled through Ghidra, and be recorded as per-function capture/substitution YAML.
Use this skill when diagnosing iOS app launch performance, startup regressions, first-frame readiness, or early responsiveness. Covers pre-main/dyld work, AppDelegate/SceneDelegate, SwiftUI App startup, launch orchestration, SDK initialization, and launch measurement. Do not use for general performance unless the code runs on the launch path.
Fixes GitHub issues from a provided issue URL. Creates a feature branch, implements the fix, updates docs and agent skill when needed, and opens a pull request. Use when given a GitHub issue link or asked to fix/resolve an issue and create a PR.
Juniors-focused React and TypeScript best practices. Use this skill when writing or reviewing code to enforce clear, consistent, and maintainable patterns across common scopes like React, TypeScript, styling, devtools, assets, and Git.
Use this skill when the user is working with LyteNyte Grid (@1771technologies/lytenyte-pro or @1771technologies/lytenyte-core), a headless React data grid. Activate for tasks like: installing or licensing LyteNyte Grid, configuring columns or rows, building cell renderers or editors, adding filters or sort controls, grouping or aggregating rows, pivoting, exporting to CSV/Excel/Parquet/Arrow, row selection, cell range selection, theming or styling, TypeScript GridSpec patterns, server-side or tree data, annotations, cell notes, marching ants, row/column animations, row banding, scroll flash suppression, and any PRO component (SmartSelect, PillManager, Menu, Dialog, TreeView, RowGroupCell). Also activate when the user describes grid problems without naming the package — e.g. "my rows won't group", "cells aren't editable", "add a loading overlay", "pin this column", "the filter isn't working", "how do I export this table", "select a range of cells", "copy cells to clipboard", "build me a grid", "animate rows", "highlight cells", "add a note to a cell".
Modernize removed or discouraged MATLAB functions and patterns. Use when the check_matlab_code MCP tool reports that a function "is not recommended", "will be removed in a future release", or "has been removed" — at any severity (info, warning, or error) — when migrating legacy code, or when replacing removed or discouraged APIs with current equivalents. Also applies to discouraged patterns Code Analyzer does not flag (containers.Map, bsxfun, str2num, eval, clear all) and to removed or discouraged functions such as trainNetwork, csvread, xlsread, datenum, guide, svmtrain, ltln2val, webmap.
Understand Microsoft technologies by querying official documentation. Use whenever the user asks how something works, wants tutorials, needs configuration options, limits, quotas, or best practices for any Microsoft technology (Azure, .NET, M365, Windows, Power Platform, etc.)—even if they don't mention "docs." If the question is about understanding a concept rather than writing code, this is the right skill.
Automatically prepare a complete Midnight development environment — Compact compiler, PATH, Docker, proof server, and VS Code extension. Use before building, compiling, or deploying any Midnight application when tooling is missing. Triggers: "set up Midnight", "install Compact", "proof server", "compact: command not found", "environment setup", "first time Midnight dev".
Use when moving a Node.js, npm, Yarn, pnpm, or Bun project to Deno, or when adopting Deno incrementally in an existing JavaScript or TypeScript codebase. Covers using Deno as a drop-in package manager, running existing package.json scripts, CommonJS versus ESM, node_modules layout, lockfile migration, permissions, whether to adopt the built-in toolchain, and per-tool command equivalents.
Use when writing or changing any class, object, function, property, or constant in a multi-module Android/Kotlin project (settings.gradle(.kts) includes more than one module — :app, :core:*, :feature:*, :data, etc.). Symptoms — a top-level declaration left at Kotlin's default public visibility; an implementation class, mapper, helper, constant, or UI-state holder reachable from another module though only used within its own; reaching for public "because the caller needs it"; "should this be public or internal?".
How to drive Muxy 2 from a shell with the `muxy` command — start terminals that keep running, type into them, read and wait on their output, and manage projects and Git worktrees. Use this when you are an agent running inside a Muxy terminal (or any script on the same computer) and want work to run in its own terminal instead of blocking yours, or to drive the desktop app's built-in browser.
Scaffold a new brooks-lint analysis skill so it passes `npm run validate` and `npm run evals` on the first try — generates skills/{name}/SKILL.md (with the mandatory "Do NOT trigger for:" clause and a Process section citing guide step ranges) plus skills/{name}/{name}-guide.md (sequentially numbered steps), then appends paired eval scenarios. Triggers when the maintainer asks to "add a new skill", "scaffold a skill", or "create a brooks-lint mode". Do NOT trigger for: editing an existing skill's content, adding a single eval to an existing skill, or authoring skills for some other plugin.
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards against regression. Use when asked to grow a static shell, fix a slow first paint or non-instant navigation, diagnose which Suspense boundary blocks useful UI, or add instant() regression coverage. Requires Next.js 16.3+ with Cache Components already adopted.
Comprehensive guide for NumPy - the fundamental package for scientific computing in Python. Use for array operations, linear algebra, random number generation, Fourier transforms, mathematical functions, and high-performance numerical computing. Foundation for SciPy, pandas, scikit-learn, and all scientific Python.
Working with the PageCraft API — block list, a single block, tags, publishing, syncing data source snapshots. Always use it when you need to "get", "publish", or "sync" something with the PageCraft server, and also when the orchestrator pagecraft-block references `pagecraft-api/scripts/*`. Call it via the `Skill(pagecraft-api)` tool, not via `Read .../SKILL.md`.
Creating and publishing PageCraft blocks and layouts from a description or a visual reference (screenshot or Figma link). Always use it when the user says "make a block", "new block", "create a block", "make a {hero/footer/...} from a reference", "make a layout", "make a site mockup", "make a wrapper for pages", "I need a header and footer around the content", and when editing an existing block or layout. The skill's first question asks whether it is a block or a layout. IMPORTANT — this skill is an orchestrator and hands work to sub-skills ONLY via the `Skill(name)` tool, not via `Read .../SKILL.md`.
Publishing a PageCraft block — writing the changelog (140 characters, in Russian), preflight-checking the remote version, calling publish-block, handling version conflicts. Use when the user says "publish", "upload", "send the block", "update the block", or when the orchestrator pagecraft-block points to "Phase 9 — Publishing". Call it via the `Skill(pagecraft-block-publish)` tool, not via `Read .../SKILL.md`.
PageCraft SSR blocks — bindingSlots, server data (product cards, favorites, cart, reviews), building stubs for preview, checking binding drift. Use when a block must show data from the server rather than from schema fields; when the orchestrator pagecraft-block points to "Phase 4.5 — Data Sources"; and for build-stubs / check-bindings. Call it via the `Skill(pagecraft-block-ssr)` tool, not via `Read .../SKILL.md`.
Setting up .env for PageCraft — the PAGECRAFT_AUTHOR (block author name) and PAGECRAFT_API_KEY (API access key) variables. Use on first run, on 401 errors from the API, or when the orchestrator pagecraft-block points to "Phase 1 — Environment". Call it via the `Skill(pagecraft-env)` tool, not via `Read .../SKILL.md`.
PageCraft Markdown block — the main content is edited in WYSIWYG as markdown and available via {{ content }}, while the schema defines only presentation settings (theme, size, spacing). Use when a block's main text is long and formatted, edited like an article/documentation; when the orchestrator pagecraft-block points to "Phase 5 — Implementation" for a markdown block. Call it via the `Skill(pagecraft-markdown-block)` tool, not via `Read .../SKILL.md`.
PageCraft schema block — fields in schema.json (text/image/color/object/array...), a Liquid template with {{ props.* }}, isolated JS, BEM styles. Use when creating a block with editor fields, editing template.liquid / schema.json / script.js, choosing field types and validating schema.json; always when the orchestrator pagecraft-block points to "Phase 5 — Implementation" for a schema block. Call it via the `Skill(pagecraft-schema-block)` tool, not via `Read .../SKILL.md`.
Executes automated project-wide refactoring with a focus on cross-file optimization. This skill should be used when the user asks for project-wide refactoring, cross-file simplification, consistency standardization across the codebase, duplication reduction, or invokes "/refactor-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.