CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

opportunity-solution-tree

Build an Opportunity Solution Tree from outcomes to opportunities, solutions, and tests. Use when a stakeholder request needs problem framing before you decide what to build.

Quality

74%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/opportunity-solution-tree/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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 body is a well-sequenced, actionable facilitation script, but it is padded with concepts Claude already knows and undermined by references to bundle files (template.md, examples/sample.md) that do not exist.

Suggestions

Create the referenced bundle files (references/template.md and references/examples/sample.md) or remove the dangling references so navigation is not broken.

Move the inlined ~80-line output template into template.md and keep only a pointer in SKILL.md to reduce token weight.

Trim the 'What is an OST' / 'Why This Works' / 'Anti-Patterns' exposition to a few lines and remove the placeholder Dean's Work line.

DimensionReasoningScore

Conciseness

The facilitation scripts and output template earn their tokens, but the Key Concepts section re-explains Torres's OST framework Claude already knows and a leftover placeholder ("[If Dean has OST resources, link here]") adds slack.

3 / 5

Actionability

Concrete question scripts, enumerated options with rationales, example opportunities/solutions with hypotheses, and a scoring table give mostly executable guidance; actual opportunity/solution generation is delegated to the agent rather than scripted.

4 / 5

Workflow Clarity

A clear two-phase sequence (Step 0 context, Q1-Q3 generate, Q4-Q5 select POC, output) with per-question confirmations as checkpoints; no destructive or batch operation applies, so the level-3 cap is not triggered.

4 / 5

Progressive Disclosure

The body references template.md and examples/sample.md, but no references/ or assets/ bundle directories exist, so those pointers are broken; meanwhile the ~80-line output template is inlined rather than split into the referenced file.

2 / 5

Total

13

/

20

Passed

Description

78%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 clearly answers both what and when with a concrete, distinctive trigger. The only blemish is a second-person clause that costs a specificity point under the rubric's voice rule.

Suggestions

Rewrite "before you decide what to build" in third person (e.g., "before deciding what to build") to recover the specificity point lost to the voice penalty.

Add a natural synonym like "feature request" or "discovery" to the trigger clause to broaden keyword coverage toward level 5.

DimensionReasoningScore

Specificity

Names the OST domain and four concrete build stages ("from outcomes to opportunities, solutions, and tests") for a base of 4, but the second-person phrase "before you decide what to build" triggers the rubric's -1 voice penalty.

3 / 5

Completeness

Explicitly states what it does ("Build an Opportunity Solution Tree from outcomes to opportunities, solutions, and tests") and when to use it ("Use when a stakeholder request needs problem framing"), matching the level-5 anchor.

5 / 5

Trigger Term Quality

Natural PM phrases like "stakeholder request", "problem framing", and "what to build" are present and would be said in need, though common synonyms like "discovery" or "feature request" are missing.

4 / 5

Distinctiveness Conflict Risk

The named OST framework plus the specific "stakeholder request needs problem framing" trigger carves a clear niche with only minor overlap risk against sibling discovery skills like problem-statement.

4 / 5

Total

16

/

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: 1 suspicious

Warning

Total

14

/

16

Passed

Repository

deanpeters/Product-Manager-Skills

Path

skills/opportunity-solution-tree/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.