CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

saas-health

Calculate SaaS health metrics (ARR, MRR, churn, CAC, LTV, NRR) and benchmark against industry standards. Usage: /saas-health <metrics|quick-ratio|simulate> [options]

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

82%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 command skill with concrete usage examples and clearly signaled references to purpose-built scripts. The main gaps are interface consistency — examples use flags absent from the Usage spec and no script invocation syntax is given — and referenced file paths that do not resolve within the skill bundle itself.

Suggestions

Document the flags used in examples (--new-customers, --sm-spend, --contraction) in the Usage block, or remove them from the examples, so the accepted interface is unambiguous.

Add a one-line invocation example per subcommand showing how the CLI flags map to the underlying script (e.g. 'python scripts/metrics_calculator.py --mrr 80000 --customers 200 --churned 3').

Make referenced script and SKILL.md paths resolve within the skill bundle (e.g. scripts/metrics_calculator.py relative to the skill directory) instead of repo-absolute paths.

DimensionReasoningScore

Conciseness

The ~37-line body is lean and assumes Claude's competence: no concept explanations, no padding, and every section (Usage, Examples, Scripts, Skill Reference, Related Commands) earns its place. This matches the anchor 'Lean and efficient; assumes Claude's competence; every token earns its place' — anchor 4 would require over-explanation to trim, which is absent.

5 / 5

Actionability

Concrete, copy-paste-ready commands with real values ('/saas-health metrics --mrr 80000 --customers 200 --churned 3 ...') cover the common cases. However, the examples use flags (--new-customers, --sm-spend, --contraction) that are not documented in the Usage spec, and no script invocation syntax is shown — minor gaps rather than the missing key details of anchor 3, so anchor 4 fits best.

4 / 5

Workflow Clarity

The subcommand-to-script mapping is unambiguous (metrics→metrics_calculator.py, quick-ratio→quick_ratio_calculator.py, simulate→unit_economics_simulator.py) and operations are read-only calculations, so no validation cap applies. It falls short of anchor 5 because the mapping from CLI flags to script arguments is never stated, leaving a minor execution gap characteristic of anchor 4.

4 / 5

Progressive Disclosure

The body is a concise overview with well-signaled, one-level-deep references, each script annotated with its purpose ('Core SaaS metrics (ARR, MRR, churn, CAC, LTV, NRR, payback)'). However, the referenced paths (finance/skills/saas-metrics-coach/scripts/*.py and the referenced SKILL.md) do not exist in this skill's bundle — they are repo-relative rather than bundle-relative — an organization gap that keeps it at anchor 4 rather than 5.

4 / 5

Total

17

/

20

Passed

Description

75%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, concise, third-person description with excellent specificity and a distinct SaaS-metrics niche. Its main weakness is the absent 'Use when...' trigger clause, which caps completeness, and keyword coverage that omits common synonyms like retention or unit economics.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks about SaaS metrics, subscription revenue, churn, retention, or unit economics.'

Include natural synonyms and variations users say (retention, revenue growth, unit economics, quick ratio) alongside the metric acronyms to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description lists concrete actions ('Calculate SaaS health metrics (ARR, MRR, churn, CAC, LTV, NRR) and benchmark against industry standards') with a comprehensive enumeration of the canonical SaaS health metrics, plus three named subcommands. It uses third-person voice and matches the anchor for multiple specific concrete actions with comprehensive coverage; anchor 4 would apply only if metric coverage had gaps, which it does not.

5 / 5

Completeness

The 'what' is clear and specific (calculate and benchmark SaaS health metrics), but there is no 'Use when...' clause or equivalent explicit trigger guidance — only a 'Usage:' syntax line. Per the judging guideline, a missing 'Use when' clause caps completeness at 3, matching the anchor 'clear what but when missing or only weakly implied'.

3 / 5

Trigger Term Quality

Natural terms users would say are present: 'SaaS', 'churn', 'MRR', 'ARR', 'CAC', 'LTV', 'NRR', 'benchmark'. However, common variations and synonyms ('retention', 'revenue', 'growth efficiency', 'unit economics') are missing and no natural trigger phrases like 'Use when' appear, so it sits between anchor 4 (good coverage, a few natural terms missing) and anchor 5 (comprehensive synonyms), closer to 4.

4 / 5

Distinctiveness Conflict Risk

'SaaS health metrics (ARR, MRR, churn, CAC, LTV, NRR)' carves out a clear niche with distinct, domain-specific trigger terms (the metric acronyms), giving minimal conflict risk with generic skills. Anchor 4 would require noted overlap with a closely related skill, which the description itself does not exhibit.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

alirezarezvani/claude-skills

Path

.gemini/skills/saas-health/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.