Agent skill

Company Os

Meta-framework for how a company runs -- the connective tissue between C-suite roles (EOS, Scaling Up, OKR-native).

MITAuto-check passedBusiness, Finance & HR

Install Company Os

skills CLI

$ npx skills add borghei/Claude-Skills --skill company-os -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install borghei/Claude-Skills company-os --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/c-level-advisor/company-os .claude/skills/company-os && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "company-os" agent skill from https://github.com/borghei/Claude-Skills/tree/main/c-level-advisor/company-os into .claude/skills/company-os/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "company-os", 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

$skill-installer install https://github.com/borghei/Claude-Skills/tree/main/c-level-advisor/company-os

Type 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.

skills CLI

$ npx skills add borghei/Claude-Skills --skill company-os -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install borghei/Claude-Skills company-os --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/c-level-advisor/company-os .agents/skills/company-os && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "company-os" agent skill from https://github.com/borghei/Claude-Skills/tree/main/c-level-advisor/company-os into .agents/skills/company-os/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "company-os", 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.

skills CLI

$ npx skills add borghei/Claude-Skills --skill company-os -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install borghei/Claude-Skills company-os --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/c-level-advisor/company-os .cursor/skills/company-os && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "company-os" agent skill from https://github.com/borghei/Claude-Skills/tree/main/c-level-advisor/company-os into .cursor/skills/company-os/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "company-os", 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

$ gemini skills install https://github.com/borghei/Claude-Skills.git --path c-level-advisor/company-os

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add borghei/Claude-Skills --skill company-os -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install borghei/Claude-Skills company-os --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/c-level-advisor/company-os .gemini/skills/company-os && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "company-os" agent skill from https://github.com/borghei/Claude-Skills/tree/main/c-level-advisor/company-os into .gemini/skills/company-os/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "company-os", 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.

GitHub CLI

$ gh skill install borghei/Claude-Skills company-os

Installs 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).

skills CLI

$ npx skills add borghei/Claude-Skills --skill company-os -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/c-level-advisor/company-os .github/skills/company-os && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "company-os" agent skill from https://github.com/borghei/Claude-Skills/tree/main/c-level-advisor/company-os into .github/skills/company-os/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "company-os", 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.

skills CLI

$ npx skills add borghei/Claude-Skills --skill company-os -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install borghei/Claude-Skills company-os --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/c-level-advisor/company-os .opencode/skills/company-os && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "company-os" agent skill from https://github.com/borghei/Claude-Skills/tree/main/c-level-advisor/company-os into .opencode/skills/company-os/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "company-os", 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: company-os
GitHub stars: 891
Token cost: ~4.7k tokens
SKILL.md length: 1,871 words
Files: 4 (incl. scripts)
Skills in repo: 354
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Meta-framework for how a company runs -- the connective tissue between C-suite roles (EOS, Scaling Up, OKR-native).

Setting up company operations
SKILL.md covers Keywords, Clarify First, Operating System Selection and The Six Core Components, plus 10 more sections
Runs Python scripts from its folder; calls python
Selecting a management framework

What it does

Company Os is an agent skill from borghei/Claude-Skills. Meta-framework for how a company runs -- the connective tissue between C-suite roles (EOS, Scaling Up, OKR-native). Use when setting up company operations, selecting a management framework, designing meeting rhythms, or implementing OKRs.

Its SKILL.md is about 4.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts (for example `scripts/meeting_pulse_designer.py`, `scripts/rocks_tracker.py` and `scripts/scorecard_builder.py`).

It sits in Business, Finance & HR, covering OKRs and executive reporting. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.

When your agent uses it

Setting up company operations
Selecting a management framework
Designing meeting rhythms
Implementing OKRs

Example prompts

“/company-os”

Requirements

Python 3

What it can do on your machine

Read from SKILL.md and the folder at commit 4a698e8. 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
Ships 3 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
- python
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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

Company Os loads about 4.7k tokens when it runs. Until then it costs about 62 tokens; SKILL.md has 1,871 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~62
When it runs · the whole SKILL.md, loaded when a task matches: ~4.7k

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); the scripts in this folder are not scanned.

SKILL.md

The full file from borghei/Claude-Skills at commit 4a698e8, republished under its MIT licence (© borghei). 1,871 words, ~4,693 tokens.

Download SKILL.mdSave it as .claude/skills/company-os/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.

