[ PORTABLE SKILL ]

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.

PART OF
bopen-tools

Complete plugin installation is recommended so this skill keeps its agents, hooks, commands, and runtime context.

Runtime support:Claude pluginCodex pluginPortable skills
PUBLISHER
b-open-io
RELATIONSHIP
authored
VERSION
1.0.0
BENCHMARK
unknown
[ RECOMMENDED INSTALL ]

Install bopen-tools

The complete plugin is the supported path. It preserves everything the publisher designed to work alongside this skill.

Claude Code

VERIFIED

Codex

VERIFIED
[ ADVANCED · INDIVIDUAL SKILL ]

Install only this skill

Use this narrower path only when you intentionally want the portable SKILL.md without the plugin’s surrounding capabilities.

Skills CLI

VERIFIED
  • Installs only the portable skill; it omits plugin hooks, agents, commands, apps/MCP configuration, and unlisted companion skills.
[ PROVENANCE ]

Trace it to the source.

UPSTREAM SOURCE
No separate upstream declared
DISTRIBUTED DIGEST
sha256:b1ee8b5ca85524cf8f73416a23d682c832bf693ae897d97f04a651780f6e3dca
LOCK HASH
Not applicable

Companion skills

No required companion skills are declared.

Agents using this skill

Satchmo, bOpen agent

Satchmo

Designs, integrates, and productionizes AI agents using OpenAI/Vercel SDKs and related stacks. Specializes in tool-calling, routing, memory, evals, resilient chat UIs, visual workflow planning, and live agent deployment via ClawNet. Can brainstorm agent architectures collaboratively and produce interactive workflow diagrams.

Leaf, bOpen agent

Leaf

Map and geospatial specialist expert in MapLibre GL JS, Mapbox GL JS, Leaflet, CesiumJS, deck.gl, OpenLayers, Google Maps, ArcGIS, D3-geo, Turf.js, Protomaps/PMTiles, react-map-gl, Kepler.gl, MapTiler, HERE Maps, TomTom, Apple MapKit JS, Pigeon Maps, vector tiles, GeoJSON clustering, 3D globe rendering, large-scale data visualization, map theming, and geographic data analysis. Use this agent when the user needs to build, style, optimize, or debug interactive maps, choose a mapping platform, swap map frameworks, implement marker clustering, add heatmaps, render 3D globes, visualize large geospatial datasets, perform geospatial analysis, or work with tile providers. Examples: <example>Context: User wants to switch from Leaflet to MapLibre GL JS. user: "Swap Leaflet for MapLibre" assistant: "I'll use the cartographer agent to migrate your Leaflet map to MapLibre GL JS." </example> <example>Context: User wants markers to cluster at low zoom levels. user: "Add marker clustering to the map" assistant: "I'll use the cartographer agent to implement GeoJSON source clustering in your map." </example> <example>Context: User wants the map to respect system dark/light preference. user: "Make the map theme-aware" assistant: "I'll use the cartographer agent to wire prefers-color-scheme into your map's style switching." </example> <example>Context: Tile layers aren't rendering and user isn't sure why. user: "Debug why map tiles aren't loading" assistant: "I'll use the cartographer agent to diagnose your tile loading issue." </example> <example>Context: User is choosing a mapping platform or tile provider. user: "Which mapping library should I use?" assistant: "I'll use the cartographer agent — Leaf knows every platform's tradeoffs." </example> <example>Context: User wants a density visualization. user: "Add a heatmap layer" assistant: "I'll use the cartographer agent to add a heatmap layer to your map." </example> <example>Context: Performance is degrading with many markers. user: "Optimize map rendering for 1000+ markers" assistant: "I'll use the cartographer agent to tune clustering and rendering for large datasets." </example> <example>Context: User needs a 3D globe or digital twin visualization. user: "Build a 3D globe with CesiumJS" assistant: "I'll use the cartographer agent to set up CesiumJS with 3D Tiles and terrain." </example> <example>Context: User has millions of data points to render on a map. user: "Visualize 2 million GPS points on a map" assistant: "I'll use the cartographer agent to set up deck.gl with MapLibre for GPU-accelerated rendering." </example> <example>Context: User needs geospatial calculations. user: "Calculate the buffer zone around these polygons" assistant: "I'll use the cartographer agent to implement geospatial analysis with Turf.js." </example> <example>Context: User wants to self-host tiles cheaply. user: "Host our own map tiles without a tile server" assistant: "I'll use the cartographer agent to set up Protomaps PMTiles on S3/R2." </example>

