CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

identify-assumptions-new

Identify risky assumptions for a new product idea across 8 risk categories including Go-to-Market, Strategy, and Team. Use when evaluating startup risks, assessing a new product concept, or mapping assumptions for a new venture.

Quality

82%

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

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 lean, well-structured instruction skill: a clear three-step workflow, concrete question prompts across all eight risk categories, and clean section organization with no unnecessary bundle files. Remaining improvement is minor — a confidence-rating scale, an output template, and removing the duplicated citation and motivational filler.

DimensionReasoningScore

Conciseness

The body is mostly efficient — terse question prompts per category and a compact three-step instruction list. Minor trimmable padding remains: the Torres citation repeats between the intro and 'Domain Context', and 'Good teams assume at least three-quarters of their ideas won't perform as they hope' is motivational filler Claude doesn't need, matching anchor 4 rather than 5.

4 / 5

Actionability

For an instruction-only skill the guidance is concrete: three named perspectives with specific focus areas, eight categories each with explicit guiding questions, and a defined deliverable ('rate confidence and suggest a test', 'Save as markdown'). It falls short of anchor 5 because 'rate confidence' lacks any scale or criteria and no output template is provided.

4 / 5

Workflow Clarity

The sequence is clear and ordered — (1) think from three perspectives, (2) identify assumptions across 8 categories, (3) rate confidence and suggest tests — ending with an explicit output instruction. This is a non-destructive analytical task so the validation cap doesn't apply, but there are also no checkpoints (e.g. reviewing coverage across all 8 categories before writing), keeping it at anchor 4.

4 / 5

Progressive Disclosure

The body is 49 lines with well-organized sections (Context, Domain Context, Instructions, Further Reading) and no bundle files exist or are needed; the Further Reading links are clearly signaled external resources one level deep. Per the under-50-lines simple-skill guideline, this matches anchor 5.

5 / 5

Total

17

/

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 well-formed description with an explicit and concrete 'Use when' clause, natural trigger synonyms, and a clear statement of what the skill does. Its only notable gap is that it surfaces just one action (identify), omitting the rating and testing steps the body actually performs.

Suggestions

Add the downstream actions from the body to the 'what' clause, e.g. 'Identify risky assumptions for a new product idea across 8 risk categories... then rate each assumption's confidence and suggest a test' — this would raise specificity from one action to several.

Include one or two more natural trigger variants such as 'business idea' or 'validate a product idea' to broaden keyword coverage toward anchor 5.

DimensionReasoningScore

Specificity

The description names the domain ('risky assumptions for a new product idea') and one concrete action ('Identify'), backed by a specific 8-category framework with three named categories. It stays at anchor 3 rather than 4 because it lists only one action — steps like rating confidence and suggesting tests appear only in the body, not the description.

3 / 5

Completeness

It explicitly answers both questions: the 'what' ('Identify risky assumptions... across 8 risk categories including Go-to-Market, Strategy, and Team') and the 'when' with three concrete trigger phrases ('Use when evaluating startup risks, assessing a new product concept, or mapping assumptions for a new venture'). This matches the anchor-5 example structure exactly.

5 / 5

Trigger Term Quality

The 'Use when' clause supplies natural phrases users would say — 'evaluating startup risks', 'assessing a new product concept', 'mapping assumptions', 'new venture' — with good synonym coverage. A few natural variants (e.g. 'business idea', 'validate idea') are missing, matching anchor 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

The new-product assumption-mapping niche is mostly distinct with targeted triggers, though 'evaluating startup risks' has minor overlap potential with general business-strategy skills. Anchor 4 ('mostly distinct; minor overlap risk with closely related skills') is the best fit.

4 / 5

Total

16

/

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-discovery/skills/identify-assumptions-new/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.