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

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>

../account-manager.md

../agent-builder.md

Use this agent for comprehensive architectural analysis, large-scale refactoring planning, and complex system design reviews requiring maximum reasoning capability. Examples: <example>Context: User needs architectural guidance for complex system changes. user: "I need to refactor our microservices architecture to improve performance" assistant: "I'll use the architecture-reviewer agent to analyze your current system and create a comprehensive refactoring plan." <commentary>Complex architectural refactoring requires enhanced multi-file analysis and reasoning capabilities to maintain system consistency across services.</commentary></example> <example>Context: Large codebase requires systematic analysis. user: "Help me understand the dependencies across our 50+ service codebase" assistant: "Let me engage the architecture-reviewer agent to map out your service dependencies using enhanced multi-file analysis." <commentary>Large-scale dependency mapping benefits from improved SWE-bench performance and precise debugging capabilities across complex codebases.</commentary></example>

../architecture-reviewer.md

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.

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

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.

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.

7 hooks across 3 events