name: company-os
description: Meta-framework for how a company runs -- the connective tissue between C-suite roles (EOS, Scaling Up, OKR-native). Use when setting up company operations, selecting a management framework, designing meeting rhythms, or implementing OKRs.
license: MIT + Commons Clause
metadata.version: 2.0.0
metadata.author: borghei
metadata.category: c-level
metadata.domain: company-operations
metadata.updated: 2026-03-09
metadata.frameworks: os-comparison, accountability-chart, scorecard-design, meeting-pulse, ids-resolution, rocks-framework, communication-cadence
metadata.triggers: operating system, company OS, EOS, Scaling Up, Rockefeller Habits, OKR, OKRs, L10 meeting, rocks, scorecard, accountability chart, issues list, IDS, meeting…

Company Operating System

The operating system is the collection of tools, rhythms, and agreements that determine how the company functions. Every company has one -- most just do not know what it is. Making it explicit makes it improvable.

Keywords

operating system, EOS, Entrepreneurial Operating System, Scaling Up, Rockefeller Habits, OKR, Holacracy, L10 meeting, rocks, scorecard, accountability chart, issues list, IDS, meeting pulse, quarterly planning, weekly scorecard, management framework, company rhythm, traction, annual planning, communication cadence

Clarify First

Before generating, confirm these inputs. If any is unknown or vague, ASK — do not assume:

Company size and stage — the framework recommendation (EOS / Scaling Up / OKR-native / Holacracy) and implementation timeline are driven primarily by headcount
What is actually broken (no scorecard, misaligned priorities, recurring unresolved issues, meeting overload) — determines which of the six components to build first
Founder operating style (operational vs. visionary) and whether the company is engineering-led or sales-led — tips the framework choice within a given size band
What rhythms and metrics already exist — so the new OS replaces meetings rather than stacking on top and causing meeting fatigue

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.

Operating System Selection

Decision Tree

START: "Which operating system?"
  |
  v
[Company size?]
  |
  +-- 10-50 people
  |     |
  |     v
  |   [Is the founder operational or visionary?]
  |     |
  |     +-- Operational --> EOS / Traction (structured, simple)
  |     +-- Visionary --> Scaling Up (ambitious, strategy-heavy)
  |
  +-- 50-200 people
  |     |
  |     v
  |   [Engineering-led or sales-led?]
  |     |
  |     +-- Engineering-led --> OKR-native (hypothesis-driven)
  |     +-- Sales-led --> Scaling Up or EOS (execution-focused)
  |
  +-- 200+ people
  |     |
  |     v
  |   [High autonomy or high alignment needed?]
  |     |
  |     +-- High autonomy --> Holacracy (only if patient)
  |     +-- High alignment --> Custom hybrid (best of EOS + OKR)
  |
  +-- Not sure --> Start with EOS. It is the simplest to implement.

Framework Comparison Matrix

Feature	EOS	Scaling Up	OKR-Native	Holacracy
Complexity	Low	Medium	Medium	High
Implementation time	30-90 days	90-180 days	60-120 days	6-12 months
Best company size	10-250	50-500	20-500	50-300
Goal framework	Rocks (binary)	OKRs + Priorities	OKRs (graded)	Roles + accountabilities
Meeting cadence	Weekly L10	Daily huddle + weekly	Weekly + quarterly	Governance + tactical
Issue resolution	IDS	Keep/Kill/Combine	Retrospective	Governance process
Accountability	Accountability chart	Function accountability	OKR ownership	Role-based
Scorecard	Weekly numbers	Weekly KPIs	Quarterly KRs	Metrics per role
Strengths	Simple, fast to implement	Rigorous, strategy-heavy	Flexible, tech-friendly	Distributed authority
Weaknesses	Can feel rigid	Complex, requires discipline	Can drift without structure	Steep learning curve

The Six Core Components

Every effective operating system has these six, regardless of framework:

Component 1: Accountability Chart

Not an org chart. An accountability chart answers: "Who owns this outcome?"

Design Principles

Principle	Implementation
Single ownership	One person owns each function. Multiple may work in it.
Explicit gaps	Functions nobody owns are identified and assigned.
No overlap	If two people think they own it, neither does. Resolve immediately.
Stage-appropriate	One person can own multiple seats early. Be explicit about it.
Quarterly review	Ownership shifts as company grows. Review every quarter.

Accountability Chart Template

