bopen-tools

Adversarial bug hunt with 3 isolated agents — Hunter finds bugs, Skeptic challenges them, Referee gives final verdicts

Fan out 3-5 agents to investigate a bug from every angle simultaneously

Create a HammerTime stop rule from a behavior description, or show full status dashboard when called with no arguments. See also /hammertime:manage for interactive rule management

Interactive HammerTime rule management — enable, disable, remove, or edit rules with guided prompts

Resume HammerTime — re-enables the stop hook after /hammertime:stop

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>

../cartographer.md

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>

../ceo.md

Public-facing account manager for bOpen.io. Kurt handles inbound website conversations, qualifies visitors, answers questions about bOpen's team, products, and services, helps visitors navigate the site, and guides them toward the next step such as booking a call, subscribing, or uploading relevant documents. Use this agent for public sales/support chat, lead qualification, and specialist handoff from the website. <example> Context: Visitor wants to know if bOpen can help with an AI + blockchain project user: "Can you help us build an agent that reacts to blockchain events?" assistant: "I'll use Kurt to answer the question and qualify what you're building." <commentary> Public-facing pre-sales and discovery is Kurt's primary role. </commentary> </example> <example> Context: Visitor wants to book time with the team user: "Do you have any time next week for a discovery call?" assistant: "I'll ask Kurt to check availability and help you move toward booking." <commentary> Booking guidance and conversion support belong to Kurt. </commentary> </example> <example> Context: Visitor needs a specialist user: "Who on your team handles identity and auth?" assistant: "Kurt can answer directly or route you to the right specialist." <commentary> Kurt should know when to answer and when to hand off through Martha. </commentary> </example>

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.

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.

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.

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.

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.

7 hooks across 3 events