Skills
97,222 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Design and build web interfaces at design-studio quality, not AI-template quality. Use for any new page, landing page, dashboard, app shell, pricing, settings, form or single component, web or mobile (native app screens with seenry-apps), for redesigns and visual polish, and for matching a reference. Designs the brand's identity first, the way studios do (a truth, a type voice, one color field, one graphic device, one image treatment), studies real identities, studio sites and category leaders from Seenry MCP, builds the page as an application of that identity on a proven product and motion floor, and does not finish until a strict slop check passes and a blind critic scores the page at big-company level
Run the self-improvement agent to review this session and the ~/.learnings/ log files. Use this skill whenever the user explicitly asks to review learnings, promote entries to CLAUDE.md, do an end-of-session review, or analyze GitHub PRs/issues for recurring patterns. Also use when the user says "promote", "review learnings", "what have we learned", or "self-improvement". Do NOT use this skill just for logging — logging happens automatically without the skill (see Passive Logging below). This skill is specifically for the *review and promotion* workflow.
Capture errors, corrections, and feature requests so your OpenClaw agent improves over time instead of repeating the same mistakes. Use when commands fail, users correct the agent, a requested capability is missing, external tools break, or a better recurring workflow is discovered.
Re-encode verbose prose into a dense telegraphic register — punctuation as connectives, label frames, verbless assertions — without losing normativity or precision. Use when compressing system prompts, tool/function descriptions, skill bodies, or agent instructions; reducing token count or context bloat; making documentation token-efficient for LLM input; or rewriting text in compressed notation.
Transfer tokens from OpenAnt wallet on Solana or Base. Use when the user wants to send, transfer, or pay tokens via OpenAnt. Supports native coins (SOL, ETH) and tokens (USDC) by name, plus arbitrary tokens by mint/contract address. Covers "send SOL", "transfer USDC", "send tokens", "pay someone", "send ETH on Base", "transfer to address", "OpenAnt wallet send".
Query and manage Sentry error-tracking data — list and search issues, drill into events and stack traces, inspect projects and releases, resolve/ignore issues, and pull stats. Use this whenever the user mentions a Sentry issue, crash, error group, or exception; pastes a sentry.io or self-hosted Sentry URL; asks "why is this erroring", "how many times has this happened", "what's the top error in {project}", "resolve this issue", or wants a Sentry-based digest — even if they don't say "API". Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.
Configure the OpenTelemetry Collector with Sentry Exporter for multi-project routing and automatic project creation. Use when setting up OTel with Sentry, configuring collector pipelines for traces and logs, or routing telemetry from multiple services to Sentry projects.
Comprehensive 7-phase SEO optimization workflow covering technical SEO auditing, keyword research strategy, on-page optimization, content SEO and E-E-A-T, structured data implementation, link building, and AI search optimization. Use when auditing search engine visibility, diagnosing ranking issues, implementing schema markup, conducting keyword research, optimizing content for E-E-A-T signals, or adapting for AI-driven search (AI Overviews, SGE).
Expert guide for technical SEO auditing. Use when checking crawlability, indexing issues, page speed, Core Web Vitals, mobile-friendliness, HTTPS configuration, robots.txt, XML sitemaps, canonical tags, hreflang, redirect chains, HTTP status codes, or diagnosing technical SEO problems.
Use when complex problems require systematic step-by-step reasoning with ability to revise thoughts, branch into alternative approaches, or dynamically adjust scope. Ideal for multi-stage analysis, design planning, problem decomposition, or tasks with initially unclear scope.
Manages session state transitions per SESSION_ORCHESTRATION.md. Controls state updates at /work phase boundaries, escalated transitions on error, and initialized restoration on session resume. Internal workflow use only. Do NOT load for: user session management, login state, app state handling.
One-time setup that maps the codebase and gathers user-provided product context to write a root PROJECT.md overview of what the project is, who it serves, how it is structured, and how it runs. Use when the user invokes $setup-project-md, says "setup project md", "create PROJECT.md", or asks for a complete project overview document at the repo root.
Installs Scalekit, then picks AgentKit or SaaSKit for the project. Use when the user wants to install Scalekit, add the plugin, or decide which kit to use. It does not configure a dashboard connection (that's `setup-agentkit`) or set app login env (that's `setup-saaskit`).
End-to-end branch delivery: commit (no AI attribution) → push → open a pull request → ensure a Board work item exists (create one per task, assigned to the configured user, if none) and link it → after merge, clean up branch and worktree. Auto-detects the platform from the remote — Azure Repos + Boards (azure-devops-node-api SDK; OAuth Bearer push fallback via `az`) or GitHub (Octokit; `gh` for auth). Scripts are TypeScript, run via `bun`. Use whenever asked to "ship", "ship it", "ship this branch", "open a PR", "push and open a PR", "raise a PR", "deliver this", "send this for review", or "create a PR and link the work item" — and when a direct push to main is blocked and the change needs to go through a PR instead. Also covers snapshotting the current state as an annotated git tag — use whenever asked to "save the current state", "tag this", "snapshot the state", "create a checkpoint", "tag a release point", or "mark where we are" (a git-tag checkpoint, distinct from PR labels/tags). Also opens a just-created (or any) PR in a chosen browser account profile — use whenever asked to "open the PR in my browser", "open it in Edge/Chrome", or "open the PR as <account>".
Complete guide to background job processing with Sidekiq in Ruby on Rails. Use this skill when: (1) Creating background jobs, (2) Configuring queues and workers, (3) Implementing retry logic and error handling, (4) Designing idempotent jobs, (5) Setting up scheduled/recurring jobs, (6) Optimizing job performance.
Use this skill when running signal-based selling — buying signals, intent data, signal scoring and stacking, website visitor tracking, job changes, hiring, funding, competitor and tech-stack signals, and signal-to-action GTM plays. Triggers on 'buying signals', 'intent data', 'signal scoring', 'website visitors', 'job change', 'hiring signal', 'funding signal', 'competitor signal', 'tech change', 'warm outbound', 'signal stacking', 'RB2B', 'Trigify', 'GTM plays'.
Signals scout for the parts of a product people barely use. Measures each clickable element and page against the reach of where it lives, gives each barely used one a likely cause, and reports the ones that are reachable and still not used.
Use when the user says “simmer this,” “refine this,” “hone this,” “iterate on this,” or asks to improve a specific artifact over multiple rounds. Runs an iterative refinement loop with investigation-first judges that read the code, understand the problem, and propose evidence-based improvements. Auto-selects a single judge or multi-judge board based on complexity. Works on any artifact type: documents, prompts, specs, emails, creative writing, API designs, pipelines, codebases. Supports multi-file workspace targets, runnable evaluators, and open-ended optimization (model selection, pipeline topology, prompt tuning).
Judge board subskill for simmer. Dispatches a panel of judges with different lenses, runs one deliberation round in which they challenge each other's scores, then synthesizes consensus scores and a single ASI. Drop-in replacement for simmer-judge that produces the identical output format. Do not invoke directly; the simmer orchestrator dispatches it when JUDGE_MODE is board.
Reflect subskill for simmer. Records iteration results in a trajectory table, tracks the best candidate, handles regression rollback, and passes ASI forward to the next round. Supports both single-file and workspace modes. Do not invoke directly; called by the simmer orchestrator after each judge round.
Setup subskill for simmer. Inspects the artifact or workspace, infers evaluation contracts and search space, proposes a complete assessment to the user, and produces a setup brief after confirmation. Conversational rather than form-based: the agent works to understand the problem, then presents its findings. Do not invoke directly; called by the simmer orchestrator.
Use when writing a new Agent Skill, editing an existing SKILL.md, or getting a skill change actually deployed — where the source lives versus the installed copy, why editing the installed copy silently does nothing, the edit → gate → commit → push → re-install → verify sequence, how to publish a skill repo so `skills add` finds it, how to word a `description` so it triggers on real requests without stealing another skill's, and when something should be an instructions-file rule instead of a skill at all.
Packages the user's agent skills into individual zips for easy upload to platforms. The default source is the current user's ~/.agents/skills, one <name>.zip per skill (keeping the top-level <name>/ directory inside the zip), with a MANIFEST.txt attached. User-invoked; the model does not trigger it automatically.
Create new skills, improve existing skills, and understand skill best practices for Builder.io Fusion. Use when the user wants to create a skill, build a slash command, automate a workflow, add custom AI instructions, create reusable AI behaviors, or asks how to extend Fusion's capabilities in their project. Also use when the user wants to improve, audit, or troubleshoot an existing skill's triggering or behavior.
Premium Skill Creator by Kevin Jeppesen (The Operator Vault). Create better OpenClaw skills with a premium first-use setup wizard pattern, minimal context bloat, and reusable scaffolding. Links: YouTube https://www.youtube.com/@kevin-jeppesen | Skool https://skool.com/operator-vault | Site https://theoperatorvault.io | X https://x.com/seo_ecom | LinkedIn https://www.linkedin.com/in/kevin-jeppesen/ | Facebook https://www.facebook.com/kevinjeppesen/
Use when the user wants to measure or set up evals/checks for one of their skills — how fast it is, whether its output is valid, whether it fires when expected, or whether its opening classification/routing gate labels inputs correctly.
Convert Claude Code skills to work on OpenAI Codex, Google Gemini CLI, Google Antigravity, and Cursor. Analyzes platform-specific features, generates target files (openai.yaml, AGENTS.md, GEMINI.md, .mdc rules), adapts frontmatter, converts MCP config, and produces compatibility reports. Use when user says "convert skill", "port skill", "multi-platform", "skill for codex", "skill for gemini", "skill for antigravity", "skill for cursor", "cross-platform skill", "convert to codex", "convert to gemini", "convert to antigravity", or "convert to cursor".
Comprehensive guide for discovering, understanding, and installing Claude Code skills from skills.sh marketplace. Use this skill when users want to (1) browse or search skills.sh for recommendations, (2) get skill recommendations by role (developer, marketer, designer, product manager), (3) understand how a specific installed skill works by reading and explaining its SKILL.md, (4) learn the anatomy and structure of skills, or (5) find and install skills that match their specific workflow needs. This is NOT for creating new skills (use skill-creator instead).
Enforce code readability and state minimisation before opening or updating a pull request. Use when code is functionally complete and needs a final simplification pass focused on skimmability: reducing arguments, removing optionality and overrides, collapsing unnecessary abstractions, preferring discriminated unions, adding assertions at boundaries, handling variants exhaustively, deleting incidental changes, and making the diff shorter, clearer, and easier to review.
Create custom slash commands for Claude Code including syntax, arguments, bash execution, file references, and frontmatter configuration. Use when creating slash commands, custom commands, .md command files, or when asked about command creation, /command syntax, or command best practices.
Generate a polished, presentation-ready HTML slide deck from a topic, document, or set of notes. Use this whenever the user says 'make a slide deck,' 'build a presentation,' 'turn this into slides,' 'create a deck for,' 'pitch deck,' 'investor deck,' 'training deck,' or asks for slides on any topic. Outputs a single self-contained HTML file with scroll-snap navigation and a clean visual system. The deck should look like a designer made it, not a default template.
Annotate and filter VCF variants with SnpEff and SnpSift. SnpEff predicts functional effects (HIGH/MODERATE/LOW/MODIFIER), genes, transcripts, AA changes, HGVS; SnpSift filters and adds ClinVar/dbSNP. Java CLI with Python subprocess integration. Use ANNOVAR for multi-database annotation; Ensembl VEP for REST API; SnpEff for fast CLI with pre-built genomes.
Apply Cialdini's six principles of persuasion — Reciprocity, Commitment/Consistency, Social Proof, Liking, Authority, and Scarcity — to analyze or design influence strategies. Use this skill when the user needs to make messaging more persuasive, analyze why a campaign works or doesn't, design sales or marketing copy, or understand social influence tactics — even if they say 'how do we convince people', 'why is this ad effective', or 'make this more persuasive'.
Turn content pillars, target platforms, and an honest posting cadence into a realistic 2-week content plan for LinkedIn, X, Instagram, Threads, Bluesky, and Facebook. Use when the user asks for a "content calendar", says "plan my week", "plan my next two weeks", or "what should I post this month". It balances pillars against formats (post, thread, carousel), anchors entries to real dates like launches and events, and deliberately leaves slack for reactive posting. It reads social-context.md for the user's brand voice, pillars, platforms, and stated cadence before planning anything. The output is a plan the user executes themselves — a markdown schedule of ideas with working hooks, not a queue of finished posts.
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.