business-health-diagnostic

Diagnose SaaS business health across growth, retention, efficiency, and capital. Use when preparing a business review or prioritizing urgent fixes.

Quality

76%

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/business-health-diagnostic/SKILL.md

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A thorough, highly actionable diagnostic with excellent numeric benchmarks and a clearly sequenced, checkpointed workflow. Its main weakness is verbosity from four inline placeholder templates and a monolithic structure with a broken examples reference rather than genuine progressive disclosure.

Suggestions

Condense the four full output templates into a compact shared scorecard skeleton plus short per-pattern deltas, cutting the bulk of the placeholder-blank boilerplate.

Move the stage benchmarks and red-flag tables into a reference file (e.g. references/benchmarks.md) and link one level deep, so SKILL.md stays an overview.

Either create the referenced examples/ folder with the three mini-cases fully worked out, or remove the 'See examples/ folder' pointer to avoid a dead reference.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of basic-concept padding, but ~780 lines include four full placeholder-blank output templates (Pattern 1 alone ~100 lines) and a Purpose section that restates the frontmatter intent near-verbatim; these could be tightened substantially.	2 / 3
Actionability	Highly actionable with concrete numeric thresholds throughout (NRR >100%, LTV:CAC >3:1, Rule of 40 >40, runway <6 months), explicit per-step evaluation criteria, specific agent questions, and copy-ready scorecard templates — guidance an instruction-only skill should have.	3 / 3
Workflow Clarity	Steps 0–4 are clearly sequenced with an explicit evaluation checkpoint after each metric-gathering step (✅/⚠️/🚨 criteria), adaptive questioning, and a delegated facilitation source-of-truth; this is a diagnostic Q&A, so the destructive/batch validation cap does not apply.	3 / 3
Progressive Disclosure	Well-sectioned with clear headings, but the file is monolithic — the four full output patterns and benchmark tables that could live in a separate reference are inline — and the 'See examples/ folder' reference points to a non-existent directory with no actual bundle files present.	2 / 3
	Total	10 / 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.

A concise, well-structured description that cleanly answers both what and when with an explicit trigger. It is held back from the top band only by a single action verb and missing common trigger variations (board meeting, QBR, fundraising).

Suggestions

Add one or two more concrete action verbs (e.g., 'scores, benchmarks against stage peers, and prioritizes fixes') to lift specificity toward the 3-anchor.

Broaden trigger terms to include the real-world occasions named in the scenarios — 'board meeting', 'quarterly review (QBR)', 'fundraising prep' — so users phrase-match more naturally.

Dimension	Reasoning	Score
Specificity	Names the SaaS domain and four concrete analysis dimensions ("growth, retention, efficiency, and capital"), but offers only a single action verb ("Diagnose") rather than a list of multiple distinct actions like the 3-anchor example.	2 / 3
Completeness	Clearly answers both what ("Diagnose SaaS business health across growth, retention, efficiency, and capital") and when ("Use when preparing a business review or prioritizing urgent fixes") with an explicit trigger clause.	3 / 3
Trigger Term Quality	Includes natural terms ("business review", "urgent fixes", "SaaS business health") but omits common variations a user would actually say — board meeting, QBR, quarterly review, fundraising — which appear in the frontmatter scenarios but not the description.	2 / 3
Distinctiveness Conflict Risk	Occupies a clear niche — holistic multi-dimensional SaaS health diagnostic — distinct from the single-metric sibling skills, with triggers unlikely to fire for the wrong skill.	3 / 3
	Total	10 / 12 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (796 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 suspicious	Warning

	Total	13 / 16 Passed

Repository: deanpeters/Product-Manager-Skills
Path: skills/business-health-diagnostic/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.