7-powers-analysis

Analyze a business, product, or feature using Hamilton Helmer's 7 Powers framework to assess competitive advantage and strategic durability. Use when the user asks about competitive moats, strategic positioning, power analysis, defensibility, competitive advantage, or "7 Powers".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

87%

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

A concise, highly actionable analytical skill body that uses progressive disclosure effectively by offloading detailed Power definitions to a real one-level reference. The one gap is workflow clarity: the analysis workflow lacks an explicit validation/verification step for its output.

Suggestions

Add an explicit validation step to the workflow (e.g., step 6: "Verify each Moderate/Strong Power rating against concrete evidence before finalizing"), turning the evidence requirement currently buried in the output template into a workflow checkpoint.

Add a brief self-check or feedback loop after step 3 (e.g., "If a Power is rated Strong but no concrete evidence comes to mind, downgrade the rating or mark it for user confirmation").

Consider folding the per-Power Present?/Strength/Durability checklist into the workflow steps themselves so the validation structure is visible in the sequence rather than only in the output template.

Dimension	Reasoning	Score
Conciseness	The body is lean: it delegates detailed Power definitions, attributes, and examples to framework.md rather than re-explaining them, and avoids padding with concepts Claude already knows; every section (workflow, template, example, adapting guidance) earns its place.	3 / 3
Actionability	It provides a concrete 5-step workflow, defined Strength (None–Strong) and Durability (Fragile–Durable) scales, a copy-paste output template, and a worked Figma example — specific, actionable guidance even without code.	3 / 3
Workflow Clarity	The 5 steps are clearly sequenced with an initial clarification checkpoint ("Ask the user if ambiguous") and a per-Power 3-dimension checklist, but there is no explicit validation/verification step for the analysis output, which the level-3 anchor requires; it clears level 2 (sequence present, validation implicit) but not 3.	2 / 3
Progressive Disclosure	The SKILL.md body is an overview with a single well-signaled, one-level-deep reference to references/framework.md (a real file that nests no further references), splitting detailed framework content appropriately from the overview.	3 / 3
	Total	11 / 12 Passed

Description

90%

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 well-crafted description with explicit what-and-when structure, strong natural trigger terms, and a clear distinct niche. The only minor weakness is that the capability statement uses a single action verb rather than enumerating multiple concrete actions.

Dimension	Reasoning	Score
Specificity	The description names the domain and purpose ("Analyze a business, product, or feature using Hamilton Helmer's 7 Powers framework to assess competitive advantage and strategic durability") but relies on a single verb rather than listing multiple distinct concrete actions, matching the level-2 anchor; it is not vague (not 1) and lacks a multi-action list (not 3).	2 / 3
Completeness	It explicitly states both what the skill does (analyze via the 7 Powers framework) and when to use it via an explicit "Use when..." trigger clause, satisfying the level-3 anchor for both what and when.	3 / 3
Trigger Term Quality	The "Use when" clause covers natural terms users would say — "competitive moats", "strategic positioning", "power analysis", "defensibility", "competitive advantage", and "7 Powers" — giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	The 7 Powers framework is a clear niche with distinct, framework-specific triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: amplitude/builder-skills
Commit: 22b0634

Reviewed: 3 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.