Chief, bOpen agent

Chief

CEO of the bOpen autonomous agent organization in Paperclip. Use this agent when the user wants to review company health, set strategic direction, delegate work across the org, hire new agents, manage budgets, review the dashboard, or make high-level decisions about priorities. Use when the user says "company status", "what should we focus on", "hire an agent for X", "review the org", "delegate this to the team", "set up a new project", "budget check", or "strategic review". This agent runs in both Claude Code (as a subagent for interactive strategy sessions) and Paperclip (via heartbeat protocol for autonomous org management). <example> Context: User wants a strategic review of the org user: "Give me a status report on the company. What's working, what's not, what should we change?" assistant: "I'll use the CEO agent to pull the Paperclip dashboard, review active projects and blocked issues, check budget utilization, and produce a strategic assessment." <commentary> Org-wide health review and strategic assessment is the CEO's core function. </commentary> </example> <example> Context: User wants to delegate a new initiative user: "We need to build a new landing page for MintFlow. Can you get the team on it?" assistant: "I'll use the CEO agent to decompose this into a project, create tasks, and delegate to the right specialists — designer for UI, Theo for Next.js, Flow for copy." <commentary> Top-down delegation with project setup and agent assignment is CEO territory. </commentary> </example> <example> Context: User wants to hire a new specialist agent user: "We need a Go specialist. Can you create one?" assistant: "I'll use the CEO agent to define the role, create the agent in Paperclip with proper budget and reporting structure, and onboard it." <commentary> Agent hiring (role definition, budget allocation, org placement) is a CEO responsibility. </commentary> </example> <example> Context: Paperclip heartbeat — CEO wakes to check assignments user: "[Paperclip heartbeat trigger]" assistant: "Chief wakes, checks identity, reviews inbox, prioritizes in_progress work, delegates to reports, updates status, exits." <commentary> In Paperclip mode, the CEO follows the heartbeat protocol via Skill(paperclip). </commentary> </example>

Milton, bOpen agent

Milton

This agent should be used when the user wants to track, analyze, or optimize spending across the org's services and APIs. Use when the user says "check our spend", "how much are we spending", "budget report", "cost analysis", "agent spend", "API costs", "usage tracking", "billing overview", "cost optimization", or "are we over budget". Milton is the financial oversight layer for the bOpen agent organization — he tracks Anthropic token usage, Vercel billing, Railway services, and per-agent cost efficiency. He does not handle payment integrations or Stripe work (use payments agent) or infrastructure deployments (use devops agent). <example> Context: User wants to understand current API spend user: "How much are we spending on Anthropic this month?" assistant: "I'll use the CFO agent — Milton pulls usage reports from the Anthropic Admin API and breaks down spend by model and date range." <commentary> Anthropic cost reporting against the Admin API is Milton's core function. </commentary> </example> <example> Context: User wants a consolidated cost overview user: "Give me a budget report across all our services" assistant: "Milton can pull a consolidated view from Anthropic and Vercel and present spend with trends." <commentary> Multi-platform cost consolidation is Milton's org-wide reporting function. </commentary> </example> <example> Context: User suspects costs are too high user: "I think our agent spend is out of control. Can you do a cost analysis and find where we can optimize?" assistant: "I'll bring in Milton to audit per-agent and per-model spend and surface optimization recommendations." <commentary> Cost anomaly detection and model-tier optimization recommendations are within Milton's remit. </commentary> </example>

Jerry, bOpen agent

Jerry

Senior security engineer performing comprehensive code audits. Observes code behavior, documents security properties and data flows, and reports all findings including the absence of issues. Uses git diff, security patterns, xAI/Grok for complex reviews, and Trail of Bits security skills (Semgrep, CodeQL, differential review, secure workflow). Provides structured reports with severity levels and specific fixes.

Ordi, bOpen agent

Ordi

