[ PORTABLE SKILL ]

free-roam-testing

Use this skill to run a discovery loop that explores a running app the way a curious or chaotic human would — randomized, unscripted paths, weird inputs, edge interactions — to surface NEW bugs, broken flows, confusing UX, and slow spots, then file them as deduplicated tickets. Invoke it when the user says "free roam", "explore the app", "monkey test", "find issues I don't know about", "exploratory testing", "use it like a real user", "discovery loop", "surface new bugs", or wants an agent to poke around an app autonomously and report what's broken. This is the producer half of the loop architecture — it feeds tickets to the execution loop. NOT for scripted regression tests (that's the tester agent's verification gate). Always respects a never-touch list and a blast-radius boundary before mutating anything.

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
0.0.1
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:cb98cae1eab8d7d29126824022b0335252bf139353e95f2b3648d843d4e9bd20
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.

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>

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