CEO
  |
  +-- Revenue (CRO/VP Sales)
  |     +-- Inbound pipeline
  |     +-- Outbound pipeline
  |     +-- Customer success
  |
  +-- Product & Engineering (CTO/CPO)
  |     +-- Product roadmap
  |     +-- Engineering delivery
  |     +-- Technical operations
  |
  +-- Operations (COO)
  |     +-- Finance & legal
  |     +-- People operations
  |     +-- Business operations
  |
  +-- Marketing (CMO/VP Marketing)
        +-- Demand generation
        +-- Brand & content
        +-- Product marketing

Workshop Protocol (2 hours)

Step 1: List all functions the company performs (30 min)
Step 2: Assign ONE owner per function (30 min)
Step 3: Identify gaps (functions nobody owns) (15 min)
Step 4: Identify overlaps (2+ people claiming ownership) (15 min)
Step 5: Resolve gaps and overlaps (20 min)
Step 6: Publish and communicate (10 min)

Component 2: Scorecard

Weekly metrics that tell you if the company is on track. Not monthly. Not quarterly. Weekly.

Scorecard Rules

Rule	Rationale
5-15 metrics maximum	More than 15 = nothing gets attention
Each metric has an owner	Ownership drives accountability
Each metric has a weekly target	Not a range -- a specific number
Red/Yellow/Green status	Not paragraphs -- traffic lights
Only Red metrics get discussion	Green = no discussion needed in meeting

Example Scorecard

Metric	Owner	Target	Week	Status
New MRR	CRO	$50K	$43K	[R]
Logo churn	CS Lead	< 1%	0.8%	[G]
Active users	CPO	2,000	2,150	[G]
Deployments	CTO	3/week	3	[G]
Critical bugs open	CTO	0	2	[R]
Runway	CFO	> 18mo	16mo	[Y]
Offer acceptance	CHRO	> 85%	90%	[G]

Component 3: Meeting Pulse

Full Meeting Rhythm

Meeting	Frequency	Duration	Who	Purpose
Daily standup	Daily	15 min	Each team	Blockers only
L10 / Leadership sync	Weekly	90 min	Leadership team	Scorecard + issues
Department review	Monthly	60 min	Dept + leadership	Deep dive on dept metrics
Quarterly planning	Quarterly	1-2 days	Leadership	Set rocks, review strategy
Annual planning	Annual	2-3 days	Leadership	1-year + 3-year vision

L10 Meeting Agenda (Weekly Leadership)

Segment	Duration	Activity
Good news	5 min	Personal + business wins
Scorecard review	5 min	Flag red items only
Rock review	5 min	On/off track for each rock
Customer/employee headlines	5 min	Notable events
Issues list (IDS)	60 min	Identify, Discuss, Solve
To-dos review	5 min	Last week's commitments: done or not?
Conclude	5 min	Rate meeting 1-10, what would make it 10 next time

Component 4: Issue Resolution (IDS)

Maximum 15 minutes per issue. This is the core problem-solving loop.

IDENTIFY: What is the actual issue? (One sentence, root cause, not symptom)
  |
DISCUSS: Relevant facts + perspectives. Time-boxed.
  |       When discussion starts repeating, STOP.
  |
SOLVE: One owner. One action. One due date. Written down.

IDS Anti-Patterns

Anti-Pattern	Why It Fails	Fix
"Let's take this offline"	Things taken offline rarely get resolved	Solve it now or put it on next week's list
Discussing without deciding	Great discussion, no action item = wasted	Every discussion must end with a decision
Revisiting decided issues	Undermines the system	Once solved, off the list. Reopen only with new data.
Issue on list 3+ meetings	Either not real or too scary to address	Force it: address this week or remove it
Multiple issues conflated	Impossible to solve a bundled problem	One issue per entry. Separate if needed.

Component 5: Rocks (90-Day Priorities)

Rock Rules

Rule	Rationale
3-7 per person maximum	More than 7 = none get done
3-7 company-level rocks	Shared leadership priorities
Binary status: done or not done	No "60% complete"
Set at quarterly planning	Reviewed weekly (on/off track)
Not a to-do list	Rocks take 90 days of sustained work

Good vs. Bad Rocks

Bad Rock	Why	Good Rock
"Improve sales process"	Not measurable or specific	"Implement CRM with pipeline stages and reporting by Mar 31"
"Hire more engineers"	No target, no deadline	"Hire 3 senior engineers with offers accepted by Apr 15"
"Reduce churn"	No target	"Reduce monthly logo churn from 3% to 1.5% by end of Q2"
"Get better at communication"	Not observable	"Ship weekly company update every Friday for 12 weeks"

Component 6: Communication Cadence