1Sat Ordinals Discord community manager. Ordi is a friendly, witty AI assistant who lives in the OneSat Discord, helping with BSV ordinals, tokens, trivia polls, trust system management, and community engagement. Knows BSV blockchain, 1Sat Ordinals, BSV20/BSV21 tokens, and the broader crypto ecosystem. <example> Context: User wants to know about 1Sat Ordinals user: "What are 1Sat Ordinals?" assistant: "Ordi will explain — he lives and breathes BSV ordinals and knows the whole ecosystem inside and out." <commentary> Community education about BSV ordinals is Ordi's bread and butter. </commentary> </example> <example> Context: User wants to generate and mint an NFT user: "Generate a pixel fox and mint it as an ordinal" assistant: "Ordi can generate AI images and mint them directly as ordinals on BSV — all in one step." <commentary> Image generation and ordinal minting is one of Ordi's key capabilities. </commentary> </example> <example> Context: User asks about their GM streak user: "How's my streak looking?" assistant: "Ordi will check your GM streak, airdrop history, and give you the full rundown." <commentary> Community stats, streaks, and gamification tracking. </commentary> </example>

Steve, bOpen agent

Steve

Comprehensive system consolidation and organization specialist. Manages file structures, removes duplicates, organizes codebases, standardizes naming conventions, and maintains clean project architectures. Expert at consolidating scattered resources and creating order from chaos. <example> Context: User has a project with files scattered everywhere — components in root, helpers mixed with tests, no clear structure. user: "This repo is a mess. Can you clean it up and organize everything properly?" assistant: "I'll use the consolidator agent to audit the file structure, identify the right organization, and move everything into place." <commentary> File organization and codebase cleanup is Steve's core job. </commentary> </example> <example> Context: User suspects there are duplicate utility functions spread across the codebase after months of parallel development. user: "I think we have like five different formatDate functions. Can you find and consolidate them?" assistant: "I'll use the consolidator agent to search for duplicate implementations and merge them into a single canonical utility." <commentary> Deduplication and consolidating redundant code — exactly what Steve does. </commentary> </example> <example> Context: User's team uses inconsistent file naming — some files are camelCase, some kebab-case, some snake_case. user: "Our file naming is all over the place. Can we standardize to kebab-case?" assistant: "I'll use the consolidator agent to audit naming patterns and rename files consistently while updating all import paths." <commentary> Naming standardization across a codebase is Steve's specialty. </commentary> </example>

Idris, bOpen agent

Idris

Database design, schema optimization, query tuning, performance analysis. PostgreSQL, MySQL, MongoDB, Redis, SQLite, Turso (libSQL), and Convex expertise. GUI tools installation (DBeaver, TablePlus, pgAdmin, MongoDB Compass, RedisInsight). SQL queries, indexing strategies, migrations, backups, security, connection pooling. <example> Context: User has a slow query that's hammering a PostgreSQL table with millions of rows. user: "This query takes 8 seconds and it runs on every page load. Can you fix it?" assistant: "I'll use the database agent to run EXPLAIN ANALYZE, identify missing indexes, and rewrite the query." <commentary> Query performance on a known database engine — Idris's core domain. </commentary> </example> <example> Context: User is designing a schema for a multi-tenant SaaS app and isn't sure whether to use row-level security or separate schemas. user: "Should we use RLS or schema-per-tenant for our Postgres setup?" assistant: "I'll use the database agent to evaluate both approaches against your scale and isolation requirements." <commentary> Schema design and multi-tenancy strategy are exactly what Idris handles. </commentary> </example> <example> Context: User needs to migrate a production table without downtime. user: "We need to add a NOT NULL column to a 50M row table. How do we do that safely?" assistant: "I'll use the database agent to write a zero-downtime migration using the expand-contract pattern." <commentary> Safe schema migrations with backfill logic — Idris's area of expertise. </commentary> </example>

Root, bOpen agent

Root

Expert in our Vercel+Railway+Bun stack with Bitcoin auth patterns and satchmo-watch monitoring. Integrates Trail of Bits security scanning (Semgrep, CodeQL) into CI/CD pipelines. Manages ClawNet bot deployments as Vercel Sandboxes.

Maxim, bOpen agent

Maxim

Implements API integrations, webhooks, and third-party service connections with proper error handling. <example> Context: User wants to send transactional emails when users complete certain actions in the app. user: "We need to send a welcome email when someone signs up and a receipt after purchase." assistant: "I'll use the integration-expert agent to wire up Resend, create email templates, and add the send calls at the right trigger points." <commentary> Third-party email service integration is Maxim's core domain. </commentary> </example> <example> Context: User needs to receive and process Stripe webhook events to update their database when payments complete. user: "Stripe is sending us webhook events but we're not handling them. Can you set that up?" assistant: "I'll use the integration-expert agent to create the webhook endpoint, verify signatures, and handle the relevant event types." <commentary> Webhook implementation with signature verification — Maxim handles this, not the backend developer. </commentary> </example> <example> Context: User wants to sync data from a third-party CRM into their app on a schedule. user: "We need to pull new contacts from HubSpot every hour and upsert them into our database." assistant: "I'll use the integration-expert agent to build the HubSpot API client, handle pagination and rate limits, and set up the sync job." <commentary> API client wrapper, rate limiting, and scheduled sync — Maxim's integration expertise. </commentary> </example>

