CtrlK
BlogDocsLog inGet started
Tessl Logo

feature-investment-advisor

Evaluate feature investments using revenue impact, cost structure, ROI, and strategy. Use when deciding whether a feature deserves investment.

64

Quality

77%

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 ./skills/feature-investment-advisor/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 highly actionable, well-sequenced advisory skill whose body is dragged down by length and structure: verbatim redundancy, inlined content that belongs in reference files, and a dangling examples/ pointer.

Suggestions

Remove the verbatim repeat of the frontmatter intent in the Purpose section and trim the Anti-Patterns list, which restates points already covered by the 10 Common Pitfalls.

Split the worked examples and the Common Pitfalls catalog into separate files under references/ (e.g. references/examples.md, references/pitfalls.md) and link to them from the body, reducing SKILL.md to an overview.

Either create the examples/ folder referenced on line 394 or remove the dangling "See examples/ folder" pointer so navigation is not broken.

DimensionReasoningScore

Conciseness

Mostly efficient but padded in places: the frontmatter intent is repeated verbatim in the Purpose section, and the Anti-Patterns plus several of the 10 Common Pitfalls restate concepts and each other rather than adding new actionable signal.

3 / 5

Actionability

Fully actionable for an instruction-only skill: concrete formulas (e.g. "LTV Impact = Increase in Customer Lifetime × Customer Base × ARPU × Margin"), enumerated adaptive options, fill-in recommendation templates, and three fully worked numerical examples cover the common cases.

5 / 5

Workflow Clarity

A clearly sequenced Step 0→5 flow with explicit adaptive branching and built-in flags (e.g. the margin-dilution warnings in Step 2), but validation checkpoints between steps are implicit rather than spelled out.

4 / 5

Progressive Disclosure

Section headers are clear, but the ~650-line file is monolithic — worked examples, the 10-pitfall catalog, and full recommendation templates are inlined rather than split out, and the "See examples/ folder" reference points to a folder that does not exist.

3 / 5

Total

15

/

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, third-person description that pairs a concrete multi-dimensional "what" with an explicit "Use when" trigger. It is specific and complete, with only minor gaps in action-verb coverage and natural-trigger synonyms.

DimensionReasoningScore

Specificity

Lists several concrete analytical dimensions — "revenue impact, cost structure, ROI, and strategy" — but the action is essentially a single "evaluate" verb and it omits the build/don't-build recommendation output, leaving a minor coverage gap.

4 / 5

Completeness

It explicitly answers both what ("Evaluate feature investments using revenue impact, cost structure, ROI, and strategy") and when ("Use when deciding whether a feature deserves investment") with a concrete trigger phrase.

5 / 5

Trigger Term Quality

The clause "Use when deciding whether a feature deserves investment" is a natural trigger a PM might voice, and "ROI"/"feature investments" add keyword coverage, though common phrasings like "should we build" or "prioritize this feature" are missing.

4 / 5

Distinctiveness Conflict Risk

The financial-investment lens is a clear niche with distinct triggers, but the skill's own references show closely related finance/prioritization skills (RICE, pricing/ROI advisors) creating minor overlap risk.

4 / 5

Total

17

/

20

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (654 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

13

/

16

Passed

Repository
deanpeters/Product-Manager-Skills
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.