Skills
98,284 packaged capabilities and playbooks for agents. Install any of them with one command.
Development
Use Miles AI, an expert WordPress designer, through composable CLI primitives. Use when the user wants to design or build a website, get design options for content they already have, design around existing copy or a brief, convert HTML into a WordPress block theme, edit or redesign a site, export site deliverables, resume work on an existing Miles site, or update/uninstall the Miles skill. Triggers include mentions of Miles, bymiles.ai, start.bymiles.ai, "build a website", "design directions", "WordPress theme", or supplying content/briefs that need a designed site.
Search the ecosystem for something that already solves the task before it gets built, and write the decision — reuse, extend or build — into the spec's Reuse research section as a spec-only commit. Use only when the user explicitly asks for reuse research or accepts an offer to run it.
Manage stacked branches and pull requests with the gh-stack GitHub CLI extension. Use when the user wants to create, push, rebase, sync, navigate, or view stacks of dependent PRs. Triggers on tasks involving stacked diffs, dependent pull requests, branch chains, or incremental code review workflows.
OpenDesign design token guide. Use this skill when you need to work with the CSS variables in the @opensig/opendesign-token package. It covers the complete token system of six themes (openEuler/Ascend/Kunpeng/Mindspore/openGauss/openUBMC) and supports all design tokens such as color, spacing, border radius, fonts, shadows, responsive typography, and the grid system. Use cases: (1) find the semantic token for a color value, (2) get the token names for spacing/border radius/fonts, (3) understand the differences between the six themes, (4) use CSS variables instead of hard-coded values in code, (5) use responsive tokens for multi-breakpoint adaptation, (6) import HarmonyOS font files and use font family/weight tokens (including seven weights, automatic Latin/Chinese splitting, and on-demand import by weight)
Provides comprehensive guidance for Parcel bundler including zero-configuration setup, asset handling, hot module replacement, and production builds. Use when the user asks about Parcel, needs to set up a build tool quickly, or work with Parcel's automatic configuration.
Skill for generating production UI based on a Store. Vue 3 + TypeScript + NuxtUI v4. Triggered by "UI 만들어줘", "화면 생성", "CRUD 화면", "목록 화면". A Store must exist, and it generates production code integrated with real APIs. If you need a Mock-data prototype, use peach-team-ui-proto.
Train custom TTS voices for Piper (ONNX format) using fine-tuning or from-scratch approaches. Use when creating new synthetic voices, fine-tuning existing Piper checkpoints, preparing audio datasets for TTS training, or deploying voice models to devices like Raspberry Pi or Home Assistant. Covers dataset preparation, Whisper-based validation, training configuration, and ONNX export.
Plaid banking API expert for financial data integration. Covers Plaid Link, Auth (account/routing numbers), Transactions, Identity verification, Balance checking, and webhooks. Build fintech apps with bank connections, ACH transfers, and transaction history. Triggers on Plaid, banking API, Plaid Link, bank connection, ACH, financial data, transaction history.
Multi-agent coordination daemon for coding agents. Use for deterministic port claims, session tracking, salvage, file claims, notes, pub/sub, tuple-space coordination, background fleets, and debugging multi-agent failures across Claude Code, Codex, Gemini CLI, Cursor, or Windsurf. NOT for production deploy orchestration, Docker or Kubernetes networking, or cloud service discovery.
Help users sync and manage their application users in Portaly Vibe, including initial migration, incremental sync, and dashboard viewing. Trigger when the user mentions Portaly user sync, user management, user synchronization, member sync, or wants to push user data to Portaly.
Expert guidance on using PostgreSQL with Swift. Use when developers mention: (1) PostgreSQL or Postgres in Swift, (2) postgres-nio library, (3) SQL queries in Swift, (4) PostgreSQL connection pooling, (5) prepared statements, (6) type-safe database access, (7) bulk loading or COPY FROM, (8) PostgresClient or PostgresConnection.
Systematic problem-solving techniques for stuck-ness. Techniques: simplification cascade (complexity spirals), collision-zone thinking (innovation blocks), meta-pattern recognition (recurring issues), inversion exercise (assumption constraints), scale game (uncertainty). Actions: simplify, analyze, recognize patterns, invert assumptions, scale thinking. Keywords: problem solving, complexity spiral, innovation block, stuck, simplification, meta-pattern, assumption inversion, scale uncertainty, breakthrough thinking, root cause, systematic analysis, Microsoft Amplifier, debugging approach, creative solution. Use when: complexity spiraling, hitting innovation blocks, seeing recurring patterns, constrained by assumptions, uncertain about scale, generally stuck on problems.
Use when the user needs to scope, write, or audit a product spec — a PRD, feature spec, user stories, acceptance criteria, or a "spec this out"/"break this into stories"/"definition of done" request — or wants an existing spec reviewed for gaps and anti-patterns. Triggers whenever a feature idea needs to become structured requirements that align a team on what to build. For the analytics behind success metrics, use data-analysis; for the technical design, use software-architect.
Make a design question tangible before committing to it: compare production-representative UI directions for a screen, component, or short flow, or drive a logic, state, data-shape, API, or CLI model through a shareable HTML demo. Use before committing to a visual, interaction, or behavioral design; not for production implementation.
Use when designing or writing a new package, procedure, function or trigger, or restructuring one — “viet package”, “tao procedure”, “them function”, “them trigger”, an API another team will call, an error-handling or logging design, a spec change. Applies the industry-standard PL/SQL design rules — the spec as a contract, named exceptions, one transaction owner, thin triggers — beneath the house conventions, which always win.
Use when a query, report or PL/SQL unit is slow, before adding an index or a hint, or when someone says “cham”, “toi uu truy van”, “optimize this query”, “why is this report slow”, or “full table scan”. Measures with the optimizer's own plan and statistics, changes one thing at a time, and proves the gain with the same measurement — license-safe, no AWR/ASH or Tuning Pack.
Sets up and tunes Ruff linting and formatting for a Python package — pyproject [tool.ruff] rule selection, Black/Flake8/isort migration — and fixes lint or format failures. Use when the user says 'set up linting', 'add ruff', 'fix lint errors', 'configure the formatter'. Not for type errors, non-Python file formatting, pre-commit wiring, or CI workflows.
Memory-safe Python script patterns for long-running processes under systemd MemoryMax constraints. Covers allocator purge (mimalloc/glibc malloc_trim), HTTP response lifecycle, DataFrame cleanup, thread-local connection reuse, and periodic GC cadence. Battle-tested through 5 OOM optimization cycles on production GPU workstations. Use this skill proactively whenever writing or reviewing Python scripts that: run under systemd with MemoryMax, process data in loops (downloads, ETL, backfill), use ThreadPoolExecutor, or make repeated HTTP requests. Also use when diagnosing OOM kills, RSS creep, or fd exhaustion in Python services. TRIGGERS - memory optimization, OOM prevention, RSS reduction, malloc_trim, systemd MemoryMax, memory leak, allocator purge, memory-safe script, RSS creep, fd exhaustion, SIGKILL status 9, MemoryHigh, glibc arena, mimalloc purge, requests memory leak, ThreadPoolExecutor cleanup.
Use this skill to record a terminal or TUI demo with VHS whenever the user wants to "record a demo", "create a GIF of my CLI", "write a VHS tape", "make a terminal recording", or "add a demo GIF to the README" — even if they never say "VHS" and only ask for an animated demo of a command-line tool. Covers tape syntax, dimensions, pacing, GIF size reduction, and CI golden-file recording. Do NOT use this skill to build the TUI itself (see build-tui), to screenshot a web app on localhost (see screenshot-local), or to capture video of anything outside a terminal.
Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.
Reverse engineer minified, bundled, and obfuscated browser/Node JavaScript — unpacking webpack chunks, recovering source from sourcemaps, undoing obfuscator.io string-array and control-flow obfuscation with webcrack/synchrony/restringer, and locating a signing or crypto routine in a live bundle via Chrome DevTools. Use when a page ships a huge minified bundle, when code is full of _0x hex identifiers and a rotated string array, when a .js.map is reachable, or when you must find where a request signature or token is computed.
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.