Agent skill · operations · alirezarezvani

company-os

Use when choosing or setting up how the company runs: EOS, Scaling Up or OKRs, accountability chart, scorecard, meeting rhythm, quarterly rocks.

Why this skill is useful

Provides a structured framework for company operations that the AI wouldn't reliably generate on its own, including accountability charts and meeting rhythms.

What it needs

About 7k tokens when loaded. Last updated 2026-08-05. 23,939 stars on the source repository.

What this skill does

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 each function. Multiple people may work in it. Ownership means the buck stops with one person. Structure: Rules: No shared ownership. "Alice and Bob both own it" means nobody owns it. One person can own multiple seats at early stages. That's fine. Just be explicit. Revisit quarterly as you scale. Ownership shifts as the company grows. Build it in a workshop: 1. List all functions the company performs 2. Assign one owner per function — no exceptions 3. Identify gaps (functions nobody owns) and overlaps (functions two people think they own) 4. Publish it. Update it when something changes. 2. Scorecard Weekly metrics that tell you if the company is on track. Not monthly. Not quarterly. Weekly. Rules: 5–15 metrics maximum. More than 15 and nothing gets attention. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills alirezarezvani/company-os--319001

View the source on GitHub

Browse the @skills marketplace