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".
86
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description with excellent trigger terms and completeness. It clearly identifies both what the skill does and when to use it, with a distinctive framework reference that minimizes conflict risk. The main weakness is that the 'what' portion could list more specific concrete actions beyond the single verb 'Analyze.'
Suggestions
Expand the capability description with more specific actions, e.g., 'Identify which of the 7 Powers apply, evaluate strength of each power, assess strategic durability, and recommend actions to build or strengthen competitive moats.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (competitive strategy analysis) and the framework (Hamilton Helmer's 7 Powers), but the core action is a single verb 'Analyze' rather than listing multiple concrete actions like 'identify power sources, evaluate defensibility, compare against competitors, recommend strategic moves.' | 2 / 3 |
Completeness | Clearly answers both 'what' (analyze a business/product/feature using Hamilton Helmer's 7 Powers framework to assess competitive advantage and strategic durability) and 'when' (explicit 'Use when' clause with multiple trigger scenarios). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'competitive moats', 'strategic positioning', 'power analysis', 'defensibility', 'competitive advantage', and '7 Powers' — these are all terms a user would naturally use when seeking this type of analysis. | 3 / 3 |
Distinctiveness Conflict Risk | The specificity of 'Hamilton Helmer's 7 Powers framework' creates a very clear niche that is unlikely to conflict with other strategy or analysis skills. The trigger terms like '7 Powers' and 'power analysis' are highly distinctive. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured analytical skill with a clear workflow, concrete output template, and a useful worked example. Its main strengths are actionability and workflow clarity — Claude knows exactly what to produce and in what order. Minor weaknesses include some verbosity in the inline output template and adaptation sections, and the inability to verify the referenced framework.md file.
Suggestions
Consider moving the full output template to a reference file (e.g., references/template.md) and keeping only a brief summary in SKILL.md to improve conciseness and progressive disclosure.
Ensure the referenced references/framework.md file exists in the bundle with detailed Power definitions, attributes, and examples to support the progressive disclosure pattern.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some unnecessary elaboration. The 'Adapting the Analysis' section and the output template, while useful, add bulk. The framework itself is well-known enough that some of the enumeration (listing all 7 Powers repeatedly) could be trimmed. However, it doesn't over-explain basic concepts. | 2 / 3 |
Actionability | The skill provides a concrete output template with a markdown table structure, specific assessment dimensions (Present/Strength/Durability), clear workflow steps, and a worked example (Figma). Claude can follow this to produce a complete, structured analysis without ambiguity. | 3 / 3 |
Workflow Clarity | The 5-step workflow is clearly sequenced and logical: clarify subject → scan all Powers → assess each → identify synergies → recommend actions. Since this is an analytical (non-destructive) task, validation checkpoints aren't critical, and the workflow is unambiguous. The adaptation variants for different contexts add useful decision guidance. | 3 / 3 |
Progressive Disclosure | The skill references [framework.md](references/framework.md) for detailed definitions, which is good progressive disclosure. However, no bundle files were provided, so we can't verify the reference exists. The output template is quite long and could potentially be in a separate reference file, and the 'Adapting the Analysis' section adds inline content that could be split out for a cleaner overview. | 2 / 3 |
Total | 10 / 12 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- amplitude/builder-skills
- Commit
221ffaa
- 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.