Company Os
The meta-framework for how a company runs — the connective tissue between all C-suite roles.
Before & after
Same prompt, same agent — the only difference is the skill.
Quarterly planning is important for keeping teams aligned. There are a few different operating systems you could choose—EOS, Scaling Up, OKR-native frameworks, or a hybrid approach. Each has different meeting rhythms and accountability structures. What's your current challenge—lack of clarity on goals, poor execution, misalignment across teams? That would help me recommend whether you need structured L10 meetings, scorecard tracking, or rock-based planning. How formal do you want the system to be?
QUARTERLY OS SETUP: 15-PERSON TEAM FRAMEWORK SELECTED: EOS-Lite (Scaling Up + OKRs) MEETING RHYTHM Weekly → Level 10 meeting (60 min, Mon 9am) • Segue (5 min) → Personal/team wins • Scorecard (5 min) → 5 KPIs reviewed vs. target • IDS (45 min) → Issues list, root cause, solve • Recap (5 min) → Commitments next week Monthly → Business review (90 min, first Friday) • Scorecard review → Full KPI dashboard vs. quarterly target • Rock progress → Each team lead updates 3-5 rocks • People review → Hiring, exits, role clarity Quarterly → Planning session (full-day offsite) SCORECARD TEMPLATE (5 metrics max) Metric | Owner | Current | Target | Status MRR | CFO | 42k | 55k | Yellow Churn % | VP Retention | 5.2% | 3.5% | Red Customer NPS | Head of Support | 52 | 65 | Yellow Employee eNPS | People Ops | 68 | 78 | On track Product Releases | VP Eng | 1/month | 2/month | Red ROCKS (Quarterly goals, 3-5 team rocks) • Platform reliability → 99.95% uptime SLA (Eng) • Expand enterprise accounts → 5 new logos (Sales) • Retention automation → Reduce churn to 3% (Retention) • Brand positioning → Launch podcast (Marketing) ACCOUNTABILITY CHART CEO → Scorecard owner, quarterly planning lead Level leads → Own 1-2 rocks each, scorecard metrics Individual contributors → Support rock execution, weekly IDS attendance NEXT 30 DAYS Week 1 → Scorecard baseline, identify current state Week 2 → Executive alignment meeting (metrics + rocks) Week 3 → Communicate to full team, collect input Week 4 → First L10 meeting, confirm rhythm
About this skill
name: company-os description: Use when The meta-framework for how a company runs — the connective tissue between all C-suite roles.
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.
What you get
- Public GitHub repo (alirezarezvani/claude-skills)
- the company-os skill folder with SKILL.md. Part of a 337-skill / 30-agent / 70-command install.
Customize your output
- Fork the repo and adapt the skill's instructions and references to your workflow.
Example output
Activates automatically when your request matches Company Os; chains with the other skills, agents, and commands in the collection.
Best for
Creators, builders, and teams using Claude Code.
SKILL.md preview
---
name: company-os
description: Use this skill when setting up company operations, selecting a management operating system, designing meeting rhythms, or building accountability and scorecard structures.
version: 1.0.0
category: Business & Ops / Executive Advisory
author: AgentVolt
license: proprietary
tags:
- business-ops
- executive-advisory
---
# Company Os
Acts as the connective operating framework for how a company runs, tying accountability, meeting rhythm, scorecards, and quarterly planning together.
## When to use
… (sign up to view the full skill)More business & ops skills
View all Business & Ops skills →Gc Review
/cs:gc-review <plan> — General Counsel interrogation of contracts, IP, regulatory, term sheets, and employment-law surface.
Caio Review
/cs:caio-review <plan> — Eval-demanding Chief AI Officer interrogation of any plan that involves AI: model selection, risk classification, cost economics, or AI hiring.
Boardroom
/cs:boardroom <brief> — 6-phase multi-role deliberation across the C-suite with Phase 2 isolation, critic pre-screen, and synthesis.
Context Engine
Loads and manages company context for all C-suite advisor skills.