Company Ceo
Prism-Shadow/penguin-harness
Run a PenguinHarness organization as its CEO — turn the mission into a ticket tree, hire HR and finance first, partition the shared workspace, schedule the calendar, open a channel per stream…
A skill your agent uses when reviewing or updating the company Vision/Traction Organizer
MITAuto-check passed
Install Ceos Vto
$ npx skills add bradfeld/ceos --skill ceos-vto -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install bradfeld/ceos ceos-vto --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/bradfeld/ceos.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/ceos-vto .claude/skills/ceos-vto && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "ceos-vto" agent skill from https://github.com/bradfeld/ceos/tree/main/skills/ceos-vto into .claude/skills/ceos-vto/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ceos-vto", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/bradfeld/ceos/tree/main/skills/ceos-vtoType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add bradfeld/ceos --skill ceos-vto -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install bradfeld/ceos ceos-vto --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bradfeld/ceos.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/ceos-vto .agents/skills/ceos-vto && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ceos-vto" agent skill from https://github.com/bradfeld/ceos/tree/main/skills/ceos-vto into .agents/skills/ceos-vto/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ceos-vto", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add bradfeld/ceos --skill ceos-vto -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install bradfeld/ceos ceos-vto --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bradfeld/ceos.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/ceos-vto .cursor/skills/ceos-vto && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ceos-vto" agent skill from https://github.com/bradfeld/ceos/tree/main/skills/ceos-vto into .cursor/skills/ceos-vto/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ceos-vto", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/bradfeld/ceos.git --path skills/ceos-vto--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add bradfeld/ceos --skill ceos-vto -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install bradfeld/ceos ceos-vto --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bradfeld/ceos.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/ceos-vto .gemini/skills/ceos-vto && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "ceos-vto" agent skill from https://github.com/bradfeld/ceos/tree/main/skills/ceos-vto into .gemini/skills/ceos-vto/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ceos-vto", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install bradfeld/ceos ceos-vtoInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add bradfeld/ceos --skill ceos-vto -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/bradfeld/ceos.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/ceos-vto .github/skills/ceos-vto && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "ceos-vto" agent skill from https://github.com/bradfeld/ceos/tree/main/skills/ceos-vto into .github/skills/ceos-vto/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ceos-vto", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add bradfeld/ceos --skill ceos-vto -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install bradfeld/ceos ceos-vto --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bradfeld/ceos.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/ceos-vto .opencode/skills/ceos-vto && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ceos-vto" agent skill from https://github.com/bradfeld/ceos/tree/main/skills/ceos-vto into .opencode/skills/ceos-vto/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ceos-vto", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
ceos-vto- GitHub stars
- 156
- Token cost
- ~1.9k tokens
- SKILL.md length
- 983 words
- Files
- 1
- Skills in repo
- 23
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when reviewing or updating the company Vision/Traction Organizer
- Works in 5 steps: Read the Current V/TO → Identify the Request → For Updates → …
- Updating the company Vision/Traction Organizer
- SKILL.md covers When to Use, Context, Process and Output Format, plus 2 more sections
- Calls git
What it does
Ceos Vto is an agent skill from bradfeld/ceos. Use when reviewing or updating the company Vision/Traction Organizer
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: EOS (Entrepreneurial Operating System) skills for Claude Code. Run your business on EOS with AI. The licence is MIT.
When your agent uses it
- Updating the company Vision/Traction Organizer
Example prompts
- “/ceos-vto”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit bdd5f01. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Ceos Vto loads about 1.9k tokens when it runs. Until then it costs about 19 tokens; SKILL.md has 983 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from bradfeld/ceos at commit bdd5f01, republished under its MIT licence (© bradfeld). 983 words, ~1,854 tokens.
Download SKILL.mdSave it as
.claude/skills/ceos-vto/SKILL.md (or your agent's skills folder).- name
- ceos-vto
- description
- Use when reviewing or updating the company Vision/Traction Organizer
- file-access
- data/vision.md, templates/vision.md, data/accountability.md, data/rocks/
- tools-used
- Read, Write, Edit
ceos-vto
Review and update the Vision/Traction Organizer (V/TO) — the single document that captures where your company is going and how it plans to get there.
When to Use
- "Review our vision" or "show me the V/TO"
- "Update our core values" or "change our 10-year target"
- "What's our core focus?" or "what are our 3 uniques?"
- "Are our Rocks aligned with the 1-Year Plan?"
- "Let's update the 3-year picture"
- Any time the leadership team needs to revisit strategic direction
Context
Finding the CEOS Repository
Search upward from the current directory for the .ceos marker file. This file marks the root of the CEOS repository.
current_dir → parent → parent → ... until .ceos foundIf .ceos is not found, stop and tell the user: "Not in a CEOS repository. Clone your CEOS repo and run setup.sh first."
Sync before use: Once you find the CEOS root, run git -C <ceos_root> pull --ff-only --quiet 2>/dev/null to get the latest data from teammates. If it fails (conflict or offline), continue silently with local data.
Key Files
| File | Purpose |
|---|---|
data/vision.md | The V/TO document (source of truth) |
data/accountability.md | Who owns what (reference for role alignment) |
data/rocks/ | Current quarter's Rocks (for alignment checks) |
templates/vision.md | Template structure (reference only) |
V/TO Sections
The V/TO has 8 sections, each covering a different planning horizon:
| Section | Horizon | Key Question |
|---|---|---|
| Core Values | Permanent | What do we stand for? |
| Core Focus | Permanent | Why do we exist? What's our niche? |
| 10-Year Target | 10 years | What's our big audacious goal? |
| Marketing Strategy | Ongoing | Who do we serve? How are we different? |
| 3-Year Picture | 3 years | What does the company look like? |
| 1-Year Plan | 1 year | What must be true in 12 months? |
| Quarterly Rocks | 90 days | See data/rocks/ (managed by ceos-rocks) |
| Issues List | Ongoing | See data/issues/ (managed by ceos-ids) |
Process
Step 1: Read the Current V/TO
Read data/vision.md from the CEOS repository root. If the file doesn't exist, tell the user to run setup.sh init first.
Display a summary of the current state:
- Company name (from the document header)
- Last updated date
- Quick snapshot of each section (one line each)
Step 2: Identify the Request
| User Intent | Action |
|---|---|
| "Review the V/TO" | Display full document, ask which sections to discuss |
| "Update [section]" | Jump to that section for editing |
| "Check alignment" | Cross-reference Rocks against 1-Year Plan |
| "What's our [specific item]?" | Read and present that section |
Step 3: For Updates
When the user wants to change a section:
- Show the current content of that section
- Discuss the change — ask clarifying questions if the request is vague
- Draft the update — write the new content
- Show the diff — display before/after for the changed section
- Ask for approval — "Does this look right? Apply this change?"
- Write the file — update
data/vision.mdwith the approved change - Update the date — change "Last updated" to today's date
Step 4: Alignment Check (Cross-Reference)
When reviewing the V/TO or when specifically asked about alignment:
- Read the 1-Year Plan section from
data/vision.md - Read all Rocks in
data/rocks/[current-quarter]/ - Compare: Does each Rock clearly support a 1-Year Plan goal?
- Flag any misalignment:
- Rocks that don't map to any 1-Year Plan goal
- 1-Year Plan goals with no supporting Rocks
- Rocks that seem to contradict the Core Focus
Report findings clearly:
Alignment Check:
- 4/5 Rocks map to 1-Year Plan goals ✓
- Rock "Build Mobile App" doesn't connect to any 1-Year goal ⚠️
- 1-Year goal "Expand to 3 new markets" has no supporting Rock ⚠️Step 5: After Changes
After any update:
- Summarize what was changed
- Suggest related actions (e.g., "You updated the 1-Year Plan — want to review Rock alignment?")
- Remind the user to commit: "Run
git committo save this update"
Show full SKILL.md (412 more words)Show less
Output Format
When displaying the V/TO, use the document's existing markdown structure. For updates, show a clear before/after diff of the changed section only (not the entire document).
For alignment checks, use the summary format shown in Step 4.
Guardrails
- Always show diff before writing. Never modify
data/vision.mdwithout showing the user what will change and getting explicit approval. - Preserve existing structure. Don't reorganize sections or change formatting unless the user asks. The V/TO follows the EOS format — respect it.
- Cross-reference when relevant. If the user updates the 1-Year Plan or Core Focus, proactively offer an alignment check against current Rocks.
- Don't modify Rocks or Issues directly. The Quarterly Rocks and Issues List sections in the V/TO link to
data/rocks/anddata/issues/. Direct the user toceos-rocksorceos-idsfor those. - One section at a time. Don't try to rewrite the entire V/TO at once. Guide the user through focused updates.
- Respect the planning horizons. Core Values and Core Focus should change rarely (annually at most). 10-Year Target shifts slowly. 3-Year Picture and 1-Year Plan are reviewed quarterly.
- Don't auto-invoke other skills. Mention
ceos-rocks,ceos-ids, andceos-annualwhen relevant, but let the user decide when to switch workflows. - Sensitive data warning. On first use, remind the user: "The V/TO may contain sensitive strategic data. Use a private repo."
Integration Notes
Rocks (ceos-rocks)
- Read:
ceos-rocksreads the 1-Year Plan section fromdata/vision.mdwhen setting Rocks to check alignment. Each Rock should connect to a 1-Year Plan goal. - Suggested flow: After updating the 1-Year Plan, suggest: "Want to check Rock alignment? Use
ceos-rocksTracking mode."
People Analyzer (ceos-people)
- Read:
ceos-peoplereads Core Values fromdata/vision.mdto evaluate team members against the company's values. - Suggested flow: If Core Values are updated, mention: "Core Values changed — existing people evaluations may need refreshing via
ceos-people."
Annual Planning (ceos-annual)
- Read/Write:
ceos-annualfacilitates a full V/TO refresh during the annual planning session. The annual skill guides the team through updating each section. - Suggested flow: V/TO updates outside annual planning are fine for minor changes. Major strategic shifts should wait for the annual session.
Quarterly Conversations (ceos-quarterly)
- Read:
ceos-quarterlyreferences V/TO goals during quarterly conversations to assess alignment between individual performance and company direction.
Write Principle
Only ceos-vto writes to data/vision.md. Other skills read it for reference (Core Values, 1-Year Plan, Core Focus). The annual planning session is the one structured time to do a full V/TO refresh, but ad-hoc updates via ceos-vto are appropriate for corrections and minor changes.
© bradfeld, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/ceos-vto of bradfeld/ceos.
Open the folder on GitHubat commit bdd5f01
Compare with similar skills
Ceos Vto next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Ceos Vto this skillbradfeld/ceos | 156 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Company CeoPrism-Shadow/penguin-harness | 2.5k | — | ~5.5k | Automated safety check: Pass | Apache-2.0 | |
| Company Brain Company QAtopoteretes/cognee | 32k | — | ~750 | Automated safety check: Notes | Apache-2.0 | |
| Fal Visionnexu-io/open-design | 100k | — | ~295 | Automated safety check: Pass | Apache-2.0 | |
| Organizationthedaviddias/Front-End-Checklist | 74k | — | ~609 | Automated safety check: Pass | MIT | |
| Openclaw Updateopenclaw/openclaw | 392k | — | ~1.5k | Automated safety check: Pass | MIT |
Similar skills
Company Brain Company QA
topoteretes/cognee
Build one company memory from a SQL database, a support ticket export and a folder of documents, linked into one graph by cognee, then answer questions that need several of those sources together.
Fal Vision
nexu-io/open-design
Analyze images — segment objects, detect, run OCR, describe, and answer visual questions via fal.ai vision models.
Organization
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing structured data on a business or brand website homepage.
Openclaw Update
openclaw/openclaw
Route routine updates of an existing local or remote OpenClaw Gateway to its installation owner, with automatic session recovery.
- Official
Update Docs
vercel/next.js
This skill should be used when the user asks to "update documentation for my changes", "check docs for this PR", "what docs need updating", "sync docs with code", "scaffold docs for this feature"…
More from bradfeld/ceos
All 23 skills in this repoCeos Accountability
bradfeld/ceos
A skill your agent uses when viewing, updating, or auditing the Accountability Chart — seats, owners, and roles
Ceos Assistance
bradfeld/ceos
A skill your agent uses when managing daily operational delegation through The Stack and structured leader-assistant standups
Ceos Calendar
bradfeld/ceos
A skill your agent uses when managing the rolling market calendar - conferences, launches, fundraising milestones, partner events, and team constraints
Ceos Cashflow
bradfeld/ceos
A skill your agent uses when assessing and optimizing the 8 financial levers that drive cash flow and profitability
Ceos Clarity
bradfeld/ceos
A skill your agent uses when taking a Clarity Break — stepping back from day-to-day work for strategic thinking time
Ceos Dashboard
bradfeld/ceos
A skill your agent uses when you want a quick snapshot of overall business health across all EOS components
Questions about Ceos Vto
What does Ceos Vto do?
A skill your agent uses when reviewing or updating the company Vision/Traction Organizer. Ceos Vto is an agent skill from bradfeld/ceos.
When should I use Ceos Vto?
Ceos Vto fits situations like: updating the company Vision/Traction Organizer.
How do I install Ceos Vto in Claude Code?
Run `npx skills add bradfeld/ceos --skill ceos-vto -a claude-code`. Or copy the skill folder (skills/ceos-vto in bradfeld/ceos) into .claude/skills/ceos-vto in your project. Claude Code loads it when a task matches its description.
How do I install Ceos Vto in Codex?
Run `npx skills add bradfeld/ceos --skill ceos-vto -a codex`. Or copy the skill folder (skills/ceos-vto in bradfeld/ceos) into .agents/skills/ceos-vto in your project. Codex loads it when a task matches its description.
Can I use Ceos Vto in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add bradfeld/ceos --skill ceos-vto -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ceos-vto, .gemini/skills/ceos-vto, .github/skills/ceos-vto and .opencode/skills/ceos-vto in your project.
What does Ceos Vto need to run?
Going by SKILL.md and its folder, Ceos Vto needs the command-line tools its instructions call (git).
Does Ceos Vto access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Ceos Vto safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Ceos Vto use?
Ceos Vto is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Ceos Vto use?
About 1.9k tokens (SKILL.md is roughly 7.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Ceos Vto?
Skills that share tags, products or a category with Ceos Vto: Company Ceo (Prism-Shadow/penguin-harness, 2.5k stars), Company Brain Company QA (topoteretes/cognee, 32k stars), Fal Vision (nexu-io/open-design, 100k stars) and Organization (thedaviddias/Front-End-Checklist, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ceos Vto?
bradfeld (a GitHub user) maintains it in bradfeld/ceos, which has 156 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on September 13, 2026.
Source: bradfeld/ceos on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.