Audience	What	When	Format
All employees	Company update	Monthly	Written + Q&A
All employees	Quarterly results + priorities	Quarterly	All-hands meeting
Leadership team	Scorecard	Weekly	Dashboard
Board	Company performance	Monthly or quarterly	Board memo/deck
Investors	Key metrics + narrative	Monthly or quarterly	Investor update
Customers	Product updates	Per release	Release notes

Default rule: If deciding whether to share internally, share it. Under-communication always costs more than over-communication.

Implementation Roadmap

30-Day Quick Start

Week	Activity	Time Investment
1	Build accountability chart	2-hour workshop
2	Define 5-10 weekly scorecard metrics	1-hour alignment session
3	Start weekly L10 meeting	90 min/week (ongoing)
4	Set first round of 90-day rocks	Half-day planning session

These four alone improve coordination more than most companies achieve in a year.

90-Day Full Implementation

Month	Focus	Deliverables
1	Foundation	Accountability chart, scorecard, L10 meetings
2	Depth	Rocks defined, issues list active, daily standups
3	Cadence	Full meeting rhythm, communication cadence, first quarterly review

Common Failure Modes

Failure	Symptom	Fix
Partial implementation	"We do OKRs but skip check-ins"	Half an OS is worse than none. Commit to the full system.
Meeting fatigue	Added rhythm on top of existing meetings	Replace meetings, do not add them
Metric overload	30 KPIs because "they all matter"	Start with 5. Add only when cadence is established.
Rock inflation	12 rocks per person	Hard limit: 7 per person, 7 for the company.
Leader non-compliance	Leadership skips L10 or ignores IDS	The OS mirrors leadership respect. Leaders go first.
No quarterly review	Annual goals checked at year-end	Quarterly is the minimum review cycle.
Scorecard without targets	Tracking numbers without thresholds	Every metric needs a target to be actionable.

Show full SKILL.md (699 more words)Show less

Red Flags

Five team leads give different answers when asked "What are the top 3 company priorities?" -- alignment failure
Same issue on the issues list for 4+ weeks -- avoidance or structural problem
No weekly scorecard exists -- flying blind
Rocks set but never reviewed weekly -- goals without accountability
Accountability chart has not been updated in 6+ months -- reality has drifted
Meetings consistently end without decisions -- meeting design problem
Communication is all top-down, never bottom-up -- feedback loop broken

Integration with C-Suite

Role	OS Dependency
CEO (`ceo-advisor`)	Sets vision that feeds 1-year plan and rocks
COO (`coo-advisor`)	Owns meeting pulse and issue resolution cadence
CFO (`cfo-advisor`)	Owns financial metrics in the scorecard
CTO (`cto-advisor`)	Owns engineering rocks and tech scorecard metrics
CHRO (`chro-advisor`)	Owns people metrics (attrition, hiring velocity)
Culture Architect (`culture-architect`)	Culture rituals integrate into meeting pulse
Strategic Alignment (`strategic-alignment`)	Validates team rocks cascade from company rocks
Change Management (`change-management`)	New OS rollout follows ADKAR model

Output Artifacts

Request	Deliverable
"Set up our operating system"	Framework recommendation + 30-day implementation plan
"Design our meeting cadence"	Full meeting rhythm with agendas and owners
"Build our scorecard"	5-15 metrics with owners, targets, and thresholds
"Help with quarterly planning"	Planning session agenda + rock-setting framework
"Fix our accountability"	Accountability chart workshop + gap/overlap analysis
"We keep discussing the same issues"	IDS training + issues list audit

Tool Reference

scorecard_builder.py

Builds and tracks weekly company scorecards with RAG status, trend analysis, and IDS-ready issue lists for L10 meetings.

bash

# Run with demo data
python scripts/scorecard_builder.py

# From JSON with metrics and rocks
python scripts/scorecard_builder.py --input scorecard.json

# JSON output
python scripts/scorecard_builder.py --json

rocks_tracker.py

Tracks 90-day company and individual rocks with binary status, blocker identification, and owner accountability.

bash

# Run with demo data
python scripts/rocks_tracker.py

# Specify quarter
python scripts/rocks_tracker.py --quarter Q2

# From JSON
python scripts/rocks_tracker.py --input rocks.json

# JSON output
python scripts/rocks_tracker.py --json

meeting_pulse_designer.py

Designs company meeting rhythms, validates meeting load, identifies redundancies and gaps, and generates L10 agenda templates.

bash

# Run with demo meetings
python scripts/meeting_pulse_designer.py

# Specify team size
python scripts/meeting_pulse_designer.py --team-size 50