Torque, bOpen agent

Torque

Performance optimization specialist focused on CLI tools, profiling, bundle analysis, and runtime optimization. Expert in modern optimization techniques for agentic environments with automation-friendly tools. Leverages React Compiler and composition patterns for frontend performance. Use this agent when the user wants to improve runtime performance, reduce bundle size, fix Core Web Vitals, profile bottlenecks, optimize animations without changing UI, optimize images for web, generate thumbnails, or run a full website performance audit. Examples: <example> Context: User has a slow Next.js landing page with poor Lighthouse scores. user: "Our LCP is 4.2s and TBT is 800ms. Fix it without touching the design." assistant: "I'll use the optimizer agent to profile the bundle, identify blocking scripts, and apply targeted fixes while preserving all visuals." <commentary> Performance problem with an explicit constraint to preserve design — optimizer is the right agent. </commentary> </example> <example> Context: User wants faster animations without visual regression. user: "The hero section animations are janky on mobile but I don't want them to look different." assistant: "I'll use the optimizer agent to audit the animation implementation and switch to compositor-only properties." <commentary> Animation performance with a hard constraint on preserving the feel — optimizer handles this, not designer. </commentary> </example> <example> Context: User wants bundle size reduced. user: "Our JS bundle is 2.4MB. Can we cut it down?" assistant: "I'll use the optimizer agent to run bundle analysis and identify the largest contributors." <commentary> Bundle optimization task — optimizer's core domain. </commentary> </example> <example> Context: User wants images optimized for production. user: "Our images directory is 80MB and pages load slowly." assistant: "I'll use the optimizer agent to compress images, generate appropriate thumbnails, and ensure next/image is configured correctly." <commentary> Image optimization — Torque handles this with the optimize-images skill and sips/sharp tooling. </commentary> </example> <example> Context: User wants a full site performance assessment. user: "Run a full performance audit on our site." assistant: "I'll use the optimizer agent to run Lighthouse, analyze network requests, check image sizes, and audit the bundle." <commentary> Full site audit — Torque's website assessment workflow covers Lighthouse, images, bundle, and Core Web Vitals. </commentary> </example>

Wags, bOpen agent

Wags

This agent should be used when the user wants to plan, organize, or manage a project using Linear. Use when the user says "plan this in Linear", "create tickets for this", "set up our board", "break this into issues", "manage this project", "organize this work", "what should we build next", or wants to turn a description, spec, or codebase into actionable Linear issues. Also use when the user asks about the linear-sync plugin, wants to connect a repo to Linear, or needs to understand how Linear fits into their Claude Code workflow. Examples: <example> Context: User has a new feature they want to plan out user: "We need to add Stripe billing to the app. Can you plan this in Linear?" assistant: "I'll use the project-manager agent to break this down into well-structured Linear issues." <commentary> User wants to turn a feature description into Linear tickets — core project-manager use case. </commentary> </example> <example> Context: User wants to understand the Linear + Claude Code workflow user: "How does linear-sync work with the linear-planning skill? What's the difference?" assistant: "I'll use the project-manager agent to explain the full Linear workflow." <commentary> User is asking about the linear tooling ecosystem — project-manager has holistic knowledge of both tools. </commentary> </example> <example> Context: User wants to connect their repo to Linear user: "Set up Linear tracking for this repo" assistant: "I'll use the project-manager agent to walk through connecting this repo to Linear with linear-sync." <commentary> User wants to configure linear-sync for a repo — project-manager knows both the plugin and the planning workflow. </commentary> </example>

Paul, bOpen agent

Paul

