Skills
99,448 packaged capabilities and playbooks for agents. Install any of them with one command.
All
A skill that generates prototype UI based on Mock data without a backend. Vue 3 + TypeScript + NuxtUI v4. It accumulates per-task screens in the modules-task folder of a separate ui-proto repository (e.g. peach-ui-proto-backoffice). Triggered by keywords such as "프로토타입 만들어줘", "Mock 화면", "proto UI", "기획 화면 빠르게", "ui-proto 작업", "기획자 검토용 화면", "태스크 폴더 추가". If a Spec document is provided as input, it automatically switches to team mode (Ralph loop 5/10 times); if a planner works directly without a Spec, it runs in solo mode. If real API integration is needed, use peach-gen-ui.
Design a presentation / slide deck in Penpot from a brief, as a senior presentation designer: 1920x1080 slide boards built one slide per call from an approved outline, a committed deck style, varied slide archetypes (cover, agenda, section, content, big-number, comparison, grid, bento, quote, timeline, image-bleed, closing), tokenized, wired into a playable View-mode flow and exportable to PDF. NOT for app screens (use penpot-build-screen). Triggers: 'create a presentation', 'build a slide deck', 'design slides in Penpot', 'pitch deck', 'keynote', 'make slides for this talk', 'turn this outline into slides'.
Guides engineers and QA professionals in interpreting performance test results, identifying bottlenecks, and producing two types of reports: a technical report (for engineers and QA) and a business report (for stakeholders and executives). Use this skill whenever the user shares load test results, CSV stats, HTML reports, percentile data, or test output from k6, Gatling, Locust, JMeter, Artillery, or any other tool — and wants to understand what the numbers mean, diagnose problems, or communicate findings. Trigger on phrases like "analyze my test results", "what do these numbers mean", "my p95 is high", "error rate under load", "write a performance report", "explain the results to my manager", "how do I present this to stakeholders", or "I found a bottleneck".
[Planning] Use when you need intelligent plan creation with prompt enhancement. Flag: --mode={ci|cro} (default none — standard planning); --mode=ci plans a fix from a GitHub Actions CI run/log, --mode=cro plans conversion-rate optimization (25-item CRO framework).
When the user wants to optimize store planograms, shelf space allocation, or visual merchandising layout. Also use when the user mentions "planogram," "shelf space optimization," "space productivity," "category management," "shelf allocation," "fixture planning," "facings optimization," or "merchandising layout." For inventory allocation, see retail-allocation. For assortment planning, see seasonal-planning.
Full Windows post-exploitation workflow. Use after obtaining a Windows shell via RCE/webshell/RDP. Covers system information gathering, UAC bypass, local privilege escalation, credential extraction (SAM/LSASS/browsers), and domain reconnaissance. Applies to standalone hosts and domain environments.
Open or update a GitHub PR from the current branch, pushing normally when needed. Use when the user invokes pr-branch or requests PR creation or refresh. Follow one value-first template for any project size: explain invisible engineering to non-technical readers, then record technical changes and verification. Default to English unless a language is explicitly specified.
Generate real instrumentation code from the tracking plan and instrumentation guide. Produces typed SDK wrapper functions, identity management, and integration guidance. Outputs files in a tracking/ directory. Use when the user wants to generate or regenerate tracking code, implement the delta plan, turn the instrumentation guide into working code, 'implement tracking,' 'generate code,' 'create tracking module,' or 'build analytics SDK wrapper.'
Update the tracking plan when a feature ships, changes, or is removed. Assesses whether new events are needed, extends existing events with properties where possible, and produces a versioned mini-delta with changelog entry. Updates .telemetry/tracking-plan.yaml, delta.md, and changelog.md. Use when the user ships a new feature, modifies existing functionality, wants to keep tracking coherent as the product evolves, "feature shipped," "new feature tracking," "update tracking for [feature]," "what tracking does this feature need," or "instrument new feature."
Build a structured product model by scanning the codebase and talking to the user. Produces .telemetry/product.md — a description of what the product does, who uses it, how value flows, and what entities exist. Use when starting telemetry work on a new codebase, when the user asks to 'model this product,' 'understand this product,' 'what does this product do,' 'map the product,' 'product model,' or when no .telemetry/product.md exists yet. This is the entry point for the telemetry lifecycle.
When the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions "programmatic SEO," "template pages," "pages at scale," "directory pages," "location pages," "[keyword] + [city] pages," "comparison pages," "integration pages," or "building many pages for SEO." For auditing existing SEO issues, see seo-audit.
Full-stack development and architecture design assistant, covering scenarios such as "development, implementation, writing code, continuing development, bug fixing, code refactoring, architecture design, technical solution evaluation/code review", suitable for full-stack R&D tasks in new projects and existing code repositories.
Design and audit promotion campaigns, offers, discounts, launches, win-back, lifecycle campaigns, app/game events, referral pushes, and seasonal campaigns across audience, eligibility, placement, messaging, fulfillment, measurement, fraud controls, and support readiness. Use when planning campaigns that should grow revenue or retention without dark patterns.
Master prompt engineering for AI models: LLMs, image generators, video models. Techniques: chain-of-thought, few-shot, system prompts, negative prompts. Models: Claude, GPT-4, Gemini, FLUX, Veo, Stable Diffusion prompting. Use for: better AI outputs, consistent results, complex tasks, optimization. Triggers: prompt engineering, how to prompt, better prompts, prompt tips, prompting guide, llm prompting, image prompt, ai prompting, prompt optimization, prompt template, prompt structure, effective prompts, prompt techniques
Use when the user needs to look up a TOTVS Protheus native function's syntax/parameters/return value, the SX data dictionary structure (SX1-SX9, SIX), REST API endpoint patterns (FWRest, WsRestFul), MV_* system parameter behavior, SX3 field validation, or whether a function is restricted/internal-only. Also triggers on Portuguese phrasing like "funcao nativa", "dicionario de dados", "parametro MV_", "campo SX3", "API REST protheus", "essa funcao e restrita".
Social Media Publisher. Takes approved content from outputs/ and schedules it across platforms via Blotato MCP. Generates infographic-style visuals (stat cards, framework diagrams, process graphics, quote graphics) for posts flagged by platform-specialist skills. Requires Blotato MCP to be configured. Run after /linkedin-writer, /threads-writer, /x-writer, or /caption-writer.
Use when a Python change is about to be called done (before commit or PR) and whenever asked to review, audit, sanity-check, or clean up Python code or judge whether it meets standards. Also use at decision points the defaults cover: choosing retry/timeout/idempotency policy, config loading, pydantic placement, module boundaries, or a concurrency model.
Authors GitHub Actions quality-gate workflows for a Python repo — lint/type/test jobs, version matrices, uv caching, an all-checks-passed aggregator, required checks, rulesets, merge queues, SHA pinning, zizmor hardening. Use for 'set up continuous integration quality gates', 'make checks required', 'move branch protection to rulesets', 'harden the workflows'. Not for release pipelines or commit hooks.
Python SDK for inference.sh - run AI apps, build agents, and integrate with all models. Package: inferencesh (pip install inferencesh). Supports sync/async, streaming, file uploads. Build agents with template or ad-hoc patterns, tool builder API, skills, and human approval. Use for: Python integration, AI apps, agent development, RAG pipelines, automation. Triggers: python sdk, inferencesh, pip install, python api, python client, async inference, python agent, tool builder python, programmatic ai, python integration, sdk python
This skill should be used when establishing comprehensive QA testing processes for any software project. Use when creating test strategies, writing test cases following Google Testing Standards, executing test plans, tracking bugs with P0-P4 classification, calculating quality metrics, or generating progress reports. Includes autonomous execution capability via master prompts and complete documentation templates for third-party QA team handoffs. Implements OWASP security testing and achieves 90% coverage targets.
Build/deploy an internal Miovision site on Quick — a folder of static files served at <site>.quick.mio.vision, with a zero-config global `quick.*` API for identity, db, realtime, AI, Snowflake, per-user SaaS integrations (Jira/Confluence/Slack/Drive/Salesforce), file uploads, and multi-site deploy. Use for internal Miovision web site/apps/tools/dashboards, or when the user mentions Quick.
This skill should be used when managing movies in Radarr. Use when the user asks to "add a movie", "search Radarr", "find a film", "add to Radarr", "remove a movie", "add movie collection", "check if movie exists", "Radarr library", or mentions movie management, TMDB integration, or Radarr operations.
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.
