CtrlK
BlogDocsLog inGet started
Tessl Logo

saas-revenue-growth-metrics

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

60

Quality

71%

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/saas-revenue-growth-metrics/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill is accurate and actionable with strong worked examples, but it is far too long and duplicates each metric across two sections, and it points to bundle files (template.md, examples/) that are missing. Splitting reference material into real files would substantially improve it.

Suggestions

Eliminate the metric-by-metric duplication: present each metric once with its formula, example, and quality checks rather than repeating formulas across Key Concepts and Application.

Create the referenced template.md and examples/ files (or remove the dangling references) so the inline 'Use the templates in template.md' and 'See examples/ folder' pointers resolve.

Move the 10 Common Pitfalls and the detailed Examples into separate reference files to slim SKILL.md into an overview.

DimensionReasoningScore

Conciseness

At ~620 lines the body is padded: each metric is defined twice (Key Concepts then Application with repeated formulas) and includes basic definitions Claude already knows ("Revenue — Total money earned from selling products/services before expenses").

1 / 3

Actionability

Provides complete formulas, worked numeric examples, and benchmark tables that are directly usable; as an instruction-only skill the absence of code is not penalized because the guidance is concrete and executable.

3 / 3

Workflow Clarity

Steps 1–4 are sequenced, but validation is a terminal pre-reporting checklist rather than interleaved checkpoints, with no validate-fix-retry feedback loop.

2 / 3

Progressive Disclosure

Sections are well-organized, but the full metric catalog, 10 pitfalls, and 3 examples are all inline content that should be split out, and the referenced template.md and examples/ files do not exist in the bundle.

2 / 3

Total

8

/

12

Passed

Description

92%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise, concrete, and includes an explicit 'Use when' trigger clause with strong natural-language terms. Its only real weakness is mild overlap with sibling finance-metrics skills in the diagnostic framing.

Suggestions

Sharpen the 'Use when' clause to distinguish from sibling skills (e.g., reference metric calculation specifically rather than 'diagnosing signals' that overlaps business-health-diagnostic).

Consider including one common acronym variation (MRR/NRR/churn rate) that users frequently say to broaden trigger coverage.

DimensionReasoningScore

Specificity

"Calculate SaaS revenue, retention, and growth metrics" names the SaaS domain and lists multiple concrete calculation actions, matching the multiple-specific-actions anchor.

3 / 3

Completeness

Explicitly answers both what ("Calculate SaaS revenue, retention, and growth metrics") and when ("Use when diagnosing momentum, churn, expansion, or product-market-fit signals"), mirroring the 3-anchor example.

3 / 3

Trigger Term Quality

Natural PM-language triggers — revenue, retention, growth, momentum, churn, expansion, product-market-fit — give good coverage of terms users would actually say.

3 / 3

Distinctiveness Conflict Risk

The SaaS revenue/retention niche is clear, but "diagnosing … signals" and shared metric vocabulary overlap with sibling skills like business-health-diagnostic, so it could still trigger for a similar skill.

2 / 3

Total

11

/

12

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.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
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.