CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

porters-five-forces

Read an industry's structure through Porter's Five Forces with documented signals per rating, ending at the profit pool. Use when weighing market entry or when margins erode and nobody can say why.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

78%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-crafted analysis skill body: tight, highly actionable, with a clean sequenced workflow and a concrete output schema. Its main weakness is progressive disclosure — the body points to template and example files that are not present in the bundle, leaving the reader to navigate to files that do not resolve.

Suggestions

Ship the referenced bundle files (template.md, examples/sample.md, examples/sample-industrial.md) or remove the links so navigation does not dead-end.

Inline one short validate-fix-retry checkpoint in the Application steps rather than relying entirely on the autonomous-investigation protocol reference, so the workflow is self-contained.

Trim the editorial asides (e.g. "a rating without signals is vibes", "not a diagram for slide four") to tighten the body further without losing the substance.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (a one-line 1979 framing, no padding about what a 'force' is), but editorial flair like "a rating without signals is vibes" and "not a diagram for slide four" could be trimmed without losing guidance.

4 / 5

Actionability

For an instruction-only workflow skill it is fully actionable: a numbered procedure, a copy-paste output schema with per-field labels, explicit Final Step options, and a worked buyer-power example showing the exact signal-plus-label format.

5 / 5

Workflow Clarity

The sequence is clear — credit context → 3-bullet search-plan gate → rate forces → emit schema → 4-option close — with implicit validation via Fact/Inference/Assumption labels and the "how do you know?" test, but explicit validate-then-fix checkpoints are delegated to the referenced protocol rather than stated inline.

4 / 5

Progressive Disclosure

Structure and one-level-deep references (template.md, examples/sample.md, examples/sample-industrial.md) are clearly signaled, but none of the referenced bundle files exist on disk, so the promised navigation leads nowhere and the inlined schema/examples carry load that the missing files were meant to share.

3 / 5

Total

16

/

20

Passed

Description

87%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: third-person voice, explicit what-and-when, and a distinctive named framework. It falls just short of perfect only on specificity and trigger-term breadth, where a touch more enumerated action and a couple more synonyms would round it out.

DimensionReasoningScore

Specificity

"Read an industry's structure through Porter's Five Forces with documented signals per rating, ending at the profit pool" names the domain plus several concrete actions (rate forces, attach signals, close on profit pool), but the actions stay one level of abstraction above the score-5 anchor's enumerated verbs.

4 / 5

Completeness

It explicitly answers both what ("Read an industry's structure through Porter's Five Forces with documented signals per rating, ending at the profit pool") and when ("Use when weighing market entry or when margins erode and nobody can say why") with concrete trigger phrases.

5 / 5

Trigger Term Quality

"Use when weighing market entry or when margins erode" surfaces natural strategic phrases a user would say, but coverage stops at two triggers and omits common synonyms like "competitive analysis" or "should we enter this market."

4 / 5

Distinctiveness Conflict Risk

"Porter's Five Forces" is a named, well-bounded framework with distinct triggers (market entry, margin erosion), giving it a clear niche and minimal overlap with adjacent skills like swot or landscape scan.

5 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 3 missing, 11 suspicious

Warning

Total

14

/

16

Passed

Repository

deanpeters/Product-Manager-Skills

Path

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.