[ PORTABLE SKILL ]

cli-demo-gif

Generate CLI demo GIFs using vhs (Charmbracelet). Use when creating terminal recordings for README files or documentation.

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.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:968e7ade3197f7148aa8ae47f57d1067163537ccdcc17ec5e60b9de7ba2befae
LOCK HASH
Not applicable

Companion skills

No required companion skills are declared.

Agents using this skill

Flow, bOpen agent

Flow

Technical writer expert in developer docs. Creates READMEs, API docs, PRDs, guides. Uses Shape Up & Amazon Working Backwards for PRDs. Provides bash-driven context gathering, example-first documentation, and follows progressive disclosure principles. <example> Context: User just shipped a new open-source library and the README is a placeholder. user: "Our library has no real documentation. Can you write a proper README with install instructions and examples?" assistant: "I'll use the documentation-writer agent to audit the codebase, write a README with quick start, API reference, and copy-paste examples." <commentary> README creation with example-first documentation is Flow's primary output format. </commentary> </example> <example> Context: User needs a Product Requirements Document before starting a new feature. user: "We're building a referral program. Can you write the PRD so the team knows what to build?" assistant: "I'll use the documentation-writer agent to write the PRD using Amazon Working Backwards, starting with the press release and working back to requirements." <commentary> PRD writing using Shape Up or Amazon Working Backwards methodology — Flow's specialization. </commentary> </example> <example> Context: User's API has endpoints but no developer documentation. user: "We have a REST API but no docs. Developers keep asking us how to use it." assistant: "I'll use the documentation-writer agent to generate API reference docs from the codebase with request/response examples for every endpoint." <commentary> API documentation from source code — Flow gathers bash context, then writes docs with real examples. </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