# From JSON with current meetings
python scripts/meeting_pulse_designer.py --input meetings.json

# JSON output
python scripts/meeting_pulse_designer.py --json

Troubleshooting

Problem	Likely Cause	Fix
Five team leads give different answers about top 3 priorities	Alignment failure -- rocks not cascaded or not reviewed weekly	Re-run quarterly planning; review rocks weekly in L10; publish company priorities visibly
Same issue on the issues list for 4+ weeks	Avoidance or structural problem too scary to address	Force it: address this week or permanently remove; escalate if needed
Scorecard has 30+ KPIs	Metric overload -- nothing gets attention	Cut to 5-10 metrics. Only the ones that tell you if the company is on track.
Rocks set but never reviewed	Goals without accountability; L10 meeting not happening	Weekly L10 is non-negotiable; 5 minutes on rocks review every week
Leadership team skips L10 or ignores IDS	Leader non-compliance destroys the OS	CEO must enforce: leaders go first. If CEO skips, the OS dies.
Meetings added on top of existing meetings	Meeting fatigue from accumulation	Replace meetings, don't add them. Audit meeting inventory; eliminate redundancies

Success Criteria

Weekly L10 meeting happens every week with 90%+ leadership attendance (no exceptions for 12+ consecutive weeks)
Scorecard reviewed weekly with red metrics discussed using IDS format (zero red metrics ignored)
70%+ of quarterly rocks completed as binary done/not-done by end of quarter
Issues list: average issue resolved within 2 meetings (no issue lingers 4+ weeks)
All team leads can articulate top 3 company priorities identically (tested quarterly)
Meeting hours per person per week below 10 hours (measured via meeting_pulse_designer.py)
Accountability chart reviewed and updated quarterly with zero unowned functions

Scope & Limitations

In Scope: Operating system selection (EOS, Scaling Up, OKR, Holacracy), accountability charts, weekly scorecards, meeting pulse design, IDS issue resolution, 90-day rocks, communication cadence, implementation roadmap.

Out of Scope: OKR software configuration, project management tool setup, Agile/Scrum methodology, sprint planning, product backlog management, HR policy development.

Limitations: Scorecard builder calculates RAG from provided data but cannot source live metrics from business systems. Rocks tracker uses manual status updates -- it cannot automatically detect completion. Meeting pulse designer provides recommendations based on team size and meeting inventory but cannot account for company-specific cultural norms. Framework comparison is directional -- actual implementation success depends on leadership commitment.

Integration Points

Skill	Integration
`ceo-advisor`	CEO sets vision that feeds 1-year plan and rocks
`coo-advisor`	Owns meeting pulse and issue resolution cadence
`cfo-advisor`	Financial metrics in the weekly scorecard
`cto-advisor`	Engineering rocks and tech scorecard metrics
`chro-advisor`	People metrics (attrition, hiring velocity) in scorecard
`culture-architect`	Culture rituals integrate into meeting pulse
`strategic-alignment`	Validates team rocks cascade from company rocks
`change-management`	New OS rollout follows ADKAR model for adoption
`chief-of-staff`	Orchestrates quarterly planning sessions and L10 follow-up

Files

SKILL.md and 3 other files (scripts) in c-level-advisor/company-os of borghei/Claude-Skills.

SKILL.md
scripts/meeting_pulse_designer.py
scripts/rocks_tracker.py
scripts/scorecard_builder.py

Open the folder on GitHubat commit 4a698e8

Compare with similar skills

Company Os 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.

Company Os compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Company Os this skillborghei/Claude-Skills	891	—	~4.7k	Automated safety check: Pass	MIT	3 days ago
Pine BacktesterTradersPost/pinescript-agents	170	1 repos	~3.9k	Automated safety check: Pass	None	2 mo ago
Analytics Strategyrampstackco/claude-skills	945	—	~2.4k	Automated safety check: Pass	MIT	3 days ago
Onboarding Plannerbpinheiroms/dotfiles	108	—	~5.4k	Automated safety check: Pass	None	4 mo ago
Replit Decksanqiufong/slides-from-anything	132	1 repos	~2.9k	Automated safety check: Pass	Apache-2.0	today
Building Streamlit Dashboardsiusztinpaul/designing-real-world-ai-agents-workshop	512	—	~1.1k	Automated safety check: Pass	Apache-2.0	4 mo ago

Similar skills

