CtrlK
BlogDocsLog inGet started
Tessl Logo

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]

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 ./.gemini/skills/saas-health/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is concise and gives concrete, executable command examples with sensible external references, but it lacks input/output validation for financial modeling and does not document how to invoke the underlying scripts. Adding verification steps and script usage examples would raise the weaker dimensions.

Suggestions

Add validation/sanity-check steps (e.g., verify ARR ≈ 12×MRR, confirm churn and growth rates are consistent, reject negative inputs) for the metrics and simulate subcommands.

Document each script's invocation signature and which subcommand uses it, so the referenced tools are directly executable rather than just listed.

Show a brief expected-output example for one command so Claude can verify a correct result against a known benchmark.

DimensionReasoningScore

Conciseness

The ~30-line body is lean and assumes Claude's competence, providing usage syntax, concrete examples, and script pointers without padding or explaining basic SaaS concepts.

5 / 5

Actionability

Provides copy-pasteable command invocations with concrete numeric examples, but the referenced scripts lack invocation signatures or usage examples, leaving a minor gap in executable guidance.

4 / 5

Workflow Clarity

Subcommand branches are clear but there are no validation checkpoints or sanity checks for the financial calculations and 12-month projection, capping workflow clarity at 3 per the feedback-loops guidance.

3 / 5

Progressive Disclosure

Well-organized sections with clearly signaled one-level references to scripts and a sibling SKILL.md, though the referenced paths are external rather than local bundle files and scripts are not mapped to subcommands.

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

The description is specific and well-targeted to SaaS metrics with strong trigger vocabulary, but it omits an explicit 'when to use' trigger clause, relying on invocation syntax instead. Adding a 'Use when...' clause would lift completeness and reduce residual overlap ambiguity.

Suggestions

Add an explicit 'Use when...' trigger clause (e.g., 'Use when analyzing subscription revenue, retention, or unit economics for a SaaS business').

Include a couple of natural synonyms (subscription revenue, retention, unit economics) alongside the metric acronyms for broader trigger coverage.

Briefly distinguish the trigger from /financial-health (e.g., 'SaaS/subscription metrics' vs 'traditional financial ratios') to further reduce conflict risk.

DimensionReasoningScore

Specificity

Names the SaaS domain and lists multiple concrete actions (calculate, benchmark) plus enumerated metrics (ARR, MRR, churn, CAC, LTV, NRR) and three subcommands, with only minor coverage gaps.

4 / 5

Completeness

Clearly states what the skill does but provides only a Usage/invocation line rather than an explicit 'Use when...' trigger clause, so completeness is capped at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Includes the canonical metric vocabulary users actually say (ARR, MRR, churn, CAC, LTV, NRR, quick-ratio), with good but not exhaustive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The SaaS-specific metric framing carves a clear niche distinct from a sibling /financial-health command, with only minor overlap risk against generic finance skills.

4 / 5

Total

15

/

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

frontmatter_unknown_keys

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

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.