Skills
99,064 packaged capabilities and playbooks for agents. Install any of them with one command.
Development
Manually migrates legacy `nango.yaml` Nango projects to Zero YAML TypeScript by generating `models.ts`, `index.ts`, package/tsconfig scaffolding, and wrapping legacy scripts in `createSync()`, `createAction()`, or `createOnEvent()`. Use when a Nango repo still has `nango.yaml` and needs manual Zero YAML migration.
Expert guide for using n8n-mcp MCP tools effectively. Use when searching for nodes, validating configurations, accessing templates, managing workflows, organizing workflows into folders, managing credentials, auditing instance security, or using any n8n-mcp tool. Provides tool selection guidance, parameter formats, and common patterns. IMPORTANT — Always consult this skill before calling any n8n-mcp tool — it prevents common mistakes like wrong nodeType formats, incorrect parameter structures, and inefficient tool usage. If the user mentions n8n, workflows, nodes, or automation and you have n8n MCP tools available, use this skill first.
Automatically generates HarmonyOS system design documents from PRD documents, including architecture design documents and functional design documents. Before generating, it analyzes the existing OpenHarmony code structure to ensure compatibility with the current architecture. Chapter 2 of the architecture design document must be competitor solution analysis, placed after the requirements background. Applies to user requests: (1) generate an architecture design document, (2) generate a functional design document, (3) generate design documents from a PRD, (4) create a system architecture design, (5) write a functional specification, (6) analyze the OH code structure. Keywords: architecture design, functional design, design doc, 竞品方案分析, OpenHarmony code analysis, 架构设计, 功能设计, 设计文档生成, OH代码分析, analyze codebase, competitor analysis
Open Orbit briefing skill — selected by the Orbit pipeline when GitHub is the user's only connected connector, or when the user explicitly scopes their daily digest to GitHub. Pulls the past 24 hours of PRs, review requests, issues, CI runs, and merges from the user's authenticated GitHub connection and renders them in a layout that mirrors GitHub's native Notifications + PR-diff visual language. This skill should not be triggered manually — it is invoked by Orbit's daily-digest scheduler against live GitHub data.
Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use when prioritizing features, synthesizing user research, writing requirement documentation, or developing product strategy.
This skill should be used when publishing a new or updated skill to the claude-skills-site Astro website. Use this skill for both adding new skills AND updating existing ones on the site. Triggers on "/publish-skill skillname", "add skill to site", "publish skillname to skills site", "update skill on site", "edit skill on site", "sync skill to site", "republish skill". Reads SKILL.md from the skills repo, generates MDX frontmatter and body, picks the right bundle, updates bundle skills array, and commits/pushes both repos. For existing skills, pass --update to preserve apothecary_name, hero_image, and activity data while regenerating the rest. A hero image is generated by default (pass --no-image to skip).
Use this skill when the user wants to get quick fix suggestions for an issue, "how to fix this issue", "where should I make changes", "quick-fix-suggestion", "suggest fix", "fix suggestion", "how to implement this issue", or before starting implementation to understand the scope of changes. This skill analyzes the issue content, locates relevant code in the repository, and suggests which files to modify with draft implementation plans. Requires Gitee MCP Server to be configured and must be run in a local git repository.
Rate limiting patterns for ASP.NET Core Razor Pages applications. Covers fixed window, sliding window, token bucket algorithms, and distributed rate limiting with Redis. Use when implementing rate limiting in ASP.NET Core applications, choosing between different rate limiting algorithms, or setting up distributed rate limiting with Redis.
Use when reviewing/judging a finished whole-system architecture document (+ its linked ADR files) to decide if an engineer can grasp the system and place a feature's TDD within it — an acceptance gate, not authoring. Judges a single-sourced 10-condition bar: boundary + external deps + concerns; components single-responsibility at whole-system altitude (not api-spec/data-model or feature-TDD detail); diagrams ⇄ narrative agree; every significant decision a standalone LINKED, immutable ADR (one per file, index in sync, supersede not edit); decisions traced + justified; NFR targets realized + tradeoffs named; cross-cutting (resilience/security/privacy/observability) addressed; ASRs covered; nothing fabricated, claims consistent with the code; amend delta-scoped. C4/arc42/ATAM/4+1 are aids judged by outcome. Emits exactly `VERDICT: approve|revise` (no false-revise on a thin doc). Not for authoring, the PRD, api-spec/data-model, a feature's TDD, or generic design docs/RFCs/standalone-ADRs (use design-review)
Use when building or fixing Roblox game UI/HUD in Luau — responsive layout across phone/tablet/desktop, ScreenGui panels, progress bars/meters, wallet/nav chrome, and the layout gotchas that bite (UIScale vs position, horizontal UIListLayout order, boolean-visibility bug, font glyphs, click-outside-close). Also the copy/clarity rules that make a HUD read well.
Conduct deep codebase research and produce a written report. Use when the user says “Research ...,” “start a research for,” “deeply investigate,” or “fully understand how X works.” Do not use for quick questions or simple code lookups
FIRST stop for Salla app development — load before generic brainstorming or planning. Use when building, configuring, or debugging a Salla app, when the task is broad ("build a Salla app", "add X to my app"), or when unsure which Salla skill applies. Dispatches intent to the right skill and maps each Salla Partners MCP tool to its capability. For a specific subsystem (OAuth, webhooks, settings, billing, publishing…), go straight to its skill. Twilight themes (a separate product) → salla-theme-builder.
Per-merchant settings for a Salla app. Use when designing a settings schema, registering the form, or reading/writing merchant config. Covers the salla_settings form + optional Validation URL, supported-features declaration (publish-blocker for communication apps), seeding defaults on install, value read/write (POST is a full replace — send ALL keys), reacting to app.settings.updated (activates the app AND is the storage source of truth), and context.settings in App Functions. Admin API → salla-api-core; lifecycle → salla-app-lifecycle.
Orchestrates AI-enhanced Scrum ceremonies and sprint coordination. Use when running sprint ceremonies, generating automated daily standups, engineering structured tickets, forecasting sprint capacity, or grooming backlogs. Use for fact-based standups, machine-readable tickets, predictive velocity, and backlog deduplication across GitHub Issues, Jira, and Linear.
Enforce semantic line breaks in Markdown specification prose. Use this whenever creating or editing specs, requirements, ADRs, README-style specification docs, or Markdown under specs/ or docs/, especially when paragraphs would otherwise be written as long wrapped lines. Apply it for AI-written specs and for review/cleanup of existing spec prose so future one-word edits produce small, readable diffs.
Debug and fix a Sentry issue — find it (by link, ID, or search), pull full context (stack trace, breadcrumbs, trace, logs), optionally run Seer root-cause / autofix, apply the code fix, and resolve it via a `Fixes PROJECT-NAME-12A` commit/PR. Use when working a known error or hunting one down to fix.
Use this skill to GENERATE a new Stackbone piece from a clean idea through a guided interview: first decide what to build — a deep agent, a durable workflow, or a workflow-agent (a workflow that calls an agent) — then scaffold it with the stackbone CLI and interview the user surface by surface. For an agent you ask for its tools and its system prompt; for a workflow you ask for the input data and the output data (the inputSchema / outputSchema); then you walk the capability checklist ONE AT A TIME — do we need a database? human-in-the-loop? RAG? storage? an LLM call? a connector? prompts? config? secrets? a schedule? to call another agent? — and wire in only the surfaces the user actually needs. This skill DRIVES the interview and the scaffolding; it delegates the real code to the `stackbone` skill (SDK authoring) and the commands to the `stackbone-cli` skill. Trigger on requests like: build a new agent, scaffold a workflow, create a workflow that calls an agent, "I want to make an agent that …", "I need a pipeline that takes X and returns Y", start a new workspace piece, generate an agent with tools, kick off a new Stackbone project. For writing the SDK code itself use the `stackbone` skill; for the CLI surface use `stackbone-cli`; for triaging a failing run use `stackbone-debug`.
Use for per-entity usage-limit and spend-control work in Stigg Governance — enforcing usage limits over whatever hierarchy of sub-units a customer needs (the entity model is customer-defined, not fixed) — defining entity types with attribution keys, setting entity entitlements for a feature or credit currency, dimensional scoping, querying the governance tree, runtime enforcement, and moving v1-beta code to v1. Triggers include "per-entity budget", "per-team spend limit", "per-agent token cap", "cost center limits", "sub-customer limits", "entity type", "entity entitlement", "attribution keys", "governance tree", "budget enforcement", "scoped assignment", "v1Beta governance", "keep entities in sync", "re-parent entity", "CannotReportUsageForEntitlementWithMeterError". Skip for account-level credit grants / pools / ledger (stigg-credits), feature gating with no entity hierarchy (stigg-entitlements), or catalog modeling (stigg-pricing-modeling).
This skill should be used when writing or reviewing Swift code for iOS or macOS projects. Apply modern Swift 6+ best practices, concurrency patterns, API design guidelines, and migration strategies. Covers async/await, actors, MainActor, Sendable, typed throws, and Swift 6 breaking changes.
Use this skill when a user asks how to generate, integrate, or implement a Word‑like document editor in JavaScript (ES6) using Syncfusion. Trigger it for requests involving the Syncfusion JavaScript (ES6) Document Editor, JavaScript (ES6)‑based editor integration, document editing and formatting, comments and track changes, working with tables and images, managing headers and footers, applying document protection, and building end‑to‑end document workflows in Javascript applications.
Guide to implement and customize the Syncfusion WinForms ColorPickerUIAdv control. Use this when implementing color-selection interfaces with organized palettes (Recent, Standard, Theme), custom color groups, Office-style layouts, a 'More Colors' dialog, or runtime color additions in Windows Forms applications.
Guide to implement Syncfusion WinForms DockingManager control for Visual Studio-style dockable windows and layouts. Use this when creating docked, floating, or tabbed windows with advanced layout management. Covers dock states, auto-hide functionality, caption customization, and serialization in WinForms applications.
Guide for implementing Syncfusion SfListView control in Windows Forms for creating list-based UIs with data binding, grouping, sorting, filtering, and selection capabilities. Use when building applications with item collections, Explorer views, contact lists, or product catalogs with sortable/filterable lists. Covers data binding, checkbox lists, grouped lists, filtered lists, and rich data display for list interfaces.
Implement and configure Syncfusion TextBoxExt control in Windows Forms - an enhanced textbox with custom borders, themes, and advanced text features. Use when you need styled textboxes with Office themes, custom border colors, multiline text with overflow indicators, character casing, text alignment, or RTL support. Covers theme integration, border customization, multiline configuration, and replacing standard TextBox controls with styled alternatives.
Use this skill when a user asks how to generate, integrate, or implement a Word‑like document editor in WPF using Syncfusion. Trigger it for requests involving the Syncfusion WPF Document Editor, WPF‑based editor integration, document editing and formatting, comments, working with tables and images, managing headers and footers, applying document protection, and building end‑to‑end document workflows in WPF applications.
This skill should be used when a task explicitly asks for TDD, test-first development, or the Red-Green-Refactor cycle. It guides incremental implementation with concrete Red-Green-Refactor examples, including Effect service patterns with mock layers.
Configure authentication providers for TinyShip: Google OAuth, GitHub OAuth, WeChat login, SMS OTP, and email/password with verification. Use when the user asks to "add google login", "configure github auth", "set up wechat login", "add SMS login", "configure authentication", "add OAuth", or "add social login".
Custom Dockerized inference workers on Together AI's managed GPU infrastructure. Build with Sprocket SDK, configure with Jig CLI, submit async queue jobs, and poll results. Reach for it whenever the user needs container-level control rather than a standard model endpoint or raw cluster.
Deep reference for when the Motoko migration chain misbehaves — upgrade compatibility errors you cannot explain, migration files you cannot write, a first migration whose OldActor is non-empty, a project converted from legacy persistence, or a request to delete/remove the migrations directory or revert to inline (with migration = ...). Load only when the rules in migrating-motoko-actors do not explain what you are seeing.
Design, build, verify, and publish production-grade TypeScript SDKs as npm packages inside a pnpm monorepo. Covers workspace layout, public API and module boundaries, plugin extension points, branded types and library-tuned tsconfig, tsdown bundling (vs tsup/tsc-only/unbuild), package.json exports with dual ESM+CJS and isomorphic conditions (browser/workers/RN/deno), Turborepo pipelines, publint and @arethetypeswrong/cli verification, changesets pre-release mode, npm dist-tags (latest/next/beta/rc/canary), and the alpha→beta→rc→stable release lifecycle. Triggers on: build a TS SDK, extract core library, package.json exports, dual ESM CJS, tsdown config, tsup vs tsdown, publint, attw, changesets prerelease, npm dist-tag, beta to rc, canary release, pnpm workspace SDK, isomorphic SDK, tsconfig library, npm provenance, shipping a TypeScript library.
Use when the user needs to build or maintain design tokens, component libraries, theme systems, or Tailwind CSS v4 configurations with responsive patterns. Triggers: user says "design system", "design tokens", "component library", "theme", "Tailwind config", "dark mode tokens", "color system", building reusable UI components.
Convert one or more webpage/app UI screenshots into a high-fidelity responsive implementation, either as a standalone page or by adapting an existing frontend. Prioritize exact viewport matching, typography/icon audits, explicit spacing and colour matching, browser screenshot comparison, and repeated refinement until no obvious mismatches remain. Handle missing assets by using supplied files, generating missing raster assets with direct image_gen when available, preferably as extractable asset sheets for multiple related assets, or otherwise using placeholders plus a single copy-paste code block containing one standalone generation prompt per remaining asset.
Operates the git-agent CLI — atomic commits, init/config, and the code graph (event log + AST + co-change). Use it whenever the user wants to commit or set up git-agent; when you are about to modify a feature and need the files that move with it (graph impact); when you are changing a function and want its callers/callees (graph callers/callees); when you need a symbol's location or source (graph node/query); when deciding which tests to run after a change (graph affected); when a test broke and you want to trace the action that introduced it (graph diagnose); or when you need action history (graph timeline) or a file's rename-aware provenance (graph provenance). All graph queries are read-only and offline (no LLM, no API key); only commit and init --scope need a provider.
Volcengine Function Service: Use when users want to deploy a local frontend, Node.js or Python app, static site, or API service; create a serverless app from a template; connect an existing project to veFaaS; view its online URL; configure production environment variables, build or start commands, or ports; publish, roll back, invoke, or debug online functions; inspect logs, instance status, or resource configuration; pull or push cloud function code; create and manage sandbox instances; troubleshoot deployment or authentication failures, framework detection errors, missing gateways, and similar issues; call the veFaaS OpenAPI directly for advanced operations; get started with veFaaS and learn its concepts, capabilities, selection, or pricing; consult the official documentation in a terminal; or develop code using the veFaaS SDK or OpenAPI.
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.