Pine Backtester
TradersPost/pinescript-agents
Implements comprehensive backtesting and performance metrics.
170 GitHub starsUsed in 1 repo~3.9k tokens
Business, Finance & HRAuto-check passed
Analytics Strategy
rampstackco/claude-skills
Design measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy.
945 GitHub stars~2.4k tokensUpdated 3 days ago
Business, Finance & HRAuto-check passed
Onboarding Planner
bpinheiroms/dotfiles
Plan high-conversion mobile app onboarding flows from scratch.
108 GitHub stars~5.4k tokensUpdated 4 mo ago
Business, Finance & HRAuto-check passed
Replit Deck
sanqiufong/slides-from-anything
Single-file horizontal-swipe HTML deck in the style of Replit Slides's landing-page template gallery.
132 GitHub starsUsed in 1 repo~2.9k tokens
Business, Finance & HRAuto-check passed
Building Streamlit Dashboards
iusztinpaul/designing-real-world-ai-agents-workshop
Building dashboards in Streamlit. An agent skill from iusztinpaul/designing-real-world-ai-agents-workshop.
512 GitHub stars~1.1k tokensUpdated 4 mo ago
Business, Finance & HRAuto-check passed
Massing Bim
ibuilder/massing
Drive a Massing BIM/AEC project from an AI agent over MCP — read a project's status, records, CDE, KPI and model-quality checks; run standards-compliance, schedule-risk, embodied-carbon, permit-…
122 GitHub stars~1.1k tokensUpdated yesterday
Business, Finance & HRAuto-check passed

Questions about Company Os

What does Company Os do?

Meta-framework for how a company runs -- the connective tissue between C-suite roles (EOS, Scaling Up, OKR-native). Company Os is an agent skill from borghei/Claude-Skills. Meta-framework for how a company runs -- the connective tissue between C-suite roles (EOS, Scaling Up, OKR-native).

When should I use Company Os?

Company Os fits situations like: setting up company operations; selecting a management framework; designing meeting rhythms; implementing OKRs.

How do I install Company Os in Claude Code?

Run `npx skills add borghei/Claude-Skills --skill company-os -a claude-code`. Or copy the skill folder (c-level-advisor/company-os in borghei/Claude-Skills) into .claude/skills/company-os in your project. Claude Code loads it when a task matches its description.

How do I install Company Os in Codex?

Run `npx skills add borghei/Claude-Skills --skill company-os -a codex`. Or copy the skill folder (c-level-advisor/company-os in borghei/Claude-Skills) into .agents/skills/company-os in your project. Codex loads it when a task matches its description.

Can I use Company Os 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 borghei/Claude-Skills --skill company-os -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/company-os, .gemini/skills/company-os, .github/skills/company-os and .opencode/skills/company-os in your project.

What does Company Os need to run?

Going by SKILL.md and its folder, Company Os needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.

Does Company Os access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Company Os 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Company Os use?

Company Os is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Company Os use?

About 4.7k tokens (SKILL.md is roughly 19k 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 Company Os?

Skills that share tags, products or a category with Company Os: Pine Backtester (TradersPost/pinescript-agents, 170 stars), Analytics Strategy (rampstackco/claude-skills, 945 stars), Onboarding Planner (bpinheiroms/dotfiles, 108 stars) and Replit Deck (sanqiufong/slides-from-anything, 132 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Company Os?

borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 891 GitHub stars. The repository holds 354 skills in this directory. The repository was last updated on October 7, 2026.

Source: borghei/Claude-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Company Os

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Company Operating System

Keywords

Clarify First

Operating System Selection

Decision Tree

Framework Comparison Matrix

The Six Core Components

Component 1: Accountability Chart

Design Principles

Accountability Chart Template

Workshop Protocol (2 hours)

Component 2: Scorecard

Scorecard Rules

Example Scorecard

Component 3: Meeting Pulse

Full Meeting Rhythm

L10 Meeting Agenda (Weekly Leadership)

Component 4: Issue Resolution (IDS)

IDS Anti-Patterns

Component 5: Rocks (90-Day Priorities)

Rock Rules

Good vs. Bad Rocks

Component 6: Communication Cadence

Implementation Roadmap

30-Day Quick Start

90-Day Full Implementation

Common Failure Modes

Red Flags

Integration with C-Suite

Output Artifacts

Tool Reference

scorecard_builder.py

rocks_tracker.py

meeting_pulse_designer.py

Troubleshooting

Success Criteria

Scope & Limitations

Integration Points

Files

Compare with similar skills

Similar skills

More from borghei/Claude-Skills

Related

Questions about Company Os