CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

monetization-strategy

Brainstorm 3-5 monetization strategies with audience fit, risks, and validation experiments. Use when exploring revenue models, evaluating pricing strategies, or deciding how to monetize a product.

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 ./pm-product-strategy/skills/monetization-strategy/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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 delivers actionable, well-sequenced brainstorming guidance with a clear output format, but it is noticeably verbose: the framework, output process, and strategic considerations restate the same components, and the example catalog plus notes explain concepts Claude already knows. Splitting reference material out and de-duplicating the workflow would materially improve it.

Suggestions

Merge the Monetization Framework, Output Process, and Strategic Considerations sections into a single workflow — they currently repeat the same per-strategy components (fit, risks, unit economics, competitive position, experiment) three times.

Delete the redundant Metadata section (it duplicates the frontmatter) and cut the Notes section plus the mechanics of well-known models (freemium, subscription, usage-based) from Example Monetization Strategies, keeping only the How/Fit/Risks/Experiment output template.

Move the example strategy catalog to a references/ file (e.g., references/strategy-catalog.md) linked from SKILL.md so the main file stays a lean overview.

DimensionReasoningScore

Conciseness

The Metadata section duplicates the frontmatter; the Monetization Framework bullets, Output Process steps, and Strategic Considerations repeat the same per-strategy components three times; and the Example Strategies and Notes sections restate well-known models and generic advice Claude already knows — several padded sections, matching the anchor for noticeable verbosity rather than just minor tightening.

2 / 5

Actionability

Concrete, executable guidance for an instruction-only skill: enumerated validation methods ("survey, landing page, pilot, freemium, waitlist"), explicit prioritization criteria, and defined outputs ("Recommend 1-2 strategies to test first"). Some framework bullets are guiding questions rather than instructions, keeping it short of fully copy-paste-ready specificity.

4 / 5

Workflow Clarity

The Output Process gives a clear 6-step sequence from brainstorming through prioritization to a testing roadmap with success criteria, and decision criteria are specified per experiment. No explicit validation checkpoints exist, but they are largely inapplicable to a non-destructive brainstorming task, so this is a minor gap.

4 / 5

Progressive Disclosure

A single 145-line file (beyond the under-50-line simple-skill exception) with a 43-line example catalog and duplicated framework detail inlined; the only external pointer is one "Further Reading" link. Structure via headers is real, but content that could live in a separate reference file is inline.

3 / 5

Total

13

/

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: it states concrete deliverables, includes an explicit and specific "Use when..." clause with natural trigger phrases, and occupies a distinct niche. The only weaknesses are a few missing natural synonyms (e.g., "make money", "business model") and slightly soft action verbs.

DimensionReasoningScore

Specificity

"Brainstorm 3-5 monetization strategies with audience fit, risks, and validation experiments" lists several concrete deliverables (strategies with a count, fit analysis, risks, experiments), but the verbs are softer than a full action list and it omits the prioritization/recommendation work the body covers — minor gaps rather than comprehensive coverage.

4 / 5

Completeness

It clearly answers both "what" ("Brainstorm 3-5 monetization strategies with audience fit, risks, and validation experiments") and "when" with an explicit "Use when..." clause containing concrete trigger phrases, matching the top anchor's pattern.

5 / 5

Trigger Term Quality

"exploring revenue models, evaluating pricing strategies, or deciding how to monetize" provides good natural keyword coverage, but misses common synonyms users would say such as "make money", "business model", or "pricing model".

4 / 5

Distinctiveness Conflict Risk

Terms like "monetization", "pricing strategies", and "revenue models" carve a clear niche with distinct triggers and minimal overlap risk with unrelated skill domains.

5 / 5

Total

18

/

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/monetization-strategy/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.