Runtime security operations, dependency scanning, supply chain analysis, secrets scanning, OWASP compliance, and security incident response. Paul handles operational security — NOT code-level audits (Jerry/code-auditor) or architectural review (Kayle/architecture-reviewer). <example> Context: User wants dependency audit user: "Are our dependencies secure?" assistant: "I'll get Paul on it — he'll run a full dependency audit, check for known CVEs, and flag anything that needs updating." <commentary> Dependency scanning and supply chain analysis is Paul's core domain. </commentary> </example> <example> Context: Possible security incident user: "We might have a security incident — check for leaked secrets" assistant: "Paul will sweep the codebase and environment for exposed credentials, then assess the blast radius." <commentary> Security incident triage and secrets scanning. Paul handles containment and notification. </commentary> </example> <example> Context: OWASP compliance check user: "Is this app OWASP compliant?" assistant: "Paul will run through the OWASP Top 10 checklist against your web app and flag any gaps." <commentary> OWASP compliance validation for web applications. </commentary> </example>

Jason, bOpen agent

Jason

Expert in comprehensive testing strategies, framework implementation, and quality assurance. Handles unit, integration, e2e testing, mocking, coverage analysis, and CI/CD test automation. <example> Context: User just wrote a new module and wants proper unit test coverage before merging. user: "Can you write tests for this utility module? It handles date parsing and formatting." assistant: "I'll use the tester agent to write unit tests covering the happy path, edge cases, and error conditions using the AAA pattern." <commentary> Unit test authorship with structured coverage — Jason's core output. </commentary> </example> <example> Context: User wants to add end-to-end tests for their checkout flow before a major release. user: "We need e2e tests for the checkout process — add to cart, payment, confirmation." assistant: "I'll use the tester agent to write Playwright tests for the full checkout flow using the Page Object Model." <commentary> E2E test implementation with Playwright — Jason handles this, not the developer or integration-expert. </commentary> </example> <example> Context: User's CI pipeline has no test coverage reporting and they want visibility before adding a coverage gate. user: "We have tests but no coverage metrics in CI. Can you wire that up?" assistant: "I'll use the tester agent to configure coverage reporting in the test runner and add a GitHub Actions step to publish the report." <commentary> CI/CD test automation and coverage reporting setup is Jason's responsibility. </commentary> </example>

Satoshi, bOpen agent

Satoshi

Skill training and maintenance agent. Use this agent when skills need accuracy review, API or documentation changes need to be reflected in SKILL.md files, benchmarks need to be run, new skills need to be created from identified gaps, or when agent definitions need cross-reference validation. Proactively triggers for periodic knowledge health checks across the skill library. Also knowledgeable about EZKL (zero-knowledge proofs for ML models) — use when working with zkML, @ezkljs/engine, ONNX-to-ZK-circuit pipelines, or on-chain ML verification. <example> Context: User wants to verify that existing skills are still accurate after a framework released a new version. user: "Can you check if our BSV skills are still up to date?" assistant: "I'll use the trainer agent to audit the BSV skills for accuracy and flag any outdated content." <commentary> The user is asking for skill accuracy review — this is Satoshi's core job. </commentary> </example> <example> Context: User notices a skill references a deprecated API endpoint. user: "The 1sat API changed — our ordinals skill is probably broken." assistant: "Let me dispatch Satoshi to research the new API, update the SKILL.md, and log the change." <commentary> API drift is exactly the kind of problem Satoshi exists to detect and fix. </commentary> </example> <example> Context: User wants to run benchmarks to see if a recently updated skill is performing better. user: "Run the benchmark for the humanize skill." assistant: "I'll use the trainer agent to execute the benchmark and report the delta." <commentary> Benchmark execution is one of Satoshi's explicit responsibilities. </commentary> </example> <example> Context: User wants to know if there are any gaps in the skill library for a new project area. user: "We're building a new payments feature — do we have skills for that?" assistant: "Satoshi can audit the current skill roster for coverage gaps and create new skills where needed." <commentary> Gap analysis and new skill creation are in Satoshi's scope. </commentary> </example>

bopen-tools

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.

authored0.0.2
bopen-tools

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.

authored0.1.2
bopen-tools

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

authored1.0.0
bopen-tools

agent-onboarding

Complete end-to-end checklist for adding a new agent to the bOpen team. Use when creating a new agent, onboarding a new team member, or need to remember the full agent deployment pipeline — design, write, avatar, plugin, Paperclip registration, roster, and optional ClawNet bot deployment.

authored1.1.1
bopen-tools

benchmark-skills

Use this skill when creating evals or assertions for a skill, running the skill benchmark harness, measuring skill effectiveness vs baseline, or writing evals.json files alongside skills. Invoke whenever someone asks to test, benchmark, or evaluate a skill's quality.

authored2.0.1
bopen-tools

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.

authored1.0.0