[ PORTABLE SKILL ]
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
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.1.2
- 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.
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.
- DISTRIBUTED SOURCE
- skills/hunter-skeptic-referee/SKILL.md ↗
- UPSTREAM SOURCE
- No separate upstream declared
- DISTRIBUTED DIGEST
- sha256:2efe3b1d99b3fbf23bf292211dfe438bf08915c117252f5ba80770f34e314bab
- LOCK HASH
- Not applicable
Companion skills
No required companion skills are declared.
Agents using this skill
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.
Kayle
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>
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.
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.
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
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>
Related skills
ALL BOPEN-TOOLS SKILLS →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