CtrlK
BlogDocsLog inGet started
Tessl Logo

saas-valuation-compression

Analyze how a private SaaS company's ARR valuation multiple changed across funding rounds, and attribute the compression or expansion to rate cycles and macro selloffs, growth deceleration, narrative shifts (including an AI premium), competition, and investor demand, benchmarked against private-market medians and peers. Use this skill whenever the user asks about valuation compression, ARR multiples, round-to-round valuation or multiple changes, down rounds, or wants to compare a VC-backed software company's funding rounds. Research the rounds rather than answering from memory.

72

Quality

89%

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

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 strong, well-structured research-workflow skill: concrete formulas, estimation heuristics, an attribution checklist, and handled edge cases, with dated data properly pushed to a one-level-deep reference file. The residual weaknesses are the unspecified 'Visualizer tool' invocation, a small amount of context duplicated between the body and benchmarks.md, and no guidance for reconciling conflicting or missing search results.

Suggestions

Give step 5 a concrete anchor for the Visualizer tool — e.g., one example component spec or a pointer to a reference file with the chart template — so the visualization step is as executable as steps 2–4.

Deduplicate the macro context: keep only a one-line pointer in the Macro/AI Premium sections and let references/benchmarks.md carry the ZIRP premium and April 2026 drawdown details.

Add a short error-recovery note in step 1 or 2 for what to do when round data or ARR figures conflict or are missing (e.g., prefer dated primary sources, show the estimate range, and mark confidence).

DimensionReasoningScore

Conciseness

The body is dense and domain-specific with almost no padding — formulas, ARR estimation heuristics, and an attribution checklist that Claude cannot reconstruct from general knowledge. It sits at 4 rather than 5 because the ZIRP '~2–5x artificial premium' rule and the April 2026 meltdown context are stated inline in the Macro and AI Premium sections while also appearing in references/benchmarks.md, a small duplication that could be trimmed. Not 3 because there is no over-explanation of concepts Claude already knows.

4 / 5

Actionability

Concrete, executable guidance dominates: exact metric formulas ('multiple_compression_pct = (later_multiple - earlier_multiple) / earlier_multiple × 100'), a data-model table with per-field extraction methods, numeric ARR heuristics by stage, a rated cause checklist, and five handled edge cases. It falls short of 5 because step 5 directs 'Use the Visualizer tool' and 'Follow the CSS variable system' without any concrete example or spec, leaving the visualization step the least executable.

4 / 5

Workflow Clarity

Six clearly sequenced steps (gather → model → compute → attribute → visualize → summarize) with an explicit cause-rating checklist and data-integrity checkpoints ('note when a figure is estimated', 'flag your data confidence when ARR had to be estimated'). No error-recovery loop is specified — e.g., what to do when round data or ARR figures conflict or a search comes up empty for multiples — which keeps it below 5; the workflow is not destructive or batch-oriented, so no lower cap applies.

4 / 5

Progressive Disclosure

The dated benchmark tables are correctly split into references/benchmarks.md (verified to exist), referenced inline at three well-signaled points and again in a 'Reference Files' section, one level deep with no nesting. The body reads as overview-plus-workflow and navigation is easy; the minor inline restatement of macro context is a hint rather than a duplicated data dump.

5 / 5

Total

17

/

20

Passed

Description

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

An exemplary description: concrete multi-action capability statement, an explicit 'Use this skill whenever...' trigger clause with natural synonyms, a clearly distinct niche, and no fluff or over-claiming. It is concise while covering what, when, and scope of research.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Analyze how a private SaaS company's ARR valuation multiple changed across funding rounds', 'attribute the compression or expansion to rate cycles and macro selloffs, growth deceleration, narrative shifts... competition, and investor demand', 'benchmarked against private-market medians and peers', and 'Research the rounds rather than answering from memory' — comprehensive coverage. Not 4 because there are no coverage gaps; every capability is named as a concrete action.

5 / 5

Completeness

Explicitly answers what ('Analyze how... ARR valuation multiple changed across funding rounds, and attribute the compression or expansion to...') and when ('Use this skill whenever the user asks about valuation compression, ARR multiples, round-to-round valuation or multiple changes, down rounds...'). Mirrors the anchor-5 example structure; not 4 because both halves are explicit and use concrete trigger phrases.

5 / 5

Trigger Term Quality

Covers natural user phrasings with synonyms and variations: 'valuation compression', 'ARR multiples', 'round-to-round valuation or multiple changes', 'down rounds', 'compare a VC-backed software company's funding rounds'. Matches the anchor-5 pattern of comprehensive natural-term coverage; no common variant of the ask is missing.

5 / 5

Distinctiveness Conflict Risk

A clear niche — ARR-multiple compression analysis for VC-backed SaaS funding rounds — with distinct triggers that would not plausibly fire for a generic finance or web-research skill. Third-person voice ('Analyze', 'attribute', 'Research') is used throughout.

5 / 5

Total

20

/

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
himself65/finance-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.