CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

saas-metrics-coach

Analyze SaaS growth, retention, efficiency, unit economics, runway, and reporting quality from supplied data.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./resources/bundled-skills/saas-metrics-coach/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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, token-efficient overview with a clear workflow and explicit completion gates, appropriately sized for a skill with no bundle files. Its weakness is actionability: it names the right analytical operations but delegates the actual formulas and specifics rather than providing them.

Suggestions

Add the key formulas explicitly (e.g., NRR, gross churn, CAC payback, net burn / runway months) or point to a reference file containing them, so 'transparent formulas' is specified rather than delegated.

Add a feedback loop for reconciliation failures, e.g., 'If totals do not reconcile, re-check data grain and churn definition before proceeding.'

Remove the '## Purpose' section that duplicates the frontmatter description verbatim to recover tokens.

DimensionReasoningScore

Conciseness

The body is lean with no concept-teaching padding, but the '## Purpose' section repeats the frontmatter description verbatim ('Analyze SaaS growth, retention, efficiency, unit economics, runway, and reporting quality from supplied data.') and the copyright line adds nothing for Claude — minor instances that could be trimmed. Better than 3 because there is no unnecessary explanation; short of 5 because of the verbatim duplication.

4 / 5

Actionability

No concrete formulas, commands, or example calculations are provided anywhere: 'Calculate retention, growth, efficiency, and runway with transparent formulas' delegates the formulas rather than specifying any (no NRR, CAC payback, burn multiple, or Rule of 40 definitions), and 'Prioritize actions by likely economic impact and confidence' is abstract. Better than 2 because the workflow steps and completion gates are specific and sequenced rather than high-level hints.

3 / 5

Workflow Clarity

A clear 5-step sequence (clarify, reconcile, calculate, segment, prioritize) with explicit validation checkpoints in 'Completion gates' ('Reconcile totals back to source data', 'State every formula and denominator'). Not 5 because there is no validate-fix-retry feedback loop (e.g., what to do when totals do not reconcile); better than 3 because checkpoints are explicit rather than implicit.

4 / 5

Progressive Disclosure

The body is under 50 lines, needs no external references, and is organized into well-labeled sections (Purpose, Tool routing, Workflow, Completion gates, Boundaries, Delivery), which the rubric guideline says earns a 5 for simple skills with well-organized sections.

5 / 5

Total

16

/

20

Passed

Description

66%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 concise, third-person description that is specific about the SaaS analysis domain, with good natural keyword coverage. Its main weakness is the missing 'when to use' trigger guidance, which caps completeness, and the absence of common synonyms like churn, ARR/MRR, CAC, and LTV.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user supplies SaaS/subscription revenue data and asks for growth, retention, churn, unit economics, or runway analysis.'

Include common synonyms users actually say — churn, ARR/MRR, NRR, CAC, LTV, burn rate, cohort analysis — to strengthen trigger term coverage.

Distinguish deliverables (e.g., reconciliation waterfalls, cohort tables, benchmark comparisons) to reduce overlap risk with generic data-analysis or charting skills.

DimensionReasoningScore

Specificity

The description names the domain plus six concrete analysis areas ("SaaS growth, retention, efficiency, unit economics, runway, and reporting quality from supplied data"), giving several specific capabilities with only minor gaps. It falls short of 5 because a single generic verb 'Analyze' carries all of them rather than multiple distinct concrete actions, and clear of 3 because coverage goes well beyond 1-2 actions.

4 / 5

Completeness

The 'what' is clear (analyze SaaS growth, retention, efficiency, unit economics, runway, reporting quality), but there is no 'Use when...' clause or any equivalent explicit trigger guidance, which the rubric guidelines cap at 3.

3 / 5

Trigger Term Quality

Natural terms a user would say are present ("SaaS", "growth", "retention", "unit economics", "runway"), matching 'good keyword coverage; a few natural terms missing'. It is not 5 because common synonyms users actually use — churn, ARR/MRR, CAC, LTV, burn rate, cohort — are absent.

4 / 5

Distinctiveness Conflict Risk

The SaaS-metrics vocabulary carves a mostly distinct niche with domain-specific triggers, but 'from supplied data' combined with general growth/efficiency analysis leaves minor overlap risk with generic data-analysis or charting skills. It is more distinct than score 3 ('could still overlap with similar skills') but lacks the fully distinct trigger phrase set of score 5.

4 / 5

Total

15

/

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

KunAgent/Kun

Path

resources/bundled-skills/saas-metrics-coach/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.