high-output-management

Apply Andy Grove's High Output Management principles to diagnose team productivity, design processes, and make management decisions. Use for team structure, meeting design, decision-making, performance management, and operational leverage.

1.06x

Quality

—

Does it follow best practices?

Impact

95%

1.06x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

77%

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

The body is well-structured and highly actionable with a clear six-step workflow and a real reference file, but it duplicates much of the framework detail already in framework.md, hurting token efficiency and progressive disclosure. Tightening the inline content to point at the reference would lift both dimensions.

Suggestions

Trim the inline leverage taxonomy, production principles, meeting taxonomy, and TRM table in the prompt template, replacing them with brief pointers to framework.md to avoid duplicating the reference and improve conciseness.

Keep only the diagnostic questions and the numbered recommendation structure inline, since those are the executable parts Claude must act on every invocation.

Move the worked 'all-hands' example and the Tips section's explanatory prose into framework.md if more than one illustrative example is needed, keeping the SKILL.md body a lean overview.

Dimension	Reasoning	Score
Conciseness	The body re-states the leverage taxonomy, production principles, meeting taxonomy, and TRM table that already live in framework.md, and includes some generic explanation Claude could infer. Not a 3 because the duplicated detail could be tightened or delegated to the reference; not a 1 because the prose is largely relevant rather than padded with basic concepts.	2 / 3
Actionability	Concrete diagnostic questions, a TRM table, a numbered recommendation structure, and a specific worked example ("Switch the Monday all-hands from status updates to a 15-minute operational review of three leading indicators...") give copy-ready guidance. Not a 2 because it is specific and complete, not pseudocode-like or abstract.	3 / 3
Workflow Clarity	Sections 1–6 sequence the analysis clearly (Diagnose leverage → Production principles → Decisions → Meetings → TRM → Recommendations). Not a 2 because the sequence is explicit and ordered; destructive-operation validation checkpoints do not apply to this advisory skill.	3 / 3
Progressive Disclosure	framework.md is clearly signaled and one level deep, but substantial framework content that belongs in the reference is duplicated inline in the prompt template. Not a 3 because content that should be separate is inlined; not a 1 because the reference exists and navigation is clear rather than nested multiple levels deep.	2 / 3
	Total	10 / 12 Passed

Description

100%

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

The description is concise, uses third-person voice, and clearly answers both what the skill does and when to use it with concrete, natural trigger terms. It is distinctive and unlikely to conflict with other skills.

Dimension	Reasoning	Score
Specificity	"diagnose team productivity, design processes, and make management decisions" lists multiple concrete actions rather than a single domain, matching the score-3 anchor. It is not a 2 because it goes beyond naming a domain plus a few actions into a comprehensive action set.	3 / 3
Completeness	It explicitly states what it does ("diagnose... design... make management decisions") and when to use it via the equivalent "Use for team structure, meeting design..." clause. Not a 2 because the when is explicit, not merely implied.	3 / 3
Trigger Term Quality	"team structure, meeting design, decision-making, performance management, and operational leverage" are natural terms a manager would actually say when needing this skill. Not a 2 because coverage is broad and includes common variations rather than a single keyword.	3 / 3
Distinctiveness Conflict Risk	"Andy Grove's High Output Management" is a clearly named niche with distinct triggers unlikely to collide with other skills. Not a 2 because the framing is specific rather than a generic domain label.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: amplitude/builder-skills
Commit: 22b0634

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.