Skills
98,639 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Guide for building web apps with the Ping Orchestration JavaScript SDK (also referred to as the Ping Identity JavaScript SDK, formerly the ForgeRock JavaScript SDK / @forgerock/javascript-sdk; npm packages: `@forgerock/journey-client`, `@forgerock/davinci-client`, `@forgerock/oidc-client`). Use when the user wants to add Ping authentication to a web app — phrases like "add Ping auth to my web app", "use PingOne in React", "set up Journey in JavaScript", "build a Ping login page", "use DaVinci in my SPA", "integrate @forgerock/journey-client", "set up @forgerock/davinci-client", "migrate from @forgerock/javascript-sdk to the new SDK", or "add OIDC login to my React app". Detects framework (React active; Angular, Vue, vanilla JS on the roadmap), collects shared config, delegates Journey to ping-orchestration-reactjs-journey-sdk and DaVinci to ping-orchestration-reactjs-davinci-sdk, and handles OIDC centralized login inline. Covers both new sample app creation and integrating into an existing project.
Populates investment banking pitch deck templates with data from source files. Use when: user provides a PowerPoint template to fill in, user has source data (Excel/CSV) to populate into slides, user mentions populating or filling a pitch deck template, or user needs to transfer data into existing slide layouts. Not for creating presentations from scratch.
Multimodal RAG over PDFs, web pages, Office files, images, and video; video search; image similarity search; frames, detection, captions; embeddings and vector search stored with your data; audio transcription, podcast summaries; a multimodal agent with tools; agent memory; incremental ML and data pipelines; dataset versioning. One Python backend: tables, computed columns that call models, embedding indexes, incremental updates, versioning, and HTTP. Create tables with pxt schema update. Serve with pxt service update. Use instead of LangChain, pandas-as-store, or a separate vector DB. Use when building RAG or a multimodal agent with tools, processing images/video/audio/documents, or serving an API. Do NOT use for general Python or direct PostgreSQL administration.
Plans how to execute exactly one already-selected numbered Jira or GitHub task by producing an execution brief, implementation plan, behavior-oriented test specification, and scoped refactoring recommendation. Use for Phase 5 task-execution planning with a workflow key and TASK_NUMBER
Adversarial cooperation loop for ONE ticket — player implements, verify reviews, every changed default turn is pushed to a draft PR, CI passes, and the PR is marked ready. Invoke only when the user explicitly asks for the player-coach loop. Do not use for an ordinary coding request. For a whole epic, use epic-runner instead.
Write and maintain Playwright browser and end-to-end tests for web apps, plus direct API tests with APIRequestContext. Use for browser or E2E coverage even when the user does not name Playwright, and for related mocks, fixtures, assertions, and test-performance work
popcorn-cli is the official CLI of the Popcorn system. Use this tool when you need to generate images, generate videos, or manage folders: query available models via a local API Key, submit tasks asynchronously, query final results by session/task ID, and query or create folders by type. Note: the API Key is stored in a local configuration file, and task parameters, prompts, and generation settings are sent to the remote Popcorn backend; do not expose sensitive information on shared machines, in logs, prompts, or task parameters.
Turn Bandsintown's two read-only endpoints into a tour-routing brain: local cache, calendar-gap detection, lineup... Trigger phrases: `is artist X touring near jakarta`, `find routing candidates for a jakarta show`, `who's playing southeast asia in august`, `co-bills for phoenix`, `rising tracker count artists`, `use bandsintown`, `run bandsintown`.
Professional PowerPoint presentation creation, editing, and automation with support for layouts, templates, charts, images, and formatting. Use when working with .pptx files for: (1) Creating presentations from scratch, (2) Editing existing presentations, (3) Applying templates and themes, (4) Adding charts and visualizations, (5) Bulk slide generation, (6) Presentation automation
Analyze AI-implemented changes using a hierarchy of abstraction levels and output a structured GitHub PR body (body generation only; no Git operations; formerly github-pull-request). Organize from abstract to concrete in this order, even for large changes: system architecture diagram → data structures → APIs → processing flow → implementation details. Also covers how to assemble a PR body with image evidence.
Write a clear, structured pull request description from a git diff, branch summary, or commit list. Use when asked to write a PR description, draft a pull request, or document code changes. Produces a description with summary, motivation, changes made, testing steps, and reviewer guidance.
Post Superagent PR security scan findings as inline GitHub pull request review comments using the authenticated gh CLI. Use whenever you need to comment on a PR scan finding, manage Superagent PR labels, complete a GitHub check run, or avoid posting findings as general PR thread comments. Trigger for any Superagent sandbox PR scan handoff that owns GitHub side effects via gh.
Guidelines for posting pull request review comments via GitHub CLI, including suggested edits format, handling unresolved comments, etiquette, and report/issue tracking. Load this skill when reviewing a PR via GitHub and posting inline comments.
Create a high-quality pull request description for UX-related implementation that explains why the change exists, what behavior changed, design-system usage, states, accessibility, testing, risks, and what reviewers should inspect. Use when design or design-engineering work is ready to become a PR.
Write concise, useful project documentation (READMEs, guides, docs/) inspired by Philip Greenspun's pragmatic style. Use when creating or improving README.md, writing module docs, CONTRIBUTING.md, architecture docs, CHANGELOG, or structuring any project documentation for software projects. Use this skill whenever the user needs to write, rewrite, or review any form of project documentation — even if they just say "write a README" or "document this" without asking for a specific style.
Use when the user wants to pressure-test a product, internal-tool, or OSS concept against Amazon's Working Backwards PRFAQ gauntlet before committing to a spec. Triggers on: \"work backwards\", \"write a PRFAQ\", \"press release first\", \"is this idea worth building\", \"pressure-test this concept\", \"filter this before brainstorm\", \"is this a real product\". Also catches solution-first pitches (\"I want to build X that does Y\") and technology-first pitches (\"use AI to...\") that need customer-first filtering. Produces a binary pass/fail verdict, not a polished doc. Hardcore coaching — direct, skeptical, concrete. On pass, hands off to brainstorm-beagle with a concept brief. Does NOT write code, plan implementation, scaffold projects, or draft specs.
Apply to any non-trivial work, not just bulk work: edits, migrations, analyses, checks. Build the tool that does it or proves it (codemod, script, generator, or a skill your subagents follow) instead of working by hand. The tool is the artifact a reviewer can rerun
Product changelog and release notes that users actually read. Covers categorization, user-facing language, visuals, and distribution. Use for: release notes, changelogs, product updates, feature announcements, versioning. Triggers: changelog, release notes, product update, version notes, what's new, feature announcement, product changelog, update log, release announcement, version release, product release, ship notes
Writes, validates, and converts ProductSpec files (.product-spec.md), the Markdown format for recording product intent before implementation. Use when authoring a new Product Spec, converting an existing PRD or feature doc into one, validating spec files locally or in CI, or recording how a spec's intent changed over time in a Decision Trace. For implementing code against a Product Spec that already exists, use the productspec skill instead.
Identify programmatic SEO page patterns worth building for your product — vs/ pages, integrations/, for-{industry}/, alternatives-to/, use-cases/ — and design the template structure, data model, and priority order. Outputs a complete pSEO blueprint with URL patterns, title templates, content frameworks, and data sources per variable.
Shared cross-agent project memory for costly trial-and-error, hard-won solutions and verified corrections to outdated lessons. This skill MUST be invoked before starting work in an existing project, to load what was already learned there, and MUST be invoked again as that work wraps up, to record what this session learned before it ends. MUST also be invoked on the triggers below to record something new, and SHOULD be invoked whenever the user states something worth remembering about how this project behaves. MUST NOT be used for task lists or open bugs, which belong in the issue tracker or AGENTS.md. Triggers on: 記一下, 之前踩過什麼雷, 學到什麼, 有什麼教訓, remember this, lesson learned, project learnings, 記錄一下, 之前遇過的, 把這個記起來
UK taxation expert for HMRC compliance, Making Tax Digital (MTD ITSA/VAT) and Self-Assessment: explain tax treatment; compute income tax/NI/dividend/CGT with band-by-band breakdown; advise on deadlines/forms/penalties; and support MTD developer integration + tax software UX/flows. Use WebSearch (gov.uk/HMRC) to verify current rates and mandation timelines. (project)
The meta-skill that powers all other AI tools. Prompt engineering for creative applications is the art and science of communicating with AI models to produce exactly what you envision—in images, video, audio, and text. This isn't just "write better prompts." It's understanding how different models interpret language, how to structure requests for different modalities, how to iterate systematically, and how to build prompt libraries that encode your creative vision. The best prompt engineers have developed intuition for what words trigger what responses in each model. This skill is foundational—it amplifies the effectiveness of every other AI creative skill. Master this, and you master the interface to all AI creation. Use when "prompt, prompting, prompt engineering, better prompts, prompt optimization, how to prompt, prompt strategy, prompt library, prompt template, make AI understand, prompt-engineering, prompting, meta-skill, ai-creative, foundational, optimization, iteration" mentioned.
Rewrites a rough prompt, voice dump, or half-written instruction into an agent-ready prompt. Use when the user asks to make a prompt better, enhance/refine a prompt, clean up instructions for an agent, or improve pasted prompt text. One-shot transformer; does not interview.
Access and test Vercel deployments protected by Vercel Authentication, SSO, or Deployment Protection with agent-browser. Use when a preview or production URL redirects to a Vercel login page, returns a protection 401 or 403, or needs short-lived Trusted Sources OIDC authentication instead of a static bypass secret or public exception.
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.