CtrlK
BlogDocsLog inGet started
Tessl Logo

saas-metrics-coach

SaaS financial health advisor. Use when a user shares revenue or customer numbers, or mentions ARR, MRR, churn, LTV, CAC, NRR, or asks how their SaaS business is doing.

68

Quality

83%

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

The canonical home for this skill is saas-metrics-coach in alirezarezvani/claude-skills

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 well-structured, highly actionable advisory skill with a clear five-step workflow and concrete CLI examples. It assumes Claude's intelligence and avoids concept re-explanation; its main gaps are a missing explicit verification step for computed metrics and referenced bundle files that are not present in the bundle.

Suggestions

Add an explicit validation checkpoint in Step 2 (e.g. "Verify each computed metric against the formulas.md definitions before benchmarking; re-check any value that looks implausible").

Ship the referenced files (references/formulas.md, references/benchmarks.md, assets/input-template.md, scripts/*.py) in the bundle so the signaled references are actually navigable, or inline the formula fallback so the skill is self-contained.

Consider moving the full output template and the per-script CLI reference into a reference file, keeping SKILL.md as a lean overview with a quick-start example.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence (it never defines what churn, LTV, or CAC are), but the three full CLI example blocks, two worked examples, and the complete output template are heavier than a lean SKILL.md needs, leaving minor trimmable instances that keep it off the 5 anchor.

4 / 5

Actionability

Guidance is copy-paste ready with real flags (e.g. "python scripts/metrics_calculator.py --mrr 50000 --customers 100 --churned 5 --json"), an explicit formula fallback, a full output template, and worked examples covering partial-data and critical cases, matching the fully-executable top anchor.

5 / 5

Workflow Clarity

The five numbered steps (Collect Inputs → Calculate → Benchmark → Prioritize → Output) form a clear sequence with soft checkpoints (flag missing data, confirm segment before scoring, cap priorities), but there is no explicit verification step for the computed metrics; since the skill is read-only analysis rather than destructive/batch, the 3-cap does not apply.

4 / 5

Progressive Disclosure

Structure is good with clearly signaled one-level-deep references (a "Reference Files" list describes formulas.md, benchmarks.md, input-template.md, and the three scripts), but the full output template and all CLI docs are inlined and none of the referenced bundle files actually exist in the bundle, so navigation would dead-end — minor gaps that keep it off the 5 anchor.

4 / 5

Total

17

/

20

Passed

Description

85%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 with excellent trigger coverage, clear what/when completeness, and a distinct SaaS-metrics niche. Its only weakness is specificity: it leads with a role label ("advisor") instead of concrete action verbs.

Suggestions

Replace the role label with concrete action verbs, e.g. "Calculates SaaS health metrics (ARR, MRR, churn, LTV, CAC, NRR), benchmarks them by segment/stage, and prioritizes actions."

Lead with the action before the trigger clause so the skill's behavior is explicit, not just its role.

DimensionReasoningScore

Specificity

It names the domain clearly ("SaaS financial health advisor") but states a role label rather than enumerating concrete actions like "calculates, benchmarks, and recommends"; no action verbs describe what the skill does, matching the 'names the domain but actions are minimal' anchor rather than the 3 anchor which requires 1-2 concrete actions.

2 / 5

Completeness

It explicitly answers both what ("SaaS financial health advisor") and when ("Use when a user shares revenue or customer numbers, or mentions ARR, MRR, churn, LTV, CAC, NRR, or asks how their SaaS business is doing") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Phrases like "shares revenue or customer numbers", "ARR, MRR, churn, LTV, CAC, NRR", and "asks how their SaaS business is doing" are exactly the natural terms a SaaS founder would say, with comprehensive acronym coverage and a plain-language synonym.

5 / 5

Distinctiveness Conflict Risk

The SaaS-specific metric acronyms (ARR, MRR, NRR, LTV, CAC, churn) carve a clear niche with distinct triggers and minimal overlap risk against generic financial-analysis skills.

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 20 missing

Warning

Total

15

/

16

Passed

Repository
alirezarezvani/claude-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.