company-os
The meta-framework for how a company runs — the connective tissue between all C-suite roles. Covers operating system selection (EOS, Scaling Up, OKR-native, hybrid), accountability charts, scorecards, meeting pulse, issue resolution, and 90-day rocks. Use when setting up company operations, selecting a management framework, designing meeting rhythms, building accountability systems, implementing OKRs, or when user mentions EOS, Scaling Up, operating system, L10 meetings, rocks, scorecard, accountability chart, or quarterly planning.
Profile →npx skills add alirezarezvani/claude-skills --skill company-os --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 don't 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, Gino Wickman, Verne Harnish ## Why This Matters Most operational dysfunction isn't a people problem — it's a system problem. When: - The same issues recur every week: no issue resolution system - Meetings feel pointless: no structured meeting pulse - Nobody knows who owns what: no accountability chart - Quarterly goals slip: rocks aren't real commitments Fix the system. The people will operate better inside it. ## The Six Core Components Every effective operating system has these six, regardless of which framework you choose: ### 1. Accountability Chart Not an org chart. An accountability chart answers: "Who owns this outcome?" **Key distinction:** One person owns
- Keywords
- Why This Matters
- The Six Core Components
- 1. Accountability Chart
- 2. Scorecard
- 3. Meeting Pulse
- 4. Issue Resolution (IDS)
- 5. Rocks (90-Day Priorities)
- 6. Communication Cadence
- Operating System Selection
- Implementation Roadmap
- Common Failure Modes
- Integration with C-Suite
- Key Questions for the Operating System
What does the company-os skill do?
The meta-framework for how a company runs — the connective tissue between all C-suite roles. Covers operating system selection (EOS, Scaling Up, OKR-native, hybrid), accountability charts, scorecards, meeting pulse, issue resolution, and 90-day rocks. Use when setting up company operations, selecting a management framework, designing meeting rhythms, building accountability systems, implementing OKRs, or when user mentions EOS, Scaling Up, operating system, L10 meetings, rocks, scorecard, accountability chart, or quarterly planning.
How do I install it?
Run `npx skills add alirezarezvani/claude-skills --skill company-os --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From alirezarezvani/claude-skills, a repository with 23,791 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.