bOpen Plugin Dev

Audit agents and skills across the plugin ecosystem for triggering, structure, progressive disclosure, permissions, and benchmark readiness. Apply for requests to audit agents, review skill quality, check skill health, validate plugin skills, or run periodic authoring maintenance.

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).

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.

Run skill benchmarks and write evals that score a skill against a no-skill baseline. Use for "benchmark this skill", "run the skill evals", "write an eval for this skill", or "did this skill actually help?".

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, default-branch release delivery, browser-confirmed Bun publishing, and credential recovery only when publishing explicitly reports an authentication failure. Do not trigger for unrelated uses of "release" (e.g. GitHub releases, press releases).

Split a large Claude Code or Codex plugin into a small core plus optional modules. Use for "split this plugin", "my plugin is too big", "reduce startup context", "Codex is omitting my skills", "core plus optional packs", or "publish part of my plugin separately". Covers marketplace subdirectory sourcing, the dependency field's silent-load behaviour, Codex adapter regeneration, and vendored-skill placement. Use agent-auditor to measure first and benchmark-skills to verify routing after.

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.

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.

Publish a plugin or standalone skill when the user asks to "publish a plugin", "release a plugin", "bump plugin version", "update a Claude Code plugin", "update a Codex plugin", or "publish skills". Covers synchronized host manifests, changelog and README updates, repository promotion, cache refresh, and standalone Agent Skills.

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.