saas-economics-efficiency-metrics

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

Quality

70%

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

65%

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 concrete formulas and worked examples for every metric, but it is verbose due to heavy duplication between the Key Concepts and Application sections and ships broken references to template.md and examples/. Tightening redundancy and fixing or removing the phantom references would meaningfully improve it.

Suggestions

Collapse the duplicate Key Concepts and Application sections into one pass per metric, or move the detailed formulas/examples into a reference file the SKILL.md points to, to cut redundancy and respect the token budget.

Either add the missing template.md and examples/ bundle files or remove the references to them, since broken links currently undermine navigation.

Convert the "Quality checks" lists into explicit validation gates (e.g. "If LTV:CAC < 3:1, stop and optimize before scaling") to add the error-recovery feedback loop the rubric rewards.

Dimension	Reasoning	Score
Conciseness	The ~687-line body duplicates material: the Key Concepts section and the Application section both restate the same metrics, formulas, and benchmarks with "Why PMs care" prose, so it is mostly useful but padded with unnecessary repetition rather than lean.	2 / 3
Actionability	Concrete formulas, fully worked numeric examples (e.g. LTV = $500 × 36 = $18,000) and segment tables give copy-paste-ready calculation recipes, which for an instruction/metrics skill counts as fully executable guidance.	3 / 3
Workflow Clarity	A clear 4-step sequence exists with per-metric "Quality checks," but these are implicit prompts-to-consider rather than explicit pass/fail validation gates with error-recovery feedback loops, matching the anchor with steps present but checkpoints implicit.	2 / 3
Progressive Disclosure	The body is organized into sections but is largely monolithic, and it references bundle files (template.md, examples/) that do not exist, so navigation is broken rather than cleanly split into one-level-deep references.	2 / 3
	Total	9 / 12 Passed

Description

75%

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 cleanly answers both what the skill does and when to use it, with a clear, non-conflicting niche. It falls short on specificity and trigger-term coverage by relying on general phrasing rather than the concrete metric names users would actually say.

Suggestions

Add concrete metric names to the description (e.g. "Evaluate SaaS unit economics and capital efficiency—CAC, LTV, payback, burn, runway, Rule of 40, magic number") to lift specificity and trigger-term coverage.

Keep the existing "Use when..." clause but pair it with the natural trigger phrasing users say (e.g. "Use when reviewing CAC/LTV/payback, checking runway, or prepping a board efficiency review").

Avoid first/second person to preserve the third-person voice the rubric rewards.

Dimension	Reasoning	Score
Specificity	"Evaluate SaaS unit economics and capital efficiency" names the domain and a couple of actions but does not enumerate multiple specific concrete actions (e.g. CAC/LTV/runway), matching the anchor that names domain and some actions without being comprehensive.	2 / 3
Completeness	It states what ("Evaluate SaaS unit economics and capital efficiency") and an explicit when ("Use when deciding whether the business can scale efficiently or needs correction"), answering both what and when with an explicit trigger.	3 / 3
Trigger Term Quality	Natural terms like "SaaS unit economics" and "capital efficiency" appear, but common variations users actually say (CAC, LTV, payback, burn, runway, Rule of 40) are absent, so coverage is partial rather than strong.	2 / 3
Distinctiveness Conflict Risk	The SaaS unit-economics/capital-efficiency niche has distinct triggers unlikely to conflict with unrelated skills, matching the clear-niche anchor.	3 / 3
	Total	10 / 12 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 (707 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: 9971018

Reviewed: 3 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.