Skills
96,981 packaged capabilities and playbooks for agents. Install any of them with one command.
Development
Winston - versatile logging library for Node.js with multiple transports, custom formatting, and log rotation. Supports structured logging, custom levels, and enterprise integration. USE WHEN: user mentions "winston", "node.js logging", "multiple transports", "log rotation", asks about "how to log to multiple destinations", "rotate log files in Node.js", "custom log formats" DO NOT USE FOR: Pino logging - use `pino` instead, Python logging - use `python-logging` instead, Java logging - use `slf4j` or `logback` instead
WordPress plugin development fundamentals: plugin headers and file structure (simple, OOP, or PSR-4 with Composer autoload), activation and deactivation hooks, actions and filters, the Settings API, custom post types and taxonomies, REST API endpoints, admin-ajax handlers, and $wpdb database access with prepared statements. Emphasizes security: nonces, capability checks, sanitization such as sanitize_text_field, escaping such as esc_html, and preventing SQL injection, XSS, and CSRF. Use when creating or structuring a WordPress plugin, registering post types or taxonomies with register_post_type, building admin settings pages, adding REST or AJAX endpoints, querying the WordPress database safely, auditing plugin security, or debugging plugin activation and deactivation problems.
Build long-running .NET background services with `BackgroundService`, Generic Host, graceful shutdown, configuration, logging, and deployment patterns suited to workers and daemons. USE FOR: background services; scheduled workers; hosted services; worker extraction; graceful shutdown, health checks, and service hosting review. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
This skill should be used when a developer or lead wants a project status overview — for example "what's the state of the project", "show me what's blocked", "project health check", "what traces are stuck", "standup summary", "how many issues are unverified", "what's left in this epic", "show me what needs attention", "what's been implemented but not verified", or "what's blocking the release". Scans all open WTF issues — Traces plus legacy Tasks — and produces a triage-ready health report with actionable next steps.
Use when an agent is writing, debugging, or updating code against Apple frameworks and needs local Xcode documentation to resolve compile errors, discover the right symbols, check API shape or availability, confirm usage patterns, or inspect related articles and topics for newly released SDK features.
Integration skill for Alibaba Cloud Yunxiao DevOps. Provides full DevOps capabilities, including code management, pipelines, project management, organization management, artifact repositories, application delivery, and test management. Use when users need to interact with Yunxiao, including: (1) code repository operations (branches, files, merge requests); (2) creating and running pipelines; (3) managing projects and work items; (4) managing organization members; (5) querying artifact repositories; (6) deploying and releasing applications; (7) managing test cases. Triggers: Yunxiao, Codeup, Flow, Projex, AppStack, DevOps.
Setup and use ActionCable for real-time features in Rails applications using WebSockets. Use when implementing real-time updates, live notifications, broadcasting changes, or when the user mentions WebSockets, ActionCable, channels, broadcasting, or Turbo Streams over cable.
Add click handlers, hover effects, pointer events, trigger areas, raycasting, and global input to Decentraland scene entities. Use when the user wants to make objects clickable, add hover effects, detect player proximity, handle E/F key actions, or cast rays. Do NOT use for advanced input patterns like movement restriction, cursor lock, or WASD control (see advanced-input). Do NOT use for screen-space UI buttons (see build-ui).
Verified contract addresses for major Ethereum protocols across mainnet and L2s. Use this instead of guessing or hallucinating addresses. Includes Uniswap, Aave, Compound, Aerodrome, GMX, Pendle, Velodrome, Camelot, SyncSwap, Lido, Rocket Pool, 1inch, Permit2, MakerDAO/sDAI, EigenLayer, Across, Chainlink CCIP, Yearn V3, USDC, USDT, DAI, ENS, Safe, Chainlink, Robinhood Chain stock tokens, and more. Always verify addresses against a block explorer before sending transactions.
Advanced input handling in Decentraland. PointerLock (cursor capture state), InputModifier (freeze/restrict player movement), PrimaryPointerInfo (cursor position and world ray), WASD keyboard patterns, and action bar slots. Use when the user wants movement restriction, cursor control, FPS controls, input polling, or cutscene freezing. Do NOT use for basic click/hover events on entities (see add-interactivity).
Advanced rendering in Decentraland scenes. Billboard (face camera), TextShape (3D world text), PBR materials (metallic, roughness, transparency, emissive glow), GltfNodeModifiers (per-node shadow/material overrides), VisibilityComponent (show/hide entities), and texture modes. Use when the user wants billboards, floating labels, 3D text, material effects, glow, transparency, or model node control. Do NOT use for screen-space UI (see build-ui) or loading 3D models (see add-3d-models).
Bash-loop runner for unattended, fresh-context execution of ready-for-agent issues. Each iteration starts empty, reads the spec from the issue body, applies TDD, commits, advances. Use when the user wants to walk away and let a batch of ready-for-agent slices ship overnight, or asks how to install/use the AFK runner.
Guide for designing and implementing command-line interfaces (CLIs) that are equally usable by human developers and automated coding agents. Use when the user wants to build a CLI, apply CLI best practices, or use Go with Cobra and Viper.
Adds an "AI Summary Request" footer component with clickable AI platform icons (ChatGPT, Claude, Gemini, Grok, Perplexity) that pre-populate prompts for users to get AI summaries of the website. Optionally creates an llms.txt file for enhanced AI discoverability. Use when users want to add AI platform integration buttons or make their website AI-friendly.
Multi-perspective code analysis using three AI personas (RYAN, FLASH, SOCRATES) for comprehensive decision-making. Use when complex code decisions need analysis from multiple viewpoints, or when avoiding single-perspective blind spots is critical.
Software development engine for coding. A production-grade skills system for web apps and mobile architecture, APIs, databases, web, mobile, AI, security, UX, SaaS, and ERP engineering. Encodes reusable engineering judgment through layered baseline and specialist skills to help generate secure, scalable, maintainable, high-performance software systems
Animate objects in Decentraland scenes. Play GLTF model animations with Animator, create procedural motion with Tween (move/rotate/scale), and chain sequences with TweenSequence. Use when the user wants to animate, move, rotate, spin, slide, bob, or create motion effects. Do NOT use for audio/video playback (see audio-video).
API design patterns for REST, gRPC, and GraphQL. Use for: api design, REST, gRPC, GraphQL, protobuf, schema design, api versioning, pagination, rate limiting, error format, OpenAPI, API authentication, JWT, OAuth2, API gateway, webhook, idempotency.
Guide for building React applications with Apollo Client 4.x. Use this skill when: (1) setting up Apollo Client in a React project, (2) writing GraphQL queries or mutations with hooks, (3) configuring caching or cache policies, (4) managing local state with reactive variables, (5) troubleshooting Apollo Client errors or performance issues.
Build and embed pro-code JavaScript custom apps inside Domo App Studio pages. Bridges the custom app build pipeline (basic-custom-app-build, domo-app-theme) with App Studio layout (basic-app-studio, advanced-app-studio). Covers decision routing between native cards and pro-code apps, build coordination with design skills, canvas integration, page-level filter propagation (domo.onFiltersUpdated), App Studio variable integration (domo.onVariablesUpdated, domo.requestVariablesUpdate), and the pending/commit pattern for variable state management. Use when a visualization or interaction exceeds native card capabilities, when the user mentions pro-code editor, or when embedding custom apps in App Studio.
This skill should be used when the user asks about “ArchiMate naming conventions,” “model quality,” “EA smells,” “anti-patterns,” “ArchiMate best practices,” “model review,” “abstraction levels,” “viewpoints,” “model organization,” or needs guidance on creating high-quality ArchiMate models.
Use when starting a new feature, designing a new project, or making a substantial architectural change to an existing codebase. Entry ramp and spine phase 1. Captures intake before scoped context discovery, then challenges deviations from idiomatic patterns, surfaces refactors as first-class decisions, and produces a validity-checked architecture.md. For epics, decomposes into child changes instead of a single architecture.md. Do NOT use for bugs or tiny changes — use triage instead.
Use this skill whenever anyone asks about migrating from Auth0 to Descope — whether they're a developer doing it themselves or a technical lead evaluating the move. Triggers on: “how do I migrate from Auth0”, “replace Auth0 with Descope”, “we're moving off Auth0”, “Auth0 to Descope”, “switch from Auth0”, “our app uses express-openid-connect / nextjs-auth0 / auth0-fastapi / other Auth0 SDK and we want to use Descope instead”, or any question about Auth0 features (Actions, FGA, Organizations, Token Vault, CIBA) in the context of Descope. Works for any language or framework with a Descope SDK. Always use this skill before producing migration guidance — do not rely on memory alone.
One unified skill for all engineering work: code, UI, docs, and repo maintenance. Auto-detects which specialization to activate from the prompt — ENGINEER for feature work and code changes (full phase-gated SDLC, spec, DAG execution, TDD, evaluator; SPEC-lite mode for design-doc-only handoffs), UI for design and styling (typography, spacing, color, components, dark mode, accessibility), DOCS for documentation (Diátaxis-driven: tutorials, how-tos, reference, explanation, READMEs), MAINTAIN for repo health (security audit, lint/type debt, flaky tests, dead code, dependency upgrades). Blends multiple specializations in a single session when the prompt spans them. Loads only the relevant reference files — a context-efficient alternative to running separate commands. Triggers on any code/feature/build request, "design a UI", "style this", "write docs", "document this", "add a README", "security audit", "fix flaky tests", "upgrade dependencies", or any combination.
Generate enterprise-grade web applications using Backstage Design System. Create admin dashboards, developer tools, and internal applications with modern React components, dark/light themes, and responsive design patterns based on Radix UI and Tailwind CSS.
Build, review, debug, configure, migrate, teach, or plan Better Auth TypeScript auth with current docs and official ecosystem packages. Use for better-auth 1.7, betterAuth, createAuthClient, auth.api, auth.handler, emailAndPassword, socialProviders, genericOAuth, organization, admin, twoFactor, passkey, magicLink, emailOTP, phoneNumber, username, anonymous, bearer, apiKey, jwt, oauth-provider, mcp, cimd, oauthDeviceAuthorization, sso, scim, stripe, captcha (incl. Vercel BotID), oauthProxy, drizzleAdapter, prismaAdapter, redis-storage, Expo, Electron, hydrateSession, nextCookies, trustedOrigins, validateUserInfo, security advisories (Magic Link / OAuth Proxy takeover fixed in 1.7.7), and bunx auth@latest generate/migrate/check/upgrade/create-admin.
GitHub operations via the Blink GitHub App — clone repos, push code, open pull requests, create issues, check CI, and call the GitHub REST API. No PAT needed. Connect once at blink.new/settings?tab=connectors and every surface (CLI, MCP, Claw agents) works automatically.
Use this skill when adding documentation comments to BoxLang code: writing function/class Javadoc-style comments, documenting arguments, return types, exceptions, examples, or generating structured API reference documentation for BoxLang classes and BIFs. Comments written with these conventions are compatible with DocBox API documentation generation.
Collaborative requirements discovery session optimized for AI coding workflows. Creates task directories, seeds PRDs, runs codebase research, proposes concrete implementation approaches with trade-offs, and converges on MVP scope through structured Q&A. Use when requirements are unclear, multiple implementation paths exist, trade-offs need evaluation, or a complex feature needs scoping before development.
Use when brainstorming a feature or change whose written design should live in a GitHub issue instead of a docs/ file — including starting, pausing, and resuming a brainstorm across sittings or harnesses, and revising an issue already handed over. Triggers include "brainstorm this into an issue", "spec it out as a GitHub issue", "file an issue for this feature", "continue/resume brainstorming issue #N", "pick up the draft brainstorm", "brainstorming-to-issue #N".
Build 2D screen-space UI for Decentraland scenes using React-ECS (JSX). Create HUDs, menus, health bars, scoreboards, dialogs, buttons, inputs, and dropdowns. Use when the user wants screen overlays, on-screen UI, HUD elements, menus, or form inputs. Do NOT use for 3D in-world text (see advanced-rendering) or clickable 3D objects (see add-interactivity).
Browser automation via Puppeteer CLI scripts (JSON output). Capabilities: screenshots, PDF generation, web scraping, form automation, network monitoring, performance profiling, JavaScript debugging, headless browsing. Actions: screenshot, scrape, automate, test, profile, monitor, debug browser. Keywords: Puppeteer, headless Chrome, screenshot, PDF, web scraping, form fill, click, navigate, network traffic, performance audit, Lighthouse, console logs, DOM manipulation, element selector, wait, scroll, automation script. Use when: taking screenshots, generating PDFs from web, scraping websites, automating form submissions, monitoring network requests, profiling page performance, debugging JavaScript, testing web UIs.
Operate Circuit, the flow engine that runs coding work as structured, evidence-backed flows (Fix, Build, Explore, Review, Prototype). Use ONLY when the user explicitly invokes Circuit by name — e.g. says "circuit", "run a flow", "use circuit", "start a circuit run", "resume the run", or names Circuit-specific concepts (flows, checkpoints, run folders, the power dial or process override, connectors, `circuit preview`, `circuit reclaim`). Do NOT trigger on generic coding requests, even substantive ones; do NOT trigger merely because Circuit is installed in the project. Absent an explicit mention, do the work by hand.
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.