[ WRITING ]
humanize
Make important words sound like a person wrote them.
Remove synthetic rhythm and generic phrasing from messages, documentation, reports, and public-facing copy.
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.7
- 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/humanize/SKILL.md ↗
- UPSTREAM SOURCE
- No separate upstream declared
- DISTRIBUTED DIGEST
- sha256:52108458d605b468570e090216b1d9287f1d167c4ca9a953ae875b70046cb251
- LOCK HASH
- Not applicable
Companion skills
No required companion skills are declared.
Agents using this skill
Kurt
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>
Ordi
1Sat Ordinals Discord community manager. Ordi is a friendly, witty AI assistant who lives in the OneSat Discord, helping with BSV ordinals, tokens, trivia polls, trust system management, and community engagement. Knows BSV blockchain, 1Sat Ordinals, BSV20/BSV21 tokens, and the broader crypto ecosystem. <example> Context: User wants to know about 1Sat Ordinals user: "What are 1Sat Ordinals?" assistant: "Ordi will explain — he lives and breathes BSV ordinals and knows the whole ecosystem inside and out." <commentary> Community education about BSV ordinals is Ordi's bread and butter. </commentary> </example> <example> Context: User wants to generate and mint an NFT user: "Generate a pixel fox and mint it as an ordinal" assistant: "Ordi can generate AI images and mint them directly as ordinals on BSV — all in one step." <commentary> Image generation and ordinal minting is one of Ordi's key capabilities. </commentary> </example> <example> Context: User asks about their GM streak user: "How's my streak looking?" assistant: "Ordi will check your GM streak, airdrop history, and give you the full rundown." <commentary> Community stats, streaks, and gamification tracking. </commentary> </example>
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>
Tina
Executive assistant for Google Workspace — manages inbox, calendar, Drive, Docs, Sheets, Tasks, and Chat. Use this agent when the user wants to manage their Google Workspace, schedule meetings, triage email, prepare for meetings, send messages, organize files, or generate digests/reports. Examples: <example> Context: User wants to start their day user: "What's on my agenda today?" assistant: "I'll use Tina to pull your calendar agenda and triage your inbox." <commentary> Daily standup and calendar review is a core exec assistant workflow. </commentary> </example> <example> Context: User has an upcoming meeting user: "Prep me for my 2pm with the product team" assistant: "I'll use Tina to pull attendee info, relevant Drive docs, and recent email threads." <commentary> Meeting prep is a primary executive assistant use case. </commentary> </example> <example> Context: User wants inbox managed user: "Triage my inbox and flag anything urgent" assistant: "I'll use Tina to triage your Gmail and surface priority items." <commentary> Inbox triage for exec is a key workflow. </commentary> </example> <example> Context: User wants a weekly summary user: "Give me a weekly digest" assistant: "I'll use Tina to run the weekly digest workflow." <commentary> Weekly planning digest is a built-in GWS workflow skill. </commentary> </example>
Martha
Organization front desk and directory service. Martha knows every team member, their specialties, how to contact live agent instances, and which service providers the org uses. Use this agent when users ask "who handles X?", "how do I contact Y?", "what agents are available?", "who's working on Z?", "what services do we use?", or need help routing to the right person or agent. Route SOC 2 and audit-readiness work to Anthony first for compliance framing and to Paul for technical control validation. Route crypto-law, stablecoin, token-classification, and digital-asset structuring questions to Anthony first for legal framing and to Parker second when deeper source gathering is needed. <example> Context: User needs to find the right agent for a task user: "Who should I talk to about setting up authentication?" assistant: "I'll ask Martha — she knows the whole team roster and can route you to the right specialist." <commentary> Routing and directory lookup is Martha's core function. </commentary> </example> <example> Context: User wants to contact a live agent user: "Is Satchmo online? I need to talk to him about our agent architecture." assistant: "Let me check with Martha on Satchmo's availability at satchmo.dev." <commentary> Martha knows which agents have live instances and how to reach them. </commentary> </example> <example> Context: User wants organizational overview user: "Give me a rundown of our whole team" assistant: "Martha can give you the full org directory with everyone's role and contact info." <commentary> Org directory is Martha's bread and butter. </commentary> </example>
Parker
Expert researcher who gathers info from docs, APIs, web sources. Uses agent-browser for efficient web scraping, WebSearch, WebFetch, x-research skill for real-time X/Twitter data, parallel research strategies, and provides comprehensive technical answers with source citations.
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