saas-economics-efficiency-metrics

Evaluate SaaS unit economics and capital efficiency. Use when deciding whether the business can scale efficiently or needs correction.

Quality

55%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/saas-economics-efficiency-metrics/SKILL.md

Quality

Content

52%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 content is highly actionable with formulas, worked examples, and benchmarks, and the four-step workflow is clearly sequenced. Its weaknesses are verbosity from duplicating the metric catalog across two sections, and poor progressive disclosure: it is a monolith that references bundle files (template.md, examples/) that do not exist.

Suggestions

Collapse the duplicated metric definitions: keep formulas and benchmarks in one place (Key Concepts) and have Application reference them, or vice-versa, to remove the bulk of the verbosity.

Create the referenced `template.md` and `examples/` files and move the worked scenarios and calculation templates there, turning the body into an overview that links one level deep.

Move the 10 Common Pitfalls (or the per-metric catalog) into a separate reference file so the main SKILL.md stays a lean overview with signaled references.

Dimension	Reasoning	Score
Conciseness	The ~690-line body restates nearly every metric twice — formulas and benchmarks appear in both "Key Concepts" and again in "Application" — duplicating the entire catalog. It avoids explaining basic concepts Claude already knows, but the repeated restatement is noticeably verbose with several padded sections.	2 / 5
Actionability	Every metric has an explicit formula, a worked numeric example with real numbers (e.g. CAC = $500,000 / 100 = $5,000), benchmarks, and quality-check questions. It is mostly executable guidance for an instruction skill; a couple of metrics (Operating Leverage, Working Capital) lack fully worked numeric examples, keeping it just below fully copy-paste-ready.	4 / 5
Workflow Clarity	A clear 4-step sequence (Unit Economics -> Capital Efficiency -> Efficiency Ratios -> Segment/Channel analysis) with per-metric quality checks acting as checkpoints. It is a non-destructive analytical skill so the validation-cap does not apply, but there are no explicit validate-then-retry feedback loops, keeping it below 5.	4 / 5
Progressive Disclosure	No references/scripts/assets directories exist, yet the body points to non-existent files (`template.md` at line 187, `examples/` folder at line 508). The body is a monolithic ~690-line wall where the metric catalog, examples, and pitfalls clearly belong in separate files, matching the inlined-content anchor.	2 / 5
	Total	12 / 20 Passed

Description

58%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 clearly states a focused SaaS efficiency domain with an explicit Use-when clause, satisfying both what and when. Its main weakness is trigger coverage: the metric terms users actually say (CAC, LTV, burn, runway) are missing, and the when-phrase is broad enough to risk overlap with related finance skills.

Suggestions

Add concrete trigger terms users actually say, e.g. "Use when evaluating CAC, LTV, payback, burn, runway, magic number, or Rule of 40" to lift trigger_term_quality and distinctiveness.

List the specific actions the skill performs (calculate unit economics, assess capital efficiency, plan runway, compare segments) to move specificity from 3 toward 4-5.

Sharpen the when-clause with concrete decision scenarios (fundraising prep, board reporting, scale-vs-optimize calls) to reduce overlap with sibling revenue/health skills.

Dimension	Reasoning	Score
Specificity	"Evaluate SaaS unit economics and capital efficiency" names the domain and a couple of concrete actions (evaluate, decide), but does not enumerate several specific actions like calculate, analyze, or report. It fits the anchor that names domain + 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	It answers both what ("Evaluate SaaS unit economics and capital efficiency") and when ("Use when deciding whether the business can scale efficiently or needs correction"), but the when-clause is a single broad scenario rather than concrete trigger phrases. It is above the both-present-but-could-be-more-specific anchor, below the explicit-concrete-triggers anchor.	4 / 5
Trigger Term Quality	Natural terms like "SaaS unit economics", "capital efficiency", and "scale efficiently" appear, but the high-frequency metric synonyms users actually invoke (CAC, LTV, burn, runway, payback, Rule of 40) are absent. This matches the anchor with relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	The SaaS efficiency niche is fairly specific, but the broad trigger "scale efficiently or needs correction" risks overlap with sibling skills like saas-revenue-growth-metrics and business-health-diagnostic. It is somewhat specific yet could still overlap with closely related skills.	3 / 5
	Total	13 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (709 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
Path: skills/saas-economics-efficiency-metrics/SKILL.md
Commit: a03af68

Reviewed: 11 days ago

Table of Contents

Discovery Implementation Validation

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.