CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

77

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

The risk profile of this skill

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-organized, highly actionable instruction skill that appropriately splits detail into one-level references and embeds feedback loops in its workflows. The only minor weakness is a few conceptual framing passages that slightly exceed the lean ideal.

Suggestions

Tighten or trim the 'Why This Matters' section and conceptual openers to reduce token spend on framing Claude already infers.

Consider moving the 'Integration with C-Suite' dependency table into a reference if it is only needed in specific role contexts, keeping the body focused on the six core components.

DimensionReasoningScore

Conciseness

The body is dense and mostly actionable (tables, hard-limit rules, time-boxed agendas, anti-patterns) with little pure padding, though sections like 'Why This Matters' and some conceptual framing add explanation that could be trimmed slightly.

4 / 5

Actionability

Highly concrete guidance throughout: hard limits ('5-15 metrics', '3-7 rocks', 'binary: done or not done'), example scorecard and accountability-chart structures, a timed L10 agenda, the IDS loop, and good/bad rock examples — fully actionable even without code.

5 / 5

Workflow Clarity

Multi-step processes are clearly sequenced with feedback loops: the L10 agenda ends with a 'rate the meeting 1-10' review, the issues list carries a '3+ meetings' attention signal, IDS is a three-step solve loop, and the implementation roadmap is an explicit checklist.

5 / 5

Progressive Disclosure

Well-signaled one-level-deep references to real files (references/os-comparison.md, references/implementation-guide.md) with quick guides kept inline and the full comparison and 90-day plan pushed to separate files; structure is clearly navigable.

5 / 5

Total

19

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-structured description that comprehensively states capabilities, trigger terms, and use-conditions in third person with minimal conflict risk. No notable weaknesses against the rubric anchors.

DimensionReasoningScore

Specificity

Lists multiple concrete components — 'operating system selection (EOS, Scaling Up, OKR-native, hybrid), accountability charts, scorecards, meeting pulse, issue resolution, and 90-day rocks' — giving comprehensive, specific coverage rather than vague language.

5 / 5

Completeness

Explicitly answers both 'what' (the meta-framework covering the listed components) and 'when' via a concrete 'Use when setting up company operations... or when user mentions...' trigger clause.

5 / 5

Trigger Term Quality

Comprehensive natural trigger terms users would say: 'EOS, Scaling Up, operating system, L10 meetings, rocks, scorecard, accountability chart, or quarterly planning', including synonyms and the specific framework names.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (company operating systems) with distinctive triggers like 'L10 meetings', 'rocks', and 'accountability chart' that are unlikely to fire for unrelated skills.

5 / 5

Total

20

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
alirezarezvani/claude-skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.