Company Operating System — Business

Company Operating System is a meta-framework that helps companies define and improve how they run by covering the six core components of any effective operating system: accountability charts, scorecards, meeting pulse, issue resolution (IDS), 90-day rocks, and communication cadence. It guides users through selecting a management framework (EOS, Scaling Up, OKR-native, etc.) and provides an implementation roadmap to establish these systems.

c-level-advisor claude-code

📂 View skill on GitHub ↗ 🚀 How to use

✨ What it does

Explains the six core components of an operating system: accountability chart, scorecard, meeting pulse, issue resolutio
Provides a comparison guide for selecting between EOS, Scaling Up, OKR-native, Holacracy, or a hybrid approach
Offers a 90-day implementation roadmap with a quick start for the first 30 days
Details the L10 meeting agenda and IDS problem-solving loop
Lists common failure modes and anti-patterns to avoid
Shows how the operating system integrates with each C-suite role

🎯 When to use it

When setting up company operations or selecting a management framework (EOS, Scaling Up, OKRs, etc.)
When designing meeting rhythms, accountability systems, or quarterly planning processes
When recurring issues, unclear ownership, or unmet goals indicate a system problem
When the user mentions terms like L10 meetings, rocks, scorecard, accountability chart, or quarterly planning

🚀 How to use

Trigger the skill by mentioning topics like 'operating system', 'EOS', 'Scaling Up', 'L10 meetings', 'rocks', 'scorecard', 'accountability chart', or 'quarterly planning'. The skill expects a description of your company's current situation or goals, such as size, challenges, or the framework you're considering. It will then provide guidance on the six components, framework selection, and implementation steps.

Example prompts:

We're a 50-person startup with chaotic operations. How do we set up an operating system?

Help me implement EOS: we need an accountability chart, scorecard, and L10 meeting structure.

📄 Output: The skill provides structured guidance and actionable steps, but does not generate files; it outputs recommendations and frameworks in conversation.

📦 Add this skill to Claude Code

# 1. Get the skills repo
git clone --depth 1 https://github.com/alirezarezvani/claude-skills /tmp/claude-skills

# 2. Copy this skill into your project (or ~/.claude/skills for all projects)
mkdir -p .claude/skills
cp -r /tmp/claude-skills/c-level-advisor/skills/company-os .claude/skills/company-os

Skill source: c-level-advisor/skills/company-os/SKILL.md

⚠️ Good to know

The skill provides general guidance and references external files for detailed comparisons and implementation plans; it does not generate custom documents or templates.

❓ FAQ

What are the six core components of an operating system?

The six core components are: accountability chart, scorecard, meeting pulse, issue resolution (IDS), rocks (90-day priorities), and communication cadence.

How many rocks should each person have?

Each person should have 3-7 rocks maximum, with a hard limit of 7. More than 7 and none get done.

What is the IDS process?

IDS stands for Identify, Discuss, Solve. It's a time-boxed problem-solving loop used in meetings to resolve issues with one owner, one action, and one due date.

🤖 Overview, features, install steps and FAQ were generated from the project's SKILL.md on Sep 4, 2026. Always check the original source before running commands.