b-open-io
134 verified skills1,279 total stars
devops-scripts
This skill should be used when the user asks to "check deployment health", "verify service connectivity", "validate environment variables before deploy", "run a pre-deploy smoke check", or "diagnose a Vercel, Railway, Redis, or Postgres connection issue". Runs deterministic shell scripts for infrastructure health checks and environment validation, returning structured JSON instead of burning context on inline bash logic.
development14
chrome-cdp
This skill should be used when the user asks to "inspect this page in Chrome", "debug what's happening in my browser", "read the browser console logs", "interact with the page open in Chrome", or "attach to my live Chrome session". Interacts with the user's local Chrome browser session via Chrome DevTools Protocol — no extension, no Puppeteer — but only after explicit user approval to inspect, debug, or interact with an open tab.
tools14
cost-tracking
This skill should be used when tracking API spend, analyzing billing data, monitoring service costs, running budget reports, or optimizing agent spend across Anthropic, Vercel, Railway, and other platforms. Invoke when asked about "cost tracking", "billing analysis", "spend report", "API costs", "usage monitoring", "budget vs actual", "cost optimization", or "which agents cost the most".
development14
coordinator
Always active when a capable current main session in Claude Code or Codex is planning non-trivial implementation and cheaper or specialized executors are available, including native subagents, Grok workers, Codex workers, or lower-tier Claude agents. Trigger before code is written to decide where each unit executes. Keep planning, specs, design intent, review, verification, and git in the main seat; dispatch bounded code-writing volume with explicit ownership and acceptance criteria.
development14
ui-audio-theme
This skill should be used when the user asks to "generate a UI sound theme", "create button click sounds for my app", "design notification sounds", or "build a coordinated audio theme for my dashboard or wallet app", "make game menu sounds", "create HUD feedback sounds", "design TV navigation sounds", "audit the sounds on my existing site", "check that transaction sounds are wired", "review UI audio wiring", or "edit a generated UI sound". Generates, audits, edits, and wires cohesive UI audio themes mapped to semantic interactions via ElevenLabs and ffmpeg, with an interactive local picker for auditioning, revising, reassigning, and accepting candidates. Also covers a synthesized web micro-interaction delivery path via cuelume and a production-agnostic interaction taxonomy for choosing a distinct sound per named moment.
tools14
front-desk
This skill should be used in Claude Code or Codex when the user asks "who handles X?", "what agents are available?", "how do I contact Y?", "team roster", "what services do we use?", "who should I talk to about Z?", "what skills are available?", "where do I find skill X?", or needs help routing to the right agent or service provider. Also use when checking agent-adapter availability, finding/installing skills, sending emails on behalf of the org, or drafting communications. Route SOC 2, audit readiness, policy drafting, and evidence-gathering questions to Anthony in product-skills, with Paul in bopen-tools for technical control validation.
tools14
plugin-settings
This skill should be used when the user asks to "add plugin settings", "make a plugin configurable", "store per-project plugin configuration", "use settings.local.json", "create a plugin state file", "expose skill settings in Agent Master", or "add a skill interface". Distinguishes official Claude Code settings from project-owned configuration and documents bOpen Agent Master skill interface discovery.
tools14
create-next-project
This skill should be used when the user asks to "create a new project", "scaffold a Next.js app", "initialize a new app", "start a new project", "set up a new Next.js project", or mentions "create-next-project". Provides a guided, opinionated full-stack Next.js project initialization with Biome, Tailwind v4, shadcn/ui, better-auth, and Vercel deployment. Uses agent teams for parallel execution.
devops14
humanize
Invoke this skill whenever producing text that a human will read — emails, messages, documentation, reports, blog posts, announcements, commit messages, or any prose draft. Trigger signals include: task is a writing or editing task, output will be sent or published, user says "humanize", "make this sound less AI", "de-AI this", "this sounds like ChatGPT", "make it sound more natural", or "edit this". Do not wait for the user to ask — apply this automatically before delivering any human-facing draft. Skipping this means delivering text with predictable AI patterns that erodes trust and sounds generated.
development14
software-factory
Use this skill when designing, configuring, or hardening a software factory — an AI developer workflow where agents iterate toward a goal — a goal an agent iterates toward on its own with a real verification gate, persistent state, and a stop condition. Invoke it when the user mentions "build a loop", "agentic loop", "self-iterating agent", "run this on a schedule/cron", "/loop or /goal", "Ralph loop", "maker-checker", "fleet of agents", "autonomous workflow", "AI developer workflow", "ADW", "software factory", "agentic SDLC", or wants an agent to keep working a goal unattended until it's verifiably done. Also use when scoping whether a loop is even worth building, when picking a verification gate, when deciding what a loop is allowed to touch (blast radius), or when a loop is burning tokens without producing accepted work.
development14
shaders
This skill should be used when the user asks to "write a custom Three.js shader", "create a GLSL shader effect", "build a TSL shader", "debug a WebGL or WebGPU shader issue", or "build a post-processing pipeline". Covers shader workflow, the TSL node system, GLSL patterns, debugging, performance optimization, and post-processing with pmndrs/postprocessing.
development14
design-game-ui
This skill should be used when the user asks for "game UI", "app-to-game UI", "video game HUD", "controller navigation", "D-pad navigation", "TV app", "ten-foot interface", "game UI key bindings", "controller-first menu", "console-style menu", "TV remote focus", or "directional navigation".
content-media14
skill-publish
This skill should be used when the user asks to "publish a plugin", "release a plugin", "bump plugin version", "update a Claude Code plugin", "update a Codex plugin", "publish skills", or mentions plugin publishing, plugin release, or skill distribution. Handles synchronized host manifests, changelog and README updates, git workflow, cache refresh, and standalone Agent Skills.
tools14
generative-ui
This skill should be used when the user asks about "generative UI", "dynamic UI", "AI-generated interfaces", "json-render", "render JSON as UI", "generate a dashboard", "create dynamic components", "AI UI generation", "MCP App UI", "deliver UI in chat", "interactive chat interface", or needs to decide whether to use static components vs AI-generated UI. Covers the json-render framework, renderer selection, catalog design, MCP Apps delivery (ui:// resources for in-chat interactive UIs), and integration with gemskills for visual asset generation.
tools14
auth-md
This skill should be used when the user asks to "implement auth.md", "add agent registration", "design delegated agent signup", "support service_auth", "mint or verify an ID-JAG", "build an agent identity provider", "make Better Auth support auth.md", or review agent-facing OAuth, account linking, consent, claims, revocation, and discovery architecture. Covers the experimental WorkOS auth.md v0.6.0 proposal and prevents conflation with Better Auth Agent Auth Protocol, OAuth Dynamic Client Registration, ordinary email signup, and RFC 8628 Device Authorization.
tools14
mcp-apps
This skill provides guidance for building MCP Apps, the official io.modelcontextprotocol/ui extension for interactive HTML interfaces inside MCP hosts. This skill should be used when the user asks to "create an MCP App", "add UI to an MCP tool", "build interactive MCP", "ui:// resource", "sandboxed iframe MCP", "interactive chat UI", "embed UI in chat", "MCP tool with interface", or needs capability negotiation, resource CSP, app-only tools, host lifecycle, or progressive text fallbacks.
tools14
setup
This skill should be used when the user says "bopen setup", "setup ui", "harness install", "audit my setup", "install everything", "unified installer", "setup plan", "/bopen-setup", or wants a single view of which bOpen plugins, CLIs, env keys, third-party skills, agents, and hooks are installed across their agent harness. It audits live state, lets the user select what to fix, and emits a runtime-tailored instruction plan — it never installs anything itself. For hooks-only configuration (enabling/disabling a single hook without the full harness view) the hook-manager skill remains canonical; this skill's Overview and per-plugin tabs point there for that narrower job.
tools14
deploy-agent-team
This skill should be used when the user says "deploy a team", "spin up agents to work on this", "use all our agents", "coordinate specialists", or wants to break a large task into parallel sub-tasks handled by multiple domain experts simultaneously. Orchestrates Claude Code's experimental agent team system using the full bopen-tools specialist roster.
tools14
visual-wayfinder
This skill should be used when the user asks to "open Visual Wayfinder", "answer a Wayfinder ticket visually", "turn this decision into a configurator", "show Wayfinder choices as a dashboard", "prototype the Wayfinder questionnaire", or wants interactive choice cards, tradeoff controls, rankings, ranges, toggles, and consequence previews for one active Wayfinder decision. It wraps the Wayfinder skill and JSON Render; it never replaces the tracker or resolves more than the active decision.
testing14
x-research
This skill should be used for AI-powered X/Twitter research via xAI Grok when the user asks "what's trending", "social sentiment", "summarize X discussion about", "analyze X conversation about", or "research topic on X". Returns AI summaries with analysis, not raw tweets. For raw tweet data, use x-user-timeline, x-tweet-search, or x-tweet-fetch. Requires XAI_API_KEY.
development14
hammertime
This skill should be used when the user mentions a behavioral rule they want enforced, says "always do X", "never do Y", "stop doing Z", "from now on", asks about HammerTime rules, wants to create a stop hook rule, mentions behavioral guardrails, or wants to understand how the HammerTime stop hook system works. Teaches how to write rules for the HammerTime stop hook system.
documentation14
linear-planning
This skill should be used when the user wants to plan a project, feature, or bug fix using Linear as the agent control plane. Use when the user says "plan this in Linear", "create Linear tickets", "break this down into tasks", "push to Linear", "set up our board for this feature", or wants to turn a description or spec into well-structured, agent-ready Linear issues. Requires the official Linear MCP server to be configured.
tools14
statusline-setup
This skill should be used when the user asks to "create a status line", "customize status line", "set up statusline", "configure Claude Code status bar", "install ccstatusline", "add project colors to status line", "show git branch in status", "display token usage", or mentions Peacock colors, powerline, or status line configuration.
development14
voice-clone
This skill should be used when the user asks to "clone a voice", "create a custom voice from audio samples", "replicate a celebrity voice style", or "build a voice for a fictional character". Chains the full ElevenLabs Instant Voice Cloning (IVC) pipeline — finding reference audio, preparing samples, uploading to IVC, testing the clone with text-to-speech, and tuning voice settings.
development14
threejs-r3f
This skill should be used when the user asks to "build a Three.js scene", "set up React Three Fiber", "animate a mesh with useFrame", "load a GLTF or GLB model", or "add physics with react-three/rapier". Covers scene setup, Drei helpers, the asset pipeline, responsive canvas, and performance budgets for Three.js and React Three Fiber projects.
tools14
wave-coordinator
This skill should be used in Claude Code or Codex when dispatching more agents than the host can run concurrently, when context budget management is needed, or when generating multiple variations of the same output. Coordinates native Claude agents, Codex custom or built-in subagents, and mixed worker lanes with wave sizing, context budget tracking, and directive diversity. Use when the user says "fan out", "generate variations", "batch agents", "wave dispatch", or asks for large-scale subagent work.
development14
orchestrator
Use this skill when a capable current Claude Code or Codex main session should coordinate native specialist agents, external implementation workers such as Grok, and an independent advisor such as Fable. Trigger for "orchestrate this", "use Grok workers", "use Fable as advisor", "Codex main with workers", "delegate implementation but keep control here", cross-model workflows, or complex work that needs a main-seat plan, parallel specialists, worker dispatch, second opinions, review, verification, and git ownership. Do not hardcode or replace the user's current main model.
development14
runtime-context
This skill should be used when the user asks "what runtime am I in", "detect the execution environment", "adapt behavior for Claude Code vs a hosted bot", or "check what tools are available in this environment". Detects the current agent execution environment (Claude Code, Vercel Sandbox, or local dev) and adapts behavior accordingly — for agents or bots that run in Claude Code as subagents AND as hosted bots, or a SOUL.md/SKILL.md that must work across runtimes.
tools14
saas-launch-audit
This skill should be used when the user asks to "audit my SaaS", "check if I'm ready to launch", "review my launch checklist", "verify my pricing", "audit my payment setup", "check my AI visibility", "prepare for Product Hunt", "validate my SaaS for launch", or mentions launching a SaaS product. Provides a comprehensive, repeatable checklist with PASS/FAIL verification and actionable next steps.
testing14
persona
Capture writing style profiles, track a pool of users, scan social intelligence, and apply style-matching to draft content. Use when asked to "capture my writing style", "draft a post in my voice", "scan what's trending", "add someone to the pool", or "track @username".
testing14
plaid-integration
This skill should be used when the user asks to "integrate Plaid", "connect a bank account", "sync bank transactions", "add Plaid Link to my app", or "implement financial data access". Integrates the Plaid API for bank account connections and transaction syncing in TypeScript/Bun applications.
development14
nextjs-upgrade
Assess and upgrade a Next.js project after resolving the target release from current official documentation. Includes tested automation and breaking-change guidance for the Next.js 15 to 16 migration. Use when the user says 'upgrade Next.js', 'migrate to Next.js 16', 'update my Next.js app', 'run the Next.js codemod', 'my Next.js version is outdated', or when a migration plan or baseline build comparison is needed.
tools14
paperclip-plugin-dev
This skill should be used when the user asks to "scaffold a Paperclip plugin", "write a Paperclip plugin manifest", "add a UI slot to a Paperclip plugin", "publish a Paperclip plugin to npm", or "install a Paperclip plugin". Builds, publishes, and installs Paperclip plugins correctly, with critical lessons learned from real publishing failures — plugin capabilities, jobs, webhooks, and agent tools.
tools14
reinforce-skills
Invoke this skill when: modifying any CLAUDE.md file, adding a new skill or agent to a plugin, user says 'update the skill map', 'add this to the map', 'register this agent', 'skills keep getting forgotten', 'I keep forgetting which skill to use', 'agents keep getting forgotten', 'add skill map', 'update agent map', 'sync skills to CLAUDE.md', or when setting up a new project. This skill injects compressed SKILL-MAP and AGENT-MAP directive blocks into CLAUDE.md so skill names and agent IDs persist across the session without fading from context. Skipping this means agents will forget skill names mid-session, fail to invoke the right skill, and guess at agent IDs — causing silent capability loss that is hard to diagnose.
tools14
notebooklm
This skill should be used when the user asks to "query my NotebookLM notebook", "ask NotebookLM about these sources", "get a citation-backed answer from my documents", or "search my NotebookLM library". Provides browser automation, library management, and persistent auth for querying Google NotebookLM notebooks directly from Claude Code, returning source-grounded answers from Gemini instead of general knowledge.
tools14
cli-demo-gif
This skill should be used when the user asks to "record a terminal demo", "generate a CLI demo GIF", "make a vhs recording", "create a terminal GIF for the README", or "capture a CLI walkthrough as a GIF". Generates CLI demo GIFs using vhs (Charmbracelet) for README files and documentation.
tools14
benchmark-skills
This skill should be used when the user asks to "write evals for a skill", "benchmark this skill", "test skill effectiveness", "run the skill benchmark harness", "measure skill quality vs baseline", or "add an evals.json alongside a skill". Invoke whenever someone wants to test, benchmark, or evaluate whether a skill actually helps compared to no skill at all.
testing14
frontend-performance
This skill should be used when the user asks to "optimize my Next.js app", "why is this page slow", "reduce my bundle size", "improve Core Web Vitals", or "run a Lighthouse audit". Diagnoses and fixes Next.js frontend performance issues using Lighthouse, bundle analysis, and animation best practices — covering LCP, TBT, and CLS.
development14
claudex
This skill should be used when a Claude Code session needs to keep working after Anthropic usage runs out, or when the user asks to run the Claude Code harness on GPT-5.6 Sol. Trigger phrases include "my Anthropic usage ran out", "I'm out of Claude usage", "usage limit reached, what now", "keep working on another model", "run Claude Code on GPT-5.6 Sol", "use GPT-5.6 Sol as the model", "set up claudex", "claudex isn't working", "route the harness through CLIProxyAPI", or "bill against my ChatGPT/Codex subscription". It stands up a local proxy so the Claude Code CLI runs on OpenAI's Codex backend as an escape hatch, and diagnoses that setup when it drifts. macOS + Homebrew.
tools14
visual-proposal
This skill should be used when the user asks to "make a visual proposal", "write this up so I can share it", "present these options visually", "diagram the trade-offs", "turn this plan into something reviewable", or requests a shareable design pitch, architecture proposal, RFC, options comparison, or visual roadmap for work that has not been built. It produces one self-contained, theme-aware HTML page led by grounded diagrams. Use visual-review instead for completed code changes; do not use this skill for internal task tracking.
development14
agent-onboarding
This skill should be used when the user asks to "create a new agent", "onboard a new agent", "add an agent to the team", "deploy a new bot", "register an agent with Paperclip", or "add this agent to the roster". Provides the complete end-to-end checklist for bringing a new agent onto the bOpen team — design, write, avatar, plugin, Paperclip registration, roster, and optional ClawNet bot deployment.
tools14
clawnet-cli
This skill should be used when the user asks to "work on the ClawNet CLI", "debug clawnet-paperclip-plugin", "explain ClawNet vault architecture", "fetch content from ORDFS", or "publish an agent or organization to the ClawNet registry". Reference for ClawNet CLI internals, architecture, and recent changes to the registry, vault, and publishing flow.
tools14
free-roam-testing
Use this skill to run a discovery loop that explores a running app the way a curious or chaotic human would — randomized, unscripted paths, weird inputs, edge interactions — to surface NEW bugs, broken flows, confusing UX, and slow spots, then file them as deduplicated tickets. Invoke it when the user says "free roam", "explore the app", "monkey test", "find issues I don't know about", "exploratory testing", "use it like a real user", "discovery loop", "surface new bugs", or wants an agent to poke around an app autonomously and report what's broken. This is the producer half of the loop architecture — it feeds tickets to the execution loop. NOT for scripted regression tests (that's the tester agent's verification gate). Always respects a never-touch list and a blast-radius boundary before mutating anything.
testing14
hook-manager
Manage bopen-tools plugin hooks — list, enable, disable, diagnose, and run first-time setup. This skill should be used when the user asks to "list hooks", "disable a hook", "enable a hook", "hook setup", "which hooks are running", "turn off the publish gate", "hooks config", or when session context contains a [BOPEN-HOOKS-SETUP] directive.
tools14
visual-review
Use this skill to turn a PR, branch, commit, or working-tree diff into a visual recap — a single self-contained, theme-aware HTML page with before/after UI wireframes, schema/API contract summaries, a file footprint map, and annotated key-change diffs — so a reviewer sees the SHAPE of a change before reading raw lines. Invoke it when the user asks to critique a change, review a diff visually, run a code review or diff review, or says "recap this PR", "visual recap", "show me what this branch changed", "summarize this diff visually", "make this PR reviewable", "explain what changed", or before reviewing any large, multi-file, UI-heavy, or schema/API-touching change. Code-review agents (code-auditor, architecture-reviewer) should produce one as the opening artifact of any big review. NOT for small single-file diffs — those review faster as a raw diff via `bunx critique --web --open`.
development14
codex-agent-setup
Explicit-only installer for bopen-tools Codex custom agents. Use ONLY when the user explicitly asks to install, update, check, uninstall, or set up Codex agents / custom agents from this plugin — phrases include "install codex agents", "setup codex agents", "update codex agents", "check codex agents", "install all codex agents", "uninstall codex agents", "project codex agents", "user codex agents", or "install bopen agents into .codex". Never auto-invoke. Never silently modify global Codex configuration.
tools14
x-user-lookup
Get X/Twitter user profile by username. Use when user asks "who is @username", "get X profile", "lookup Twitter user", "find X account", "user details", "follower count for". Requires X_BEARER_TOKEN.
data-ai13
x-tweet-fetch
Fetch a specific tweet by URL or ID. Use when user shares an X/Twitter URL (https://x.com/... or https://twitter.com/...), asks "get this tweet", "fetch tweet", "what does this tweet say", "read this X post". Requires X_BEARER_TOKEN.
testing13
visual-recap
Use this skill to turn a PR, branch, commit, or working-tree diff into a visual recap — a single self-contained, theme-aware HTML page with before/after UI wireframes, schema/API contract summaries, a file footprint map, and annotated key-change diffs — so a reviewer sees the SHAPE of a change before reading raw lines. Invoke it when the user says "recap this PR", "visual recap", "show me what this branch changed", "summarize this diff visually", "make this PR reviewable", "explain what changed", or before reviewing any large, multi-file, UI-heavy, or schema/API-touching change. Code-review agents (code-auditor, architecture-reviewer) should produce one as the opening artifact of any big review. NOT for small single-file diffs — those review faster as a raw diff via the critique skill.
development13
advisor
Active when a Claude Code or Codex main session needs an independent, read-only second opinion at a commitment boundary. Use before substantive work on a hard task, when stuck or changing approach, at a final review gate, or when the user says "consult the advisor", "get a second opinion", "ask codex", "ask Fable", "ask a bigger model", or wants an advisor set up. Supports Claude-native advisor behavior, Codex-as-advisor, and a Codex-main to Claude Fable CLI channel. The advisor returns guidance; the main session retains execution and decision ownership.
tools13
x-user-timeline
Get recent tweets from an X/Twitter user. Use when user asks "what has @username posted", "recent tweets from", "user's X posts", "show timeline for", "what is @user saying". Requires X_BEARER_TOKEN.
tools13
arbitrage
Always active when coding in a Claude (Fable/Opus) session alongside a codex quota. Triggers whenever implementation work is being planned, scoped, or about to start — before writing any code — to decide where each piece of work executes. Routes judgment (planning, specs, design intent, review, visual validation, git) to the premium session and all code-writing volume to codex dispatches, with guardrails learned from real dispatch failures.
development13
hunter-skeptic-referee
This skill should be used when the user asks to 'find bugs', 'do a thorough code review', 'run a security audit', 'hunt for bugs', 'check for correctness issues', or 'review this code for edge cases'. Orchestrates a three-phase adversarial review using three isolated agents — Jerry (Hunter), Kayle (Skeptic), Jason (Referee) — to neutralize sycophancy and produce high-fidelity bug reports. User-facing command: /bug-hunt
development13
loop-engineering
Use this skill whenever designing, configuring, or hardening an autonomous agent "loop" — a goal an agent iterates toward on its own with a real verification gate, persistent state, and a stop condition. Invoke it when the user mentions "build a loop", "agentic loop", "self-iterating agent", "run this on a schedule/cron", "/loop or /goal", "Ralph loop", "maker-checker", "fleet of agents", "autonomous workflow", or wants an agent to keep working a goal unattended until it's verifiably done. Also use when scoping whether a loop is even worth building, when picking a verification gate, when deciding what a loop is allowed to touch (blast radius), or when a loop is burning tokens without producing accepted work.
development13
agent-auditor
Comprehensive audit skill for agents and skills across the plugin ecosystem. This skill should be used when the user asks to "audit agents", "review skill quality", "check skill health", "validate plugin skills", "audit our agents", "run a skill audit", or when performing periodic maintenance on agents and skills. Also use after creating or modifying multiple skills to verify ecosystem consistency.
tools13
remind
Search and recall previous Claude Code conversation sessions. Use this skill whenever the user asks to remember, recall, find, or look up something from a past conversation or session. Triggers on phrases like: 'remember when we...', 'what did we do about...', 'find that conversation where...', 'when did I last work on...', 'what was that command/approach/solution we used for...', 'look up my past sessions about...'. Also use this skill when the user references prior work context that isn't in the current session, asks to continue work from a previous session, or wants to find a specific discussion, decision, or code snippet from their conversation history. Even vague references to past work ('that thing we did', 'the approach from last week') should trigger this skill.
development13
npm-publish
This skill should be used when the user wants to publish a package to npm, bump a version, release a new version, or mentions "npm publish", "bun publish", "version bump", or "release to npm". Handles version bumping, changelog updates, git push, npm publishing, and automatic token rotation via agent-browser when auth expires. Do not trigger for unrelated uses of "release" (e.g. GitHub releases, press releases).
documentation13
x-tweet-search
Search recent X/Twitter posts by query. Returns RAW TWEETS (last 7 days). Use when user asks "search X for", "find tweets about", "what are people saying about", "Twitter search", "raw tweets about". For AI summaries/sentiment, use x-research instead. Requires X_BEARER_TOKEN.
data-ai13
geo-optimizer
This skill should be used when the user asks to "audit for AI visibility", "optimize for ChatGPT", "check GEO readiness", "analyze hedge density", "generate agentfacts", "check if my site works with AI search", "test LLM crawlability", "check discovery gap", or mentions Generative Engine Optimization, AI crawlers, Perplexity discoverability, or NANDA protocol.
testing12
github-stars
This skill should be used when adding GitHub star counts, star buttons, star widgets, or GitHub social proof to a website or app. Applies when the user says "add GitHub stars", "show star count", "add a star badge", "GitHub badge", "star widget", "GitHub social proof", "stargazer count", or wants to display how many stars a repo has on a marketing page, header, or landing page. Also applies when integrating the GitHub API for repository metadata display.
development12
agent-decommissioning
This skill should be used when the user asks to "retire an agent", "decommission an agent", "remove an agent from the team", "shut down a bot", "remove a bot", "sunset an agent", or "take an agent offline permanently". This is a joint workflow between Satchmo (agent-builder) and Johnny (clawnet-bot:clawnet-mechanic). Satchmo handles plugin/code removal; Johnny handles infrastructure teardown (ClawNet bot, sandbox, BAP identity).
tools12
check-version
Check if the bopen-tools plugin is up to date by comparing local vs GitHub versions. Use this skill at the start of any session where the agent needs current skill/agent definitions, when the user asks 'is everything up to date?', 'check for updates', 'am I on the latest version?', or when you suspect skills may have changed since last install. Also use proactively when a skill seems to behave differently than documented or when instructions reference features you don't recognize. Completes in under 100ms.
tools12
charting
Full-stack data visualization and charting intelligence. This skill should be used when the user asks to "create a chart", "visualize this data", "build a dashboard", "plot this", "graph these metrics", "show me a chart of", "make a bar chart", "create a line graph", "build a heatmap", or needs help choosing the right chart type, selecting a charting library, or engineering the data pipeline from raw database state to rendered visualization. Covers chart selection, data transformation, library choice by scale, performance optimization, and accessibility.
development12
html-to-pdf
This skill should be used when the user asks to "design a business card", "make a printable PDF", "render HTML to PDF", "generate a postcard", "build print collateral", "set up an HTML print pipeline", or needs help with bleed, safe areas, font embedding, or QR generation for print. Provides a Playwright-based pipeline with multiple bundled templates and theme variants for business cards (minimal, watercolor light, watercolor dark) and instructions for adding new templates.
development12
perf-audit
Run local performance audits on a project without network calls. This skill should be used when the user says 'audit performance', 'check bundle size', 'find large images', 'check for heavy dependencies', 'run a perf audit', 'how big is my bundle', 'optimize images', 'find oversized assets', or before any performance optimization work. Also use when an agent needs baseline metrics before making changes. All scripts output structured JSON to stdout.
testing12
process-cleanup
Finds stale and resource-hungry processes, scores them by waste, and presents a cleanup report with friendly names. Use this skill when the user says 'what's eating my RAM', 'kill stale processes', 'clean up my machine', 'free up memory', 'my computer is slow', 'what's running', 'too many things open', or asks to find/kill background processes. Also use proactively when you notice sluggishness, process spawn failures, or many duplicate processes during normal work.
data-ai12
publish-request
Use this skill when preparing to publish a package, plugin, or skill and you need human approval first. Invoked when the user says "publish", "release", "ship", or "push to registry" but no approved Linear ticket exists yet. Runs preflight checks, creates or updates a Linear ticket with a structured release plan, moves it to Ready for Review, then stops — it does NOT execute the publish command.
tools12
wait-for-ci
Wait for CI/CD pipelines to complete after pushing code, then act on results. This skill should be used after git push, after creating a PR, when the user says 'wait for CI', 'check if the build passes', 'monitor the pipeline', 'wait for checks', 'is CI green?', or whenever the agent needs to verify that pushed code passes CI before proceeding. Also use when an agent workflow involves push-then-verify cycles, deployment monitoring, or needs to block on CI results before taking the next step. Supports GitHub Actions, GitLab CI, and Vercel deployments.
development12
confess
Invoke this skill BEFORE ending any session, marking a task done, or saying 'complete'. Also invoke when the user says 'are you sure?', 'did you miss anything?', 'anything else?', 'what did I miss?', 'confess', or 'audit your work'. This is a proactive self-audit — do not wait to be asked. Skipping this means shipping incomplete work, broken references, untested paths, or unmentioned concerns the agent noticed but buried. Covers: incomplete changes, untested assumptions, pattern violations, hidden concerns, and cleanup debt.
testing12
code-audit-scripts
Run deterministic code security and quality scans — secret detection, debug artifact cleanup, and TODO/FIXME tracking. Use this skill before any security review, code audit, PR review, or when the user says 'scan for secrets', 'find debug logs', 'check for TODOs', 'audit this code', 'security scan', or 'clean up before shipping'. Also use proactively before deployments or when reviewing unfamiliar codebases. Runs all scans in parallel for speed.
development12
critique
This skill should be used when the user asks to "show me the changes", "what did you change", "let me see the diff", "review the code", "open web preview of changes", "show me what you worked on", "compare branches", "explain what changed", or wants to view git diffs in a terminal UI, web browser, or get AI-powered code review explanations.
development12
json-render-react
React renderer for json-render that turns JSON specs into React components. Use when working with @json-render/react, building React UIs from JSON, creating component catalogs, or rendering AI-generated specs.
development11
convert-web-app
This skill should be used when the user asks to "add MCP App support to my web app", "turn my web app into a hybrid MCP App", "make my web page work as an MCP App too", "wrap my existing UI as an MCP App", "convert iframe embed to MCP App", "turn my SPA into an MCP App", or needs to add MCP App support to an existing web application while keeping it working standalone. Provides guidance for analyzing existing web apps and creating a hybrid web + MCP App with server-side tool and resource registration.
tools11
create-mcp-app
This skill should be used when the user asks to "create an MCP App", "add a UI to an MCP tool", "build an interactive MCP View", "scaffold an MCP App", or needs guidance on MCP Apps SDK patterns, UI-resource registration, MCP App lifecycle, or host integration. Provides comprehensive guidance for building MCP Apps with interactive UIs.
tools11
ezkl
This skill should be used when the user asks about "zero-knowledge ML", "zkML", "EZKL proofs", "prove ML inference", "verify model output", "ZK proof for machine learning", "ONNX to ZK circuit", "on-chain ML verification", "EVM verifier for ML", or needs to generate, verify, or deploy zero-knowledge proofs for machine learning models. Also use when working with @ezkljs/engine, ezkl CLI, or Lilith managed proving.
tools11
json-render-react-email
React Email renderer for json-render that turns JSON specs into HTML or plain-text emails using @react-email/components and @react-email/render. Use when working with @json-render/react-email, building transactional or marketing emails from JSON, creating email catalogs, rendering AI-generated email specs, or when the user mentions react-email, HTML email, or transactional email.
development11
json-render-remotion
Remotion renderer for json-render that turns JSON timeline specs into videos. Use when working with @json-render/remotion, building video compositions from JSON, creating video catalogs, or rendering AI-generated video timelines.
development11
remotion-best-practices
Best practices for Remotion - Video creation in React
development11
json-render-image
Image renderer for json-render that turns JSON specs into SVG and PNG images via Satori. Use when working with @json-render/image, generating OG images from JSON, creating social cards, or rendering AI-generated image specs.
testing11
json-render-shadcn
Pre-built shadcn/ui components for json-render. Use when working with @json-render/shadcn, adding standard UI components to a catalog, or building web UIs with Radix UI + Tailwind CSS components.
development11
json-render-react-native
React Native renderer for json-render that turns JSON specs into native mobile UIs. Use when working with @json-render/react-native, building React Native UIs from JSON, creating mobile component catalogs, or rendering AI-generated specs on mobile.
development11
add-app-to-server
This skill should be used when the user asks to "add an app to my MCP server", "add UI to my MCP server", "add a view to my MCP tool", "enrich MCP tools with UI", "add interactive UI to existing server", "add MCP Apps to my server", or needs to add interactive UI capabilities to an existing MCP server that already has tools. Provides guidance for analyzing existing tools and adding MCP Apps UI resources.
tools11
json-render-core
Core package for defining schemas, catalogs, and AI prompt generation for json-render. Use when working with @json-render/core, defining schemas, creating catalogs, or building JSON specs for UI/video generation.
development11
bsocial
This skill should be used when the user asks to "post to BSocial", "like a post", "unlike", "follow user", "unfollow", "send message", "repost", "friend request", "on-chain social media", "BMAP", "BSocial protocol", "channel message", "create on-chain post", "read BSocial posts", or needs social operations (posts, likes, follows, messages, reposts, friends) on BSV blockchain.
testing5
create-script-template
This skill should be used when the user asks to "create a script template", "add a new template to ts-templates", "create a BitCom template", "build an OP_RETURN template", or mentions creating templates for protocols like SIGMA, AIP, MAP, BAP, B. Guides creation of @bsv/sdk ScriptTemplate implementations.
development5
calculate-mining-difficulty
This skill should be used when the user asks to "calculate mining difficulty", "convert target to difficulty", "analyze block difficulty", "BSV difficulty calculation", or needs to compute difficulty from block headers.
tools5
create-bap-identity
This skill should be used when the user asks to "create BAP identity", "new BAP", "Type42 identity", "Legacy BAP identity", "generate BAP", "set up BAP identity", "initialize BAP", "update profile", "get profile", "attest attribute", "BAP attestation", or needs to create or manage Bitcoin Attestation Protocol identities.
testing5
lookup-block-info
This skill should be used when the user asks to "get block info", "lookup block by height", "block by hash", "block header details", or needs to retrieve BSV block information.
development5
junglebus
This skill should be used when the user asks about "JungleBus", "transaction streaming", "BSV subscriptions", "real-time blockchain data", "GorillaPool API", or needs to subscribe to blockchain events.
development5
stratum-v2
This skill should be used when the user asks "what is Stratum v2", "mining protocol v2", "binary mining protocol", "encrypted mining", "job declaration protocol", or needs to understand Stratum v2 for BSV mining infrastructure.
devops5
validate-bsv-script
This skill should be used when the user asks to "validate BSV script", "analyze locking script", "parse unlocking script", "check script opcodes", or needs to validate and analyze Bitcoin scripts using @bsv/sdk.
development5
wallet-send-bsv
This skill should be used when the user asks to "send BSV", "transfer satoshis", "create payment transaction", "send from WIF", "P2PKH transaction", or needs to build, sign, and broadcast P2PKH transactions from a WIF private key using @bsv/sdk.
development5
estimate-transaction-fee
This skill should be used when the user asks to "estimate transaction fee", "calculate BSV fee", "fee per byte", "transaction cost", or needs to estimate fees based on transaction size and current rates.
tools5
wallet-brc100
This skill should be used when the user asks to "implement BRC-100 wallet", "use wallet-toolbox", "TypeScript BSV wallet", "BRC-100 implementation", "desktop wallet", "Electron wallet", "browser wallet", "IndexedDB wallet storage", "wallet actions", "wallet baskets", "UTXO management", "createAction", "listOutputs", "wallet certificates", "WalletClient", "noSend", "BEEF payment", "pay-beef", "send BEEF", "Transaction.fromBEEF", "toHexBEEF", or needs guidance on building conforming wallets using @bsv/wallet-toolbox or connecting to a user's BRC-100 wallet via WalletClient.
tools5
codex-agent-setup
Explicit-only installer for the BSV Skills David Codex custom agent. Use ONLY when the user explicitly asks to install, update, check, uninstall, or set up the BSV Skills, David, or Bitcoin Codex agent, including "install David in Codex", "update the BSV Skills Codex agent", or "check bsv_skills_bitcoin". Never auto-invoke for ordinary BSV, Bitcoin, wallet, transaction, identity, mining, or blockchain requests.
development5
key-derivation
This skill should be used when the user asks to "derive keys", "use Type42", "use BRC-42", "derive child keys", "use BIP32", "use HD keys", "create mnemonic", "convert mnemonic to key", "derive BAP identity keys", "derive encryption keys", or mentions key derivation, hierarchical deterministic wallets, invoice numbers, or child key generation on BSV.
business5
manage-bap-backup
This skill should be used when the user asks to "export BAP identity", "import BAP backup", "view BAP backup", "manage BAP backup", "backup BAP identity", or needs to work with BAP identity backup files using the bap CLI.
tools5
encrypt-decrypt-backup
This skill should be used when the user asks to "encrypt backup", "decrypt .bep file", "bitcoin-backup CLI", "backup wallet", "Touch ID password cache", "upgrade backup iterations", or needs to encrypt/decrypt BSV backup files using the bbackup CLI.
tools5
check-bsv-price
This skill should be used when the user asks "what is BSV price", "BSV to USD", "current BSV rate", "BSV market cap", or needs to fetch current BSV price and exchange rate information.
development5
broadcast-arc
This skill should be used when the user asks to "broadcast transaction", "submit to ARC", "broadcast via ARC", "broadcast BEEF", "broadcast EF", "use GorillaPool ARC", "use TAAL ARC", "arc.gorillapool.io", "arc.taal.com", "ArcConfig", "broadcastMany", or needs to submit a signed BSV transaction to the network using the ARC broadcaster from @bsv/sdk.
development5
smart-contracts
This skill should be used when the user asks about "BSV smart contract", "Bitcoin smart contract", "write a smart contract", "create a BSV contract", "use sCrypt", "use Runar", "compile to Bitcoin Script", "stateful contract", "covenant", "OP_PUSH_TX", "escrow contract", "auction contract", "token contract", "deploy smart contract", "test smart contract", or needs to author, compile, test, or deploy Bitcoin SV smart contracts using high-level languages.
development5
stratum-v1
This skill should be used when the user asks to "implement Stratum v1", "mining pool protocol", "JSON-RPC mining", "pool-miner communication", "mining.subscribe", or needs to build Stratum v1 mining infrastructure.
development5
ordfs
This skill should be used when the user asks "what is ORDFS", "how to use ordfs.network", "ordfs API", "access on-chain content", "inscription gateway", "ordfs query parameters", "ordfs sequence", "ordfs directory", "ordfs preview", "recursive inscriptions", "ord-fs/json", or needs to reference, access, or serve on-chain content through ORDFS.
development5
wallet-encrypt-decrypt
This skill should be used when the user asks to "encrypt message with BSV key", "decrypt with private key", "ECDH encryption", "AES-256-GCM BSV", "EncryptedMessage", "BRC-2 encryption", or needs to encrypt/decrypt data using BSV keys and @bsv/sdk.
development5
wallet-brc100-go
This skill should be used when the user asks to "implement BRC-100 wallet in Go", "use go-wallet-toolbox", "Go BSV wallet", "BRC-100 Go implementation", or needs guidance on building conforming wallets using Go wallet-toolbox.
tools5
bsv-standards
This skill should be used when the user asks about any BRC standard (BRC-1 through BRC-113), "what is BRC-61", "what is BRC-42", "what is BEEF", "what is BUMP", "Compound Merkle Path", "Merkle proof format", "what is MAP protocol", "what is AIP", "what is B protocol", "what are BSV standards", "what is SIGMA", "what is BAP", "what is paymail", "what is 1Sat Ordinals", "what is BSV-20", "what is STAS", "lookup BRC", "BitCom protocols", "what is bitcoin-auth", "what is bitcoin-backup", "what is bitcoin-image", "what is Bitcoin Schema", "what is DPP", "what is PacketPay", "what is Authrite", "what is PIKE", "what is P2PKH", "what is Push Drop", "overlay network", "SPV", "outpoint format", "what is ORDFS", "Mandala token", or needs to understand any BSV ecosystem standard, protocol, or specification. Covers all 12 BRC categories: Wallet, Transactions, Scripts, Key Derivation, Payments, Overlays, Peer-to-Peer, Tokens, Outpoints, Opinions, State Machines, and Apps.
development5
message-signing
This skill should be used when the user asks to "sign a message", "verify a signature", "use BSM", "use BRC-77", "implement Sigma signing", "create signed messages", "authenticate with Bitcoin", "sign with AIP", "AIP protocol", or mentions message signing, signature verification, ECDSA signatures, or authentication protocols on BSV.
testing5
review-script-template
This skill should be used when the user asks to "review a script template", "audit a template", "check template implementation", "validate ts-templates code", or mentions reviewing BitCom templates like AIP, MAP, SIGMA, BAP. Validates ScriptTemplate implementations against best practices.
development5
lookup-bsv-address
This skill should be used when the user asks to "lookup address", "check address balance", "address UTXOs", "address history", or needs to retrieve BSV address information from WhatsOnChain API.
development5
yours-wallet
This skill should be used when the user asks to integrate "Yours Wallet", "connect a BSV wallet", use "BRC-100", "pay with BSV wallet", add "wallet checkout in a web app", use "yours-wallet-provider", build a "pay with Yours Wallet" button, access "window.CWI", or connect a React app to a BRC-100 wallet.
development5
decode-bsv-transaction
This skill should be used when the user asks to "decode transaction", "parse tx hex", "transaction details", "analyze transaction", "decode BEEF", "parse BEEF hex", "decode EF transaction", "inspect transaction", or needs to decode BSV transaction hex (raw, Extended Format, or BEEF) into human-readable format.
development5
team-group-photo
This skill should be used when the user asks to "create team photo", "generate group portrait", "make team banner", "team image in any style", "group shot with multiple people", or needs a composite image featuring multiple team members arranged together in any art style.
data-ai3
edit-image
This skill should be used when the user asks to "edit an image", "modify a photo", "inpaint", "outpaint", "extend an image", "replace object in image", "add element to image", "resize image for social media", "crop image", "adapt image for Twitter", "convert image to OG format", or needs AI-powered image editing with masks.
development3
generate-video
This skill should be used when the user asks to "generate a video", "create a video", "animate an image", "text to video", "image to video", "make a video clip", "video from image", "bring this image to life", "subject-consistent video", "match character likeness in video", "interpolate between frames", or needs AI video generation using Veo 3.1. Handles prompt rewriting, style application, reference images for subject consistency, and Gemini Veo video generation API calls.
tools3
deck-creator
This skill should be used when the user asks to "create a deck", "make a presentation", "build slides", "pitch deck", "investor deck", "sales presentation", "design a deck", "interactive presentation", "presenter mode", "HTML slides", "video background deck", "deck playground", "visual deck editor", "deck builder UI", "publish deck link", or needs to generate a complete deck with minimal friction. Handles low-question discovery, early Deck Creator UI launch, theme selection, copywriting, parallel slide generation, PDF stitching, optional HTML presenter, and publishing workflows.
development3
upscale-image
This skill should be used when the user asks to "upscale an image", "increase image resolution", "make image bigger", "enlarge image", or "enhance image resolution". Requires Vertex AI credentials.
data-ai3
style-creator
This skill should be used when the user asks to "add a new style", "create a style", "add an art style", "new aesthetic", "custom style", "make a style for", or needs to add a new art style to the gemskills style library. Guides the complete workflow from defining the style to generating and optimizing the reference tile.
development3
visual-planner
This skill should be used when the user asks to "plan a workflow", "diagram an agent system", "visualize an architecture", "map out a pipeline", "create a flow diagram", "draw agent connections", "design a multi-agent system", "show how agents interact", "make a system diagram", "visualize a data pipeline", "map out a process", "diagram my workflow", "create an architecture diagram", "plan agent orchestration", "brainstorm a system design", "show the flow between components", "interactive workflow diagram", "workflow canvas", "visual-planner", "open in tldraw", or "plan this project visually". Produces tldraw .tldr diagrams natively — the standard infinite canvas format. Includes a thin playground wrapper with planning-specific UI (phase controls, agent assignment, KPI bar, agent callback bridge) and an "Open in tldraw" button for standalone editing.
development3
section-dividers
This skill should be used when the user asks to "create section dividers", "make transparent dividers", "generate decorative borders", "create parallax dividers", "design section transitions", "make HR dividers", "crystal dividers", "organic borders", "silhouette borders", or needs transparent PNG dividers for web sections.
development3
optimize-images
This skill should be used when the user asks to "optimize images", "compress images", "reduce image file size", "make images smaller", "optimize PNGs", "optimize JPEGs", "speed up website images", "reduce bundle size images", or needs help with image compression for web projects. Provides workflows and scripts for batch image optimization using sharp.
development3
generate-svg
This skill should be used when the user asks to "generate SVG", "create SVG", "make a logo", "create vector graphics", "generate icon", "make vector illustration", "vectorize image", or needs scalable vector graphics generated via AI.
development3
generate-image
This skill should be used when the user asks to "generate an image", "create a banner", "make artwork", "create an illustration", "generate a logo", "make a graphic", "design a header", "AI art", "img2img", "social share image", "OG image", "open graph image", "Twitter card", "hero image", "cover photo", "profile picture", "social media graphic", or needs AI image generation. Handles prompt rewriting and Gemini 3 Pro image generation API calls.
development3
generate-icon
This skill should be used when the user asks to "generate an icon", "create a favicon", "make an app icon", "create iOS icon", "create Android icon", "generate PWA icons", "make desktop app icon", "create Windows icon", "create macOS icon", "app store icon", "Play Store icon", "App Store icon", or needs AI-generated icons with platform-specific sizing.
testing3
avatar-portrait
This skill should be used when the user asks to "create an avatar from a photo", "generate a portrait avatar", "make a profile image", "convert headshot to styled portrait", "team member avatar", "character-style avatar", or needs likeness-preserving avatars in any style (including pixel art).
data-ai3
ask-gemini
This skill should be used when the user asks to "ask Gemini", "get Gemini's opinion", "have Gemini review", "improve writing style", "make less AI-sounding", "get feedback on article", "review this draft", "Nano Banana", "Gemini API help", "Gemini models", or needs a second opinion on content, writing, code, or design. Supports text questions and up to 10 images.
development3
browsing-styles
This skill should be used when the user asks to "browse art styles", "pick a style", "choose a style", "select a style", "list available styles", "search styles", "show style options", "what styles are available", "explore artistic styles", "open style browser", "style picker", or needs to see available styles for image generation. Launch the visual browser (browse.ts) when the user wants to interactively pick a style.
data-ai3
segment-image
This skill should be used when the user asks to "segment an image", "identify objects", "extract objects", "generate masks", "find objects in image", or needs AI-powered image segmentation.
data-ai3
pixel-avatar
Compatibility alias for legacy pixel-avatar requests. Use this skill when old prompts explicitly reference pixel-avatar, then route to avatar-portrait with a pixel-art style requirement.
testing3
setup-convex
Setup Sigma Auth OAuth integration in a Convex application. Guides through installing @sigma-auth/better-auth-plugin, configuring Convex environment variables, and setting up the auth server.
tools
bitcoin-auth-diagnostics
Diagnose and troubleshoot bitcoin-auth token generation and verification issues. This skill should be used when users encounter authentication failures, signature verification errors, or integration problems with the bitcoin-auth library.
development
tokenpass
This skill should be used when the user asks about "TokenPass", "install TokenPass", "run TokenPass server", "TokenPass desktop app", "TokenPass API", "personal identity server", "be your own OAuth provider", or needs help setting up, configuring, or integrating TokenPass Server or Desktop applications. Provides installation, configuration, and API integration guidance.
development
codex-agent-setup
Explicit-only installer for the Sigma Auth Siggy Codex custom agent. Use ONLY when the user explicitly asks to install, update, check, uninstall, or set up the Sigma Auth or Siggy Codex agent, including "install Siggy in Codex", "update the Sigma Auth Codex agent", or "check sigma_auth_guide". Never auto-invoke for ordinary OAuth, authentication, Better Auth, BAP, wallet, session, passkey, or security requests.
development
setup-nextjs
Setup Sigma Auth OAuth integration in a Next.js application. Guides through installing @sigma-auth/better-auth-plugin, configuring environment variables, creating auth client, implementing sign-in flow, and setting up API routes for token exchange with Bitcoin-native authentication.
tools
device-authorization
This skill should be used when the user asks to "implement device auth", "add device authorization", "authenticate desktop app", "authenticate CLI tool", "device code flow", "RFC 8628", "poll for token", "get user info after device auth", or mentions authenticating apps that can't handle browser redirects. Provides step-by-step guidance for device authorization with Sigma Identity.
tools