company-os

What This Skill Does

The company-os skill acts as the architectural blueprint for your organization. It is a meta-framework designed to help leadership teams formalize how they operate. Rather than simply tracking tasks, it provides a structured approach to implementing proven management frameworks like EOS (Entrepreneurial Operating System) or Scaling Up. By integrating the six core components of organizational health—specifically focusing on the Accountability Chart and the Weekly Scorecard—the skill helps you transition from chaotic, reactive management to a proactive, systemic rhythm. It forces clarity on 'who owns what' and provides the data-driven transparency needed to identify and resolve issues before they become terminal.

Installation

To integrate this skill into your environment, run the following command in your terminal:

clawhub install openclaw/skills/skills/alirezarezvani/company-os

Ensure your OpenClaw agent has the necessary permissions for configuration management and data structuring as defined in your policy settings.

Use Cases

• Establishing Governance: Use the skill during early-stage scaling to define clear roles and prevent overlaps in responsibilities.
• Meeting Optimization: Deploy it when leadership meetings feel like 'status updates' rather than 'decision-making' sessions; the skill will help you design a meeting pulse centered on IDS (Identify, Discuss, Solve).
• Performance Alignment: Implement the Scorecard system to move from gut-feeling management to objective, metric-led decision-making.
• Strategic Execution: Use it to turn abstract quarterly objectives into actionable 90-day 'Rocks' with defined owners and success criteria.

Example Prompts

1. "We are constantly arguing over who is responsible for customer onboarding. Can you help me design an accountability chart based on our current department heads?"
2. "Our weekly leadership meetings are unproductive and take over two hours. Can you suggest an L10 meeting agenda and help us build a 10-metric weekly scorecard?"
3. "We have hit a plateau in our growth. Walk me through the core components of the EOS framework and help us identify which one we are failing at."

Tips & Limitations

• Tip: Treat the Accountability Chart as a living document. It should evolve as the company moves from early-stage (where roles are fluid) to growth-stage (where specialized roles are required).
• Tip: When setting up your Scorecard, stick to the rule of 5-15 metrics. Including more will lead to cognitive overload and diminish the signal-to-noise ratio.
• Limitation: This skill provides the framework and the logic, but the success of an operating system depends entirely on the leadership team's discipline to follow the rhythms, specifically the commitment to the weekly meeting pulse.