Agent Skills
Instruction packs for your AI agent — browse standalone skills, tool add-ons and skills that need setup first.
✦ Standalone skills2,358
Listed for general use, with no separate prerequisite named.
🧰 Tool add-ons426
Listed as skills bundled with a specific tool, with no separate prerequisite named.
🔌 Needs setup first88
Each relies on something you set up separately — such as an app, a command-line tool or an account — and its page names what that is.
automattic
88 skills needing setupspotify-player
★ 391,509by openclaw
Terminal Spotify playback/search via spogo (preferred) or spotify_player.
🔌 Needs the spogo or spotify_player CLI and Spotify Premium
summarize
★ 391,509by openclaw
Summarize or transcribe URLs, YouTube/videos, podcasts, articles, transcripts, PDFs, and local files.
🔌 Needs the summarize CLI
things-mac
★ 391,509by openclaw
Add, update, list, search, or inspect Things 3 todos, inbox, today, projects, areas, and tags on macOS.
🔌 Needs the things CLI and Things 3 on macOS
tmux
★ 391,509by openclaw
Control tmux sessions/panes for interactive CLIs: list, capture output, send keys, paste text, monitor prompts.
🔌 Needs tmux
trello
★ 391,509by openclaw
Manage Trello boards, lists, and cards via the Trello REST API.
🔌 Needs a Trello API key and token, plus curl and jq
wacli
★ 391,509by openclaw
Send third-party WhatsApp messages or sync/search WhatsApp history via wacli, not normal active chats.
🔌 Needs the wacli CLI and a WhatsApp login
xurl
★ 391,509by openclaw
xurl CLI for authenticated X posts, replies, reads/search, DMs, media upload, followers, auth status, or raw v2 API calls.
🔌 Needs the xurl CLI and X API credentials
n8n:linear-issue
★ 195,330by n8n-io
Fetch and analyze Linear issue with all related context. Use when starting work on a Linear ticket, analyzing issues, or gathering context about a Linear issue.
🔌 Needs Linear's MCP server and the GitHub CLI (gh)
n8n:human-like-code-review
★ 195,330by n8n-io
Reviews a GitHub pull request like a thoughtful human reviewer and writes the feedback to a markdown file. Prioritizes context, architecture fit, solution complexity, bugs, security edge cases, and missing tests. Use when given a PR URL to review, or when the user says /human-like-code-review.
🔌 Needs the GitHub CLI (gh)
fix-ci-failures
✓★ 187,144by microsoft
Investigate and fix CI failures on a pull request. Use when CI checks fail on a PR branch — covers finding the PR, identifying failed checks, downloading logs and artifacts, extracting the failure cause, and iterating on a fix. Requires the `gh` CLI.
🔌 Needs the GitHub CLI (gh)
project-setup-info-context7
✓★ 187,144by microsoft
Comprehensive setup steps to help the user create complete project structures in a VS Code workspace. This tool is designed for full project initialization and scaffolding, not for creating individual files. When to use this tool: when the user wants to create a new complete project from scratch; when setting up entire project frameworks (TypeScript projects, React apps, Node.js servers, etc.); when initializing Model Context Protocol (MCP) servers with full structure; when creating VS Code extensions with proper scaffolding; when setting up Next.js, Vite, or other framework-based projects; when the user asks for "new project", "create a workspace", or "set up a [framework] project"; when you need to establish a complete development environment with dependencies, config files, and folder structure. When NOT to use this tool: when creating single files or small code snippets; when adding individual files to existing projects; when making modifications to existing codebases; when the user asks to "create a file" or "add a component"; for simple code examples or demonstrations; for debugging or fixing existing code. This tool provides complete project setup including folder structure creation, package.json and dependency management, configuration files (tsconfig, eslint, etc.), initial boilerplate code, development environment setup, and build and run instructions. Use other file creation tools for individual files within existing projects.
🔌 Needs the Context7 MCP server
agent-tui
✓★ 105,779by google-gemini
Main Agents: Do NOT use this skill directly. If you need to test the TUI, invoke the `tui_tester` subagent. Drive terminal UI (TUI) applications programmatically for testing, automation, and inspection. Use when: automating CLI/TUI interactions, regression testing terminal apps, or verifying interactive behavior. Also use when: user asks "what is agent-tui", "what does agent-tui do", "demo agent-tui", "show me agent-tui", "how does agent-tui work", or wants to see it in action.
🔌 Needs the agent-tui CLI
qa
★ 102,956by browser-use
QA-test a website or web app and return a 1-5 quality score (5 = flawless, 1 = broken) with evidence. Use when the user wants to test, QA, evaluate, score, or "check how good" a site, page, flow, or app — including a local dev server (e.g. "qa test localhost:5173", "does the checkout work?", "rate this landing page"). Drives a real Browser Use cloud browser, tunneling localhost automatically.
🔌 Needs the browser-harness CLI and Browser Use Cloud
x402
★ 102,956by browser-use
Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — "just use it" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing touches your codebase) or "build it in" (install the SDK and write the key + code into your project). Walks through wallet setup, funding, .env, and a ~$1 test run. Use when the user asks about x402, pay-per-use, USDC payments, or wants Browser Use Cloud without an API key. For the free-tier signup (reverse-CAPTCHA → API key), use `browser-use cloud signup` or the `cloud` skill instead.
🔌 Needs the Browser Use SDK and a USDC wallet on Base
cloud
★ 102,956by browser-use
Documentation reference for using Browser Use Cloud — the hosted API and SDK for browser automation. Use this skill whenever the user needs help with the Cloud REST API (v2, v3, or v4), browser-use-sdk (Python or TypeScript), X-Browser-Use-API-Key authentication, cloud sessions, browser profiles, profile sync, CDP WebSocket connections, stealth browsers, residential proxies, CAPTCHA handling, webhooks, workspaces, skills marketplace, liveUrl streaming, pricing, or integration patterns (chat UI, subagent, adding browser tools to existing agents). Also trigger for questions about n8n/Make/Zapier integration, Playwright/ Puppeteer/Selenium on cloud infrastructure, or 1Password vault integration. Do NOT use this for the open-source Python library (Agent, Browser, Tools config) — use the open-source skill instead.
🔌 Needs a Browser Use Cloud API key
depot-container-builds
✓★ 35,336by posthog
Configures and runs Depot remote container builds using `depot build` and `depot bake`. Use when building Docker images, creating Dockerfiles with Depot, pushing images to registries, building multi-platform/multi-arch images (linux/amd64, linux/arm64), debugging container build failures, optimizing Dockerfile layer caching, using docker-bake.hcl or docker-compose builds, or migrating from `docker build` / `docker buildx build` to Depot. Also use when the user mentions depot build, depot bake, container builds, image builds, or asks about Depot's build cache, build parallelism, or ephemeral registry.
🔌 Needs the Depot CLI and a Depot account
depot-github-runners
✓★ 35,336by posthog
Configures Depot-managed GitHub Actions runners as a drop-in replacement for GitHub-hosted runners. Use when setting up or migrating GitHub Actions workflows to use Depot runners, choosing runner sizes (CPU/RAM), configuring runs-on labels, setting up ARM or Windows or macOS runners, troubleshooting GitHub Actions runner issues, configuring egress filtering, using Depot Cache with GitHub Actions, or running Dagger/Dependabot on Depot runners. Also use when the user mentions depot-ubuntu, depot-windows, depot-macos runner labels, or asks about faster/cheaper GitHub Actions runners. Not for Depot CI, the separate engine that reads .depot/workflows/ — that is the depot-ci skill.
🔌 Needs a Depot account and the Depot GitHub App on a GitHub organization
react-doctor
✓★ 35,336by posthog
Diagnose and fix React codebase health issues. Use when reviewing React code, fixing performance problems, auditing security, or improving code quality.
🔌 Needs the react-doctor CLI
land
✓★ 25,801by openai
Land a PR by monitoring conflicts, resolving them, waiting for checks, and squash-merging when green; use when asked to land, merge, or shepherd a PR to completion.
🔌 Needs the GitHub CLI (gh)
push
✓★ 25,801by openai
Push current branch changes to origin and create or update the corresponding pull request; use when asked to push, publish updates, or create pull request.
🔌 Needs the GitHub CLI (gh)
manim-video
★ 15,091by browser-use
Production pipeline for mathematical and technical animations using Manim Community Edition. Creates 3Blue1Brown-style explainer videos, algorithm visualizations, equation derivations, architecture diagrams, and data stories. Use when users request: animated explanations, math animations, concept visualizations, algorithm walkthroughs, technical explainers, 3Blue1Brown style videos, or any programmatic animation with geometric/mathematical content.
🔌 Needs Manim Community Edition, LaTeX and ffmpeg
dotagents
✓★ 8,701by sentry
Manage agent skill dependencies with dotagents. Use when asked to "add a skill", "install skills", "remove a skill", "update skills", "dotagents init", "agents.toml", "agents.lock", "sync skills", "list skills", "set up dotagents", "configure trust", "add MCP server", "add hook", "wildcard skills", "user scope", or any dotagents-related task.
🔌 Needs the dotagents CLI
agent-device
✓★ 7,136by shopify
Interact with iOS simulator or Android emulator/device using snapshot-based coordinates. Uses accessibility tree snapshots for precise element targeting, with screenshot verification as fallback. Use when navigating the app on a simulator/emulator.
🔌 Needs the agent-device CLI
create-pr
✓★ 6,148by microsoft
Create a pull request using the repository PR template. Use when asked to: create PR, open PR, push and create PR, submit PR, open pull request, send changes for review.
🔌 Needs the GitHub CLI (gh)
hex1b
✓★ 6,148by microsoft
CLI tool for automating any terminal application — TUI apps, shells, CLI tools, REPLs, and more. Use when you need to launch a process in a virtual terminal, capture its screen output, inject keystrokes or mouse input, take screenshots, record sessions, or assert on what's visible.
🔌 Needs the Hex1b .NET tool
github-discussion-query
✓★ 4,723by github
Query GitHub discussions with jq filtering and reusable selectors.
🔌 Needs the GitHub CLI (gh)
github-issue-query
✓★ 4,723by github
Query GitHub issues with jq filtering and reusable selectors.
🔌 Needs the GitHub CLI (gh)
github-pr-query
✓★ 4,723by github
Query GitHub pull requests with jq filtering and reusable selectors.
🔌 Needs the GitHub CLI (gh)
github-codebase-briefing
★ 1,743by google-labs-code
Generates a deeply contextual, progressive-disclosure briefing for any GitHub repository. It builds a mental model of the code before analyzing issues and PRs to provide actionable insights. Use when asked for a "GitHub report," "repo status," "daily briefing," or to "catch up on a codebase."
🔌 Needs the GitHub CLI (gh)
generate-project-plan
✓★ 1,704by figma
Generate a FigJam project plan board from a PRD plus codebase context. Interactive flow: research → propose sections → per-section deep research → per-section content + block-shape proposal → create FigJam → skeleton → fill → diagrams → wrap. Each content block (section, nested section, intro callout, table, multi-column text, sticky column, diagram section, metadata strip) has its own subskill reference file. Use when the user asks for 'project plan in FigJam', 'interactive project plan', '/generate-project-plan', or provides a PRD and wants per-section confirmation on content + rendering.
🔌 Needs Figma's MCP server and a Figma account