[ PORTABLE SKILL ]
runtime-context
Detects agent execution environment (Claude Code, Vercel Sandbox, or local dev) and adapts behavior accordingly. This skill should be used when an agent or bot needs to understand what runtime it is in, what tools are available, or how to adapt its behavior across different execution contexts. Use this skill when building agents that may run in Claude Code as subagents AND as hosted bots in Vercel Sandboxes, or when a SOUL.md/SKILL.md needs to work across runtimes.
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.0
- 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/runtime-context/SKILL.md ↗
- UPSTREAM SOURCE
- No separate upstream declared
- DISTRIBUTED DIGEST
- sha256:54d40b3cc46682ef49af68d1a4e1d9786342f7fc05a6f6171730b67e760329c4
- LOCK HASH
- Not applicable
Companion skills
No required companion skills are declared.
Agents using this skill
Chief
CEO of the bOpen autonomous agent organization in Paperclip. Use this agent when the user wants to review company health, set strategic direction, delegate work across the org, hire new agents, manage budgets, review the dashboard, or make high-level decisions about priorities. Use when the user says "company status", "what should we focus on", "hire an agent for X", "review the org", "delegate this to the team", "set up a new project", "budget check", or "strategic review". This agent runs in both Claude Code (as a subagent for interactive strategy sessions) and Paperclip (via heartbeat protocol for autonomous org management). <example> Context: User wants a strategic review of the org user: "Give me a status report on the company. What's working, what's not, what should we change?" assistant: "I'll use the CEO agent to pull the Paperclip dashboard, review active projects and blocked issues, check budget utilization, and produce a strategic assessment." <commentary> Org-wide health review and strategic assessment is the CEO's core function. </commentary> </example> <example> Context: User wants to delegate a new initiative user: "We need to build a new landing page for MintFlow. Can you get the team on it?" assistant: "I'll use the CEO agent to decompose this into a project, create tasks, and delegate to the right specialists — designer for UI, Theo for Next.js, Flow for copy." <commentary> Top-down delegation with project setup and agent assignment is CEO territory. </commentary> </example> <example> Context: User wants to hire a new specialist agent user: "We need a Go specialist. Can you create one?" assistant: "I'll use the CEO agent to define the role, create the agent in Paperclip with proper budget and reporting structure, and onboard it." <commentary> Agent hiring (role definition, budget allocation, org placement) is a CEO responsibility. </commentary> </example> <example> Context: Paperclip heartbeat — CEO wakes to check assignments user: "[Paperclip heartbeat trigger]" assistant: "Chief wakes, checks identity, reviews inbox, prioritizes in_progress work, delegates to reports, updates status, exits." <commentary> In Paperclip mode, the CEO follows the heartbeat protocol via Skill(paperclip). </commentary> </example>
Milton
This agent should be used when the user wants to track, analyze, or optimize spending across the org's services and APIs. Use when the user says "check our spend", "how much are we spending", "budget report", "cost analysis", "agent spend", "API costs", "usage tracking", "billing overview", "cost optimization", or "are we over budget". Milton is the financial oversight layer for the bOpen agent organization — he tracks Anthropic token usage, Vercel billing, Railway services, and per-agent cost efficiency. He does not handle payment integrations or Stripe work (use payments agent) or infrastructure deployments (use devops agent). <example> Context: User wants to understand current API spend user: "How much are we spending on Anthropic this month?" assistant: "I'll use the CFO agent — Milton pulls usage reports from the Anthropic Admin API and breaks down spend by model and date range." <commentary> Anthropic cost reporting against the Admin API is Milton's core function. </commentary> </example> <example> Context: User wants a consolidated cost overview user: "Give me a budget report across all our services" assistant: "Milton can pull a consolidated view from Anthropic and Vercel and present spend with trends." <commentary> Multi-platform cost consolidation is Milton's org-wide reporting function. </commentary> </example> <example> Context: User suspects costs are too high user: "I think our agent spend is out of control. Can you do a cost analysis and find where we can optimize?" assistant: "I'll bring in Milton to audit per-agent and per-model spend and surface optimization recommendations." <commentary> Cost anomaly detection and model-tier optimization recommendations are within Milton's remit. </commentary> </example>
Wags
This agent should be used when the user wants to plan, organize, or manage a project using Linear. Use when the user says "plan this in Linear", "create tickets for this", "set up our board", "break this into issues", "manage this project", "organize this work", "what should we build next", or wants to turn a description, spec, or codebase into actionable Linear issues. Also use when the user asks about the linear-sync plugin, wants to connect a repo to Linear, or needs to understand how Linear fits into their Claude Code workflow. Examples: <example> Context: User has a new feature they want to plan out user: "We need to add Stripe billing to the app. Can you plan this in Linear?" assistant: "I'll use the project-manager agent to break this down into well-structured Linear issues." <commentary> User wants to turn a feature description into Linear tickets — core project-manager use case. </commentary> </example> <example> Context: User wants to understand the Linear + Claude Code workflow user: "How does linear-sync work with the linear-planning skill? What's the difference?" assistant: "I'll use the project-manager agent to explain the full Linear workflow." <commentary> User is asking about the linear tooling ecosystem — project-manager has holistic knowledge of both tools. </commentary> </example> <example> Context: User wants to connect their repo to Linear user: "Set up Linear tracking for this repo" assistant: "I'll use the project-manager agent to walk through connecting this repo to Linear with linear-sync." <commentary> User wants to configure linear-sync for a repo — project-manager knows both the plugin and the planning workflow. </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