company-os

Overview of company-os skill

What company-os is for

company-os is a C-level advisory skill for designing or improving the operating system of a company: the framework of roles, metrics, meetings, priorities, and issue-resolution habits that determines how work actually gets coordinated. It is most useful when leaders need to choose between EOS, Scaling Up, OKR-native, Holacracy, or a custom hybrid model, then translate that choice into an actionable operating cadence.

Best-fit users and operating situations

The company-os skill fits founders, CEOs, COOs, chiefs of staff, operations leaders, and leadership teams building Internal Operations discipline. It is especially relevant for founder-led teams, scaling companies with recurring coordination problems, or organizations preparing quarterly planning, accountability charts, leadership scorecards, L10-style meetings, rocks, OKRs, or weekly executive rhythms.

What makes this different from a generic prompt

A generic AI prompt may produce a list of management frameworks. company-os gives the agent a more specific operating lens: compare frameworks, identify current-system gaps, design accountability structures, define metrics, shape meeting pulses, and sequence implementation over 90 days. The included references are decision-oriented, not just conceptual: references/os-comparison.md helps with framework selection, while references/implementation-guide.md focuses on staged rollout.

When company-os is not the right skill

Do not use this skill as a substitute for legal HR policy design, compensation architecture, financial controls, or enterprise change-management consulting. It can help frame operating decisions, but it needs accurate context from your organization. If leadership is not aligned on adopting a shared operating rhythm, the skill can draft materials, but it cannot overcome lack of executive commitment.

How to Use company-os skill

company-os install and files to read first

Install the skill from the repository path:

npx skills add alirezarezvani/claude-skills --skill company-os

After installation, read SKILL.md first to understand the trigger concepts and operating-system vocabulary. Then inspect:

• references/os-comparison.md for EOS, Scaling Up, OKR-native, Holacracy, and hybrid tradeoffs.
• references/implementation-guide.md for a phased 90-day rollout sequence.
• The repository path: c-level-advisor/skills/company-os.

There is no separate README or script layer in this skill, so most practical value is in the main skill instructions and the two reference files.

Inputs the skill needs for useful output

For strong company-os usage, give the agent current operating context instead of asking for a generic framework. Include:

• Company stage, employee count, business model, and leadership team shape.
• Current meetings, planning cadence, and decision bottlenecks.
• Existing metrics, OKRs, scorecards, or lack of them.
• Known pain points: unclear ownership, repeated issues, weak follow-through, meeting overload, or quarterly priorities that do not stick.
• Constraints: remote/hybrid team, founder bandwidth, board expectations, implementation appetite, and whether you want EOS-like, OKR-native, Scaling Up, or hybrid guidance.

A weak prompt is: “Create a company operating system.”
A stronger prompt is: “Use company-os to design a lightweight operating system for a 45-person B2B SaaS company. We have weekly exec meetings, inconsistent OKRs, no accountability chart, and recurring handoff issues between sales and customer success. Recommend the best-fit framework, first 30 days of implementation, leadership scorecard, and meeting cadence.”

A practical company-os workflow

Start with diagnosis before design. Ask the skill to map your current operating gaps across ownership, data, meetings, issue resolution, and quarterly priorities. Next, request a framework recommendation with explicit tradeoffs: EOS vs Scaling Up vs OKR-native vs hybrid. Then create the core artifacts in order: accountability chart, scorecard, meeting pulse, issue list process, and 90-day rocks or OKRs.

For implementation, follow the repository’s staged logic: do not launch everything at once. A realistic company-os guide should begin with leadership alignment, current-state audit, and an OS owner. Then phase in the accountability chart and scorecard before adding heavier meeting and planning rituals.

Prompt patterns that improve outputs

Ask for decisions, not just explanations. Useful prompt phrases include:

• “Compare these operating models for our context and recommend one.”
• “Turn our messy org responsibilities into an accountability chart, not an org chart.”
• “Design a weekly leadership meeting agenda that replaces our current meetings.”
• “Create a 90-day implementation plan with risks, owner, and adoption checkpoints.”
• “Identify where this operating system is too heavy for our current stage.”

These prompts work because they give the skill a real operating job: choosing, sequencing, simplifying, and adapting.

company-os skill FAQ

Is company-os mainly an EOS skill?

No. EOS is one of the major frameworks covered, but company-os also supports Scaling Up, OKR-native systems, Holacracy, and custom hybrids. Use it when you want a framework decision, not only when you have already chosen EOS.

Can beginners use this skill without knowing management frameworks?

Yes, but the output improves if you describe your company’s current problems in plain language. You do not need to know terms like IDS, rocks, or accountability chart in advance. The skill is useful for translating symptoms—such as unclear ownership or repeated meetings—into operating-system components.

How is company-os for Internal Operations different from strategy planning?

Strategy planning defines where the company is going. Internal Operations defines how the company runs every week to execute that strategy. company-os connects the two through meeting rhythms, scorecards, accountability, quarterly priorities, and issue resolution.

When should I avoid installing company-os?

Avoid it if you only need a one-off meeting agenda, a generic OKR template, or personal productivity advice. It is best for teams willing to change operating habits across leadership, not for isolated documentation work with no implementation owner.

How to Improve company-os skill

Improve company-os results with sharper context

The biggest quality lever is specificity. Provide your current meeting list, leadership roles, metrics, planning artifacts, and pain points. If you have existing OKRs, scorecards, or org charts, paste summaries and ask the skill to convert them into operating-system artifacts. The skill performs better when it can adapt, simplify, or challenge existing practices instead of inventing from nothing.

Watch for common failure modes

Common weak outputs include overbuilt systems, too many meetings, unclear owners, and framework purity that does not match the company’s stage. Ask the skill to flag complexity, identify what to defer, and separate “must implement now” from “later once the rhythm is stable.” For small teams, request a lightweight version. For larger teams, request governance and rollout checkpoints.

Iterate after the first operating design

After receiving a first draft, run a second pass focused on adoption risk:

• “What will leaders resist?”
• “Which meetings can we delete or merge?”
• “Which metrics are lagging indicators and which are weekly controllables?”
• “Where is ownership still ambiguous?”
• “What should the OS owner inspect every Friday?”

This turns company-os from a static framework generator into a practical implementation partner.

Customize the skill for your organization

To improve the company-os skill locally, add examples of your preferred operating artifacts: scorecard templates, meeting agendas, quarterly planning formats, decision rights, and definitions of executive roles. Keep examples concise and current. The goal is not to lock the agent into one framework, but to make its recommendations match your company’s language, cadence, and tolerance for operational structure.