saas-revenue-growth-metrics

Calculate SaaS revenue, retention, and growth metrics. Use when diagnosing momentum, churn, expansion, or product-market-fit signals.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/saas-revenue-growth-metrics/SKILL.md

Quality

Content

63%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 thorough, well-sequenced metrics reference with strong worked examples and a validation checklist, undermined by redundancy between the Key Concepts and Application sections and by dangling references to bundle files that are absent. Actionability and workflow clarity are solid; conciseness and progressive disclosure are the weak points.

Suggestions

Collapse the duplicated metric coverage: keep formulas/benchmarks in Key Concepts and worked examples/quality checks in Application, or merge each metric into a single entry instead of restating it twice.

Remove or trim the 'Why PMs care' rationale blocks and basic definitions (e.g. what 'Revenue' is) that Claude already knows, keeping only domain-specific benchmarks and formulas.

Either ship the referenced `template.md` and `examples/` files or remove the inline pointers to them, so progressive-disclosure references resolve to real bundle content.

Dimension	Reasoning	Score
Conciseness	The body explains concepts Claude already knows (e.g. 'Revenue — Total money earned from selling products/services before expenses') and duplicates each metric across the Key Concepts and Application sections, plus recurring 'Why PMs care' rationale blocks; it is mostly useful reference material but could be tightened noticeably.	3 / 5
Actionability	Concrete formulas and fully worked numeric examples (MRR build to ARR=$6.6M, NRR=108%, Quick Ratio=3.5, cohort tables) are copy-paste usable, but the body points to `template.md` and an `examples/` folder that are not present in the bundle, leaving minor gaps.	4 / 5
Workflow Clarity	A clear four-step sequence (Revenue → Retention → Trend analysis → Quality Checks) with per-metric quality checks and a final ✅ validation checklist, though there is no validate→fix→retry feedback loop since the task is analytical rather than destructive.	4 / 5
Progressive Disclosure	Section headers (Purpose, Input, Key Concepts, Application, Examples, Pitfalls, References) give real structure, but everything is inlined into one ~625-line SKILL.md with no bundle files, and inline references to `template.md` / `examples/` point to files that do not exist.	3 / 5
	Total	14 / 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 cleanly pairs a concrete 'what' with an explicit 'Use when' trigger clause using natural PM terminology. It is comprehensive on completeness with only minor gaps in action enumeration and synonym coverage.

Dimension	Reasoning	Score
Specificity	Phrases 'Calculate SaaS revenue, retention, and growth metrics' name the domain and several concrete metric categories, but rely on a single verb ('Calculate') rather than enumerating multiple distinct actions, so it sits just below the comprehensive-coverage anchor.	4 / 5
Completeness	It explicitly states what ('Calculate SaaS revenue, retention, and growth metrics') and when via a concrete 'Use when diagnosing momentum, churn, expansion, or product-market-fit signals' trigger clause, matching the explicit what+when anchor.	5 / 5
Trigger Term Quality	'diagnosing momentum, churn, expansion, or product-market-fit signals' supplies natural PM vocabulary a user would actually say, though common synonyms like MRR/ARR/NRR are absent, keeping it short of comprehensive.	4 / 5
Distinctiveness Conflict Risk	'SaaS revenue, retention, and growth metrics' carves a clear niche with distinct PMF/churn triggers, but there is minor overlap risk with sibling finance skills (e.g. saas-economics-efficiency-metrics) referenced in the body.	4 / 5
	Total	17 / 20 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (643 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: deanpeters/Product-Manager-Skills
Path: skills/saas-revenue-growth-metrics/SKILL.md
Commit: a03af68

Reviewed: 11 days ago

Table of Contents

Discovery Implementation Validation

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.