CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

porters-five-forces

Perform Porter's Five Forces analysis — competitive rivalry, supplier power, buyer power, threat of substitutes, and threat of new entrants. Use when analyzing industry dynamics, assessing competitive forces, or evaluating market attractiveness.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./pm-product-strategy/skills/porters-five-forces/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

48%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.

The skill body is well-organized and provides a usable analysis process, but the bulk of it re-explains a framework Claude already knows, making it token-inefficient. The output process is concrete but lacks an example deliverable, and the single-file structure inlines reference-grade material.

Suggestions

Strip the 'High/Low When' bullet lists for each force down to a few non-obvious indicators (or move them to a references/ file), since Claude already knows the standard Five Forces conditions — this would recover most of the ~150 lines of framework restatement.

Add a short example output or template (e.g., a filled-in force rating table with trend, key players, and profitability implications) so the deliverable format is unambiguous.

Include guidance on what input is minimally required versus optional, and how to proceed when the user supplies only a partial industry definition, to make the 'Input Requirements' section actionable rather than declarative.

DimensionReasoningScore

Conciseness

Roughly 150 of the ~210 lines restate textbook Five Forces conditions ('Many competitors of similar size and strength', 'Few suppliers or concentrated supplier base') that Claude already knows. The content is dense bullet lists rather than padded prose, so it is above anchor 1, but the majority of the body is unnecessary explanation — matching anchor 2.

2 / 5

Actionability

The Output Process gives concrete steps ('Assess each of the five forces (High, Medium, Low)', 'Prioritize the 2-3 forces most critical to your strategy') but provides no example output or template showing what the finished analysis looks like. As an instruction-only skill this lands at anchor 3 — some concrete guidance with key details missing.

3 / 5

Workflow Clarity

A clear numbered 7-step Output Process with an embedded attractiveness heuristic ('High rivalry + strong forces = less attractive'). This is a non-destructive analytical skill so validation caps do not apply, but there are no verification or feedback steps that would warrant anchor 5.

4 / 5

Progressive Disclosure

No bundle files exist and the single SKILL.md inlines ~150 lines of force-by-force condition lists that could live in a reference file, with the only external pointer being a URL under 'Further Reading'. Sections are well-organized, matching anchor 3 rather than 2.

3 / 5

Total

12

/

20

Passed

Description

83%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 description that names the framework, enumerates all five forces, and provides an explicit 'Use when' clause with natural trigger phrases. Its only weaknesses are single-action framing and slightly incomplete synonym coverage.

DimensionReasoningScore

Specificity

The description explicitly enumerates all five forces ('competitive rivalry, supplier power, buyer power, threat of substitutes, and threat of new entrants'), giving specific coverage of the domain, but the action itself is a single one ('Perform Porter's Five Forces analysis') without mentioning outputs like force ratings or strategic recommendations.

4 / 5

Completeness

Clearly answers both 'what' (performs a Five Forces analysis with the five forces named) and 'when' ('Use when analyzing industry dynamics, assessing competitive forces, or evaluating market attractiveness') with concrete trigger phrases, matching the anchor-5 example pattern.

5 / 5

Trigger Term Quality

Includes natural phrases users would say — 'Porter's Five Forces', 'analyzing industry dynamics', 'assessing competitive forces', 'evaluating market attractiveness' — but misses common variations like 'industry analysis', 'competitive analysis', or 'market structure'.

4 / 5

Distinctiveness Conflict Risk

Porter's Five Forces is a distinctly named framework with clear triggers, but generic phrases like 'evaluating market attractiveness' create minor overlap risk with closely related strategy skills (e.g., SWOT, PESTLE).

4 / 5

Total

17

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

phuryn/pm-skills

Path

pm-product-strategy/skills/porters-five-forces/SKILL.md

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.