Skills
97,725 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Verify whether a GitHub issue is fixed in the local codebase. User provides a GitHub issue URL, the skill fetches it, extracts reproduction steps, builds the product from source, runs the reproduction steps, and reports whether the issue still exists or not.
Migrate applications between IDS (Iress Design System) major versions — including v4→v5, v5→v6, and OUI→v6. Covers component renaming, prop changes, form architecture migration (Formik→React Hook Form), testing updates, and common gotchas. Use when the user asks about upgrading, migrating, or updating IDS versions, or mentions OUI, v4, v5, or v6 migration.
Turns existing audit or health output, or saved recurring runs, into an HTML dashboard, SVG charts or Mermaid diagrams. Triggers: visualise the findings, dashboard, chart, graph the trends. Does not run audits (run one first); for a written brief use stakeholder-brief.
Generate complete, runnable Volcengine SDK code and provide SDK configuration guidance. Supports Go, Python, PHP, Java, and Node.js. Trigger this skill whenever the user wants to call a Volcengine API, generate Volcengine SDK code, or describes a cloud operation on Volcengine (e.g., "list ECS instances", "create a VPC on Volcengine", "query Volcengine billing with Python"). Also trigger when the user asks about Volcengine SDK configuration and best practices — including retry, timeout, authentication (AK/SK, STS, AssumeRole), proxy, connection pooling, SSL, debug mode, and error handling (e.g., "how to configure retry for Volcengine Go SDK", "volcengine python sdk proxy setup"). Trigger when the user mentions Volcengine service names such as ECS, VPC, CDN, CLB, RDS, Redis, Kafka, billing, IAM, DNS with code generation or SDK usage intent. When the user only needs API specification queries (parameters, error codes, response structures), hand off to the volcengine-api skill. When the user needs CLI-based operations, hand off to the volcengine-cli skill. Supports both Chinese and English prompts.
Search VRBO (Vrbo / Expedia Group) vacation rentals including entire homes, condos, and cabins via Patchright browser automation. VRBO sits behind Akamai Bot Manager so plain HTTP and standard Playwright get a 429 bot wall. Use for whole-home or group stays, multi-bedroom rentals, and Airbnb-vs-VRBO comparisons. Trigger phrases include search VRBO, Vrbo rentals, vacation rental, cabin rental, whole house, condo for the group.
Walrus CLI client for storing, reading, and managing blobs from the command line. Use when the user needs to run walrus store, walrus read, walrus blob-status, walrus extend, walrus delete, walrus share, or any other walrus CLI command. Also use for CLI installation, configuration (client_config.yaml), JSON mode for scripting, gas budgets, wallet configuration, and logging. For blob lifecycle management details, see `walrus-blob-lifecycle`. For quilts, see `walrus-quilts`.
Encrypting data before storing on Walrus using Seal (threshold encryption with onchain access control). Use when the user needs to store private or sensitive data on Walrus, implement access control for blob content, encrypt blobs before uploading, use @mysten/seal for threshold encryption, or understand Walrus data security guarantees (availability, integrity, confidentiality). Also use when the user asks about Nautilus (TEE-based off-chain computation) in the context of Walrus data. All blobs on Walrus are public by default.
Walrus quilts for batching many small blobs into a single storage unit. Use when the user needs to store multiple files as a quilt, retrieve individual blobs by QuiltPatchId or identifier, list patches in a quilt, or use quilt HTTP endpoints. Also use when optimizing storage costs for many small blobs. Covers both CLI (store-quilt, read-quilt, list-patches-in-quilt) and HTTP API quilt operations. For regular single-blob storage, see `walrus-cli` or `walrus-http-api`.
Deploying, updating, and serving decentralized static websites on Walrus Sites. Use when the user needs to deploy a frontend to Walrus Sites, run a local portal for testnet or mainnet, use the site-builder CLI, configure ws-resources.json (routing, headers, metadata), set up custom domains (SuiNS, DNS), automate deploys with GitHub Actions CI/CD, debug site-builder errors, or manage site object lifecycle (update, destroy, extend blobs). Also use when the user asks about site-builder, walrus-sites, portal setup, or hosting a dApp on Walrus. For blob storage without the Sites framework (raw upload/download), see `walrus-cli` or `walrus-http-api`.
Walrus storage pricing, cost estimation, and the dual-token (WAL + SUI) cost model. Use when the user asks how much storage costs, how to estimate costs for a dataset, what the per-blob metadata overhead is, how epochs relate to pricing, how to use the cost calculator or walrus info, or why small blobs are expensive. Also use when the user asks about WAL vs SUI fees, write fees, storage fund deposits, dry-run cost checks, or cost optimization strategies (quilts, storage reuse).
Use when tasks need real-browser web automation in Chrome/Chromium via CDP: open or navigate URLs, click/type/select in forms, run page JS, wait for selectors, scrape structured content, capture screenshots, validate UI flows, or run measured web-browser latency checks (`bench:eval`, `bench:all`) for perf regressions.
Create and deploy single-page static websites to GitHub Pages with autonomous workflow. Use when building portfolio sites, CV pages, landing pages, or any static web project that needs GitHub Pages deployment. Handles complete workflow from project initialization to live deployment with GitHub Actions automation.
Production-grade web application UI design based on Refactoring UI principles. ALWAYS activate for: landing page, dashboard, auth screens, hero sections, card design, button design, form inputs, navigation, layouts, spacing decisions, typography hierarchy, color selection, shadows, depth, empty states, background decoration. Provides design workflow, visual hierarchy, spacing systems (4px grid), type scale, HSL color systems, shadow elevation, finishing touches. Turkish: sayfa tasarımı, UI/UX, frontend tasarım, web tasarım, güzel arayüz, modern tasarım, card tasarımı, buton stili, form tasarımı, renk paleti, tipografi. English: beautiful interface, sleek design, premium feel, visual hierarchy, whitespace, color palette, typography scale.
Web2 recon pipeline — subdomain enumeration (subfinder, Chaos API, assetfinder), live host discovery (dnsx, httpx), URL crawling (katana, waybackurls, gau), directory fuzzing (ffuf), JS analysis (LinkFinder, SecretFinder), continuous monitoring (new subdomain alerts, JS change detection, GitHub commit watch). Use when starting recon on any web2 target or when asked about asset discovery, subdomain enum, or attack surface mapping.
Use when the complete Spring Boot 3 request path is reactive: WebFlux controllers, Reactor pipelines, R2DBC persistence, streaming, backpressure, or cancellation. For defining and registering declarative outbound API interfaces, use http-interface-clients
Build premium, narrative-driven landing pages from scratch or redesign weak ones. Apply the design principles, techniques, and iterative process refined through building tydra.netlify.app — a biotech landing page that went from flat to genuinely good through deliberate iteration. Use when asked to design or redesign a website, landing page, or product page.
Manage LLM-compiled wikis: initialize, ingest/import, compile/query, research/audit, collect catalogs, track inventory/datasets/Ideas, review Idea/Project portfolios, manage archives/sessions/feedback, and generate outputs. Activates for /wiki commands; wiki or knowledge-base work; ingest, collect, catalog, compile, query, audit, librarian, inventory, idea, portfolio, business ideas, projects, datasets, archives, sessions, feedback, checkpoints, private adapters, adapter routing, explicit wiki skill-factory requests, personal specialist skills, expert review, specialist selection, provenance, external resource actions (including requests to read, review, or edit hosted documents), or questions in a directory with .wiki/ or a configured hub.
This skill MUST be used when rescuing an unbootable Windows PC from Linux, preparing a Linux rescue USB, or extracting Windows image files to replace damaged system components. Covers Windows 開不了機, BSOD 救援, 救資料, BCD 修復, NTFS 損壞, BitLocker, 離線掃毒, 重設 Windows 密碼, 系統檔替換, Windows 映像提取, 隨身碟救援系統 and 救援工具安裝. It SHOULD also be used when symptoms imply offline Windows recovery even without naming a tool. Default language is Traditional Chinese for Taiwan.
Guides design, build, customization, and integration of warehouse management systems—receiving, putaway, inventory, allocation, picking (wave/batch/zone), packing, shipping, cycle counts; slotting; lot/serial/expiry; RF/mobile and barcode; WMS–ERP–TMS–OMS integration; EDI/API; WCS/automation handoffs; peak scaling; multi-warehouse and 3PL models. Use when the user mentions WMS developer, warehouse management system, pick path, wave planning, putaway, cycle count, WMS integration, RF scanning, slotting, 3PL WMS, fulfillment system, inventory allocation, or WMS customization—not supply chain strategy without WMS (supply-chain-manager), generic ERP consulting, logistics routing without WMS, OT/ICS plant (scada-ics-cyber-security-specialist, control-software-developer), analytics warehouse marts (data-warehouse-engineer), or generic app/platform work without warehouse domain (senior-software-engineer, platform-engineer).
Use for the wooksjs monorepo or any @wooksjs package: @wooksjs/event-core (EventContext, key/cached/cachedBy slots, defineWook, defineEventKind, AsyncLocalStorage, useRouteParams, useLogger), @wooksjs/event-http (createHttpApp, HTTP routing, useRequest, useHeaders, useCookies, useUrlParams, useAuthorization, useAccept, useResponse, HttpError, prepareTestHttpContext, programmatic fetch/request, SSR, withHttpContext, forwardHeaders), @wooksjs/http-body (useBody, parseBody), @wooksjs/http-static (serveFile), @wooksjs/http-proxy (useProxy), @wooksjs/event-cli (createCliApp, command routing, useCliOptions, useCliOption, useCliHelp, useAutoHelp), @wooksjs/event-ws (WooksWs, onMessage, onConnect, onDisconnect, useWsConnection, useWsMessage, useWsRooms, useWsServer, WsError), @wooksjs/event-wf (createWfApp, steps/flows, useWfState, pause/resume, StepRetriableError, outlets, swapStrategy), @wooksjs/ws-client (createWsClient, reconnection, RPC, WsClientError). Also for runtime-duplication warnings ("A second copy of @wooksjs/event-core", "Incompatible versions of @wooksjs/event-core"). Not for moostjs or generic Node http servers.
Receive and verify WorkOS webhooks. Use when setting up WorkOS webhook handlers, debugging WorkOS-Signature verification, or handling enterprise auth events like dsync.user.created, dsync.group.user_added, connection.activated, user.created, or session.created.
Design and facilitate consulting workshops, strategy offsites, discovery sessions, prioritization, and design sprints. Use for agendas, participant activities, facilitation guides, pre-work, and follow-through for in-person, virtual, or hybrid groups.
Complete reference for World of Warcraft UI escape sequences — pipe-character sequences embedded in text strings to produce colors, inline textures, atlas icons, grammar inflections, word-wrap hints, Kstrings, and other special rendering. Use when formatting chat output, tooltip text, FontString content, or any UI text that needs color codes, inline icons, named colors, item-quality colors, texture markup, atlas markup, localized grammar forms, or escape-sequence utilities like WrapTextInColorCode, CreateTextureMarkup, CreateSimpleTextureMarkup, and CreateAtlasMarkup.
Sets up GitHub Actions CI/CD workflows for WordPress plugins — coding standards (WPCS/PHPCS), PHP/JS/CSS linting, PHPUnit testing, static analysis (PHPStan), Composer security scanning, WordPress Playground PR previews, and automated deployment to WordPress.org. ALWAYS use this skill when a user wants to create, add, set up, or configure GitHub Actions, CI/CD, automated checks, or deployment workflows for a WordPress plugin — even if they don't use the exact phrase "GitHub Actions". This includes any request to: add automated coding standards or PHPCS/WPCS checks to a WP plugin repo; set up linting (PHP, JS, CSS) for a WordPress plugin; configure PHPUnit testing in CI for a plugin; auto-deploy a plugin to WordPress.org from GitHub; add Playground previews to pull requests; add security scanning or static analysis to a plugin pipeline; or generally "add CI", "add automated checks", "set up workflows", or "automate" anything related to a WordPress plugin's GitHub repository. Also trigger when someone mentions wanting to stop doing manual SVN deploys, wants quality gates on PRs, or is setting up a new WordPress plugin repo and wants best practices for automation. If the user is inside a WordPress plugin repository and mentions anything about automated testing, code quality, deployment, or GitHub workflows, use this skill.
Systematic approach to finding and testing CVEs for identified WordPress plugins. Covers plugin discovery, version extraction from multiple sources (readme.txt, assets, inline JS), CVE database cross-referencing with WPScan/Patchstack/NVD/NVD API, version-based vulnerability matching, exploitation PoC generation, and false-positive elimination. Built from field experience finding exploitable plugin CVEs across 58-company mass recon including ElementsKit (CVE-2023-6851/CVE-2023-6853), Revslider (CVE-2024-2534), WPDM (CVE-2023-49753), Gravity Forms (CVE-2024-6115), and Jetpack (CVE-2024-1782).
Primary pipeline shaping step after /research and before /prd-to-issues. Use when the problem is understood well enough to turn into a bounded PRD issue. May invoke /design-an-interface or /api-design-review when interface or contract uncertainty remains. Not for discovery, decomposition, or implementation-ready work.
Use when starting any feature, system change, or bugfix that requires architectural decisions — before writing implementation plans or code. Triggers on new projects, multi-component changes, API design, or when the user says "design", "spec", or "architecture".
Create Xiaohongshu (RED / 小红书) note covers and first images in 3:4 (1080×1440) for product seeding (种草), reviews, hauls and tutorials: big bold Chinese headline, product hero, visual anchor and stickers, in proven viral layouts. Use for 小红书封面, 种草图, 笔记首图, RED cover, rednote.
【小爷】XY operations coach (Skill edition). When the host does not support custom subagents, this Skill takes on the coach role: restore the user profile, assess the business stage, advance only one step, call the relevant xy-* skill, answer using evidence from the atomic library, and give the next first action. Use when the user says “walk me through it,” “what should I do,” “I don’t know where to start,” “you’re my coach,” or describes their overall situation. | Produced by 小爷
Use when handling BK-CI YAML pipeline import/export, bidirectional YAML and Model conversion, PAC, template references, and YAML validation. Prefer this when the user mentions YAML pipelines, PAC, templating, comment preservation, expression parsing, or conversion debugging.
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.