CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

comps-analysis

Build institutional-grade comparable company analyses with operating metrics, valuation multiples, and statistical benchmarking in Excel/spreadsheet format. **Perfect for:** - Public company valuation (M&A, investment analysis) - Benchmarking performance vs. industry peers - Pricing IPOs or funding rounds - Identifying valuation outliers (over/under-valued) - Supporting investment committee presentations - Creating sector overview reports **Not ideal for:** - Private companies without comparable public peers - Highly diversified conglomerates - Distressed/bankrupt companies - Pre-revenue startups - Companies with unique business models

Quality

74%

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 ./plugins/vertical-plugins/financial-analysis/skills/comps-analysis/SKILL.md

The canonical home for this skill is comps-analysis in anthropics/financial-services

SKILL.md
Quality
Evals
Security

Quality

Content

56%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 skill is highly actionable and domain-rich, with genuine institutional-finance guidance (data-source hierarchy, formula-over-hardcode rules, verification checkpoints). Its weaknesses are verbosity and duplication — a 640-line monolith with two "Section 6" headings, triple-repeated industry metric lists, and checklists that restate earlier sections — plus no use of separate reference files to split that bulk.

Suggestions

Deduplicate aggressively: merge the three industry-specific metric lists (Sections 5, 6-Advanced, 9) into one table, renumber the duplicate "Section 6", and consolidate the formatting conventions, "Excel Formatting Checklist", and "Output Checklist" into a single checklist.

Move the Section 11 formula reference guide and the consolidated industry metric tables into a separate reference file (e.g., references/metrics.md) to cut SKILL.md to a lean overview, and make the examples/comps_example.xlsx reference resolvable in the bundle.

Drop explanations of basic finance definitions Claude already knows (EBITDA definition, ROE/ROA formulas) and fix the broken bullet "🚩ixing pure-play and conglomerates" (missing "M").

DimensionReasoningScore

Conciseness

The ~640-line body is noticeably padded and repetitive: two different sections are both numbered "Section 6" ("Best Practices & Quality Checks" and "Advanced Features"), industry-specific metric lists appear three times (Sections 5, 6-Advanced, and 9), and the formatting conventions of Section 1 are restated as both the "Excel Formatting Checklist" and the "Output Checklist". It also explains concepts Claude already knows ("EBITDA - Earnings before interest, tax, depreciation, amortization", "ROE = Net Income / Shareholders' Equity", what quartiles indicate). This matches anchor 2 ("Noticeably verbose; several unnecessary explanations or padded sections") rather than anchor 3's "some unnecessary explanation" — the redundancy is systematic, not incidental.

2 / 5

Actionability

Largely executable and concrete: exact Excel formulas ("Gross Margin (F7): =E7/C7", "=QUARTILE(B7:B9,3)"), a copy-paste-ready Office JS snippet with a real pitfall fix, hex color codes, and numeric sanity ranges ("EV/EBITDA: typically 8-25x"). Minor gaps keep it below anchor 5: many formulas are placeholders ("FCF Margin: =[FCF]/[Revenue]"), there is no complete end-to-end openpyxl script, and one bullet is literally broken ("🚩ixing pure-play and conglomerates").

4 / 5

Workflow Clarity

There is a clear 6-step sequenced process ("Set up structure → Gather data → Build formulas → Add statistics → Quality control → Documentation") plus an explicit user-checkpoint loop ("After setting up the structure → show the user the header layout... catch errors early") and sanity checks — squarely anchor-4/5 territory. It falls short of anchor 5 because the workflow is scattered across four places (data-source rules, the verification section, Section 7, Section 10 red flags), the duplicate "Section 6" headings muddle the sequence, and some verification is vague ("Test each calculation before moving on" without specifying how) — i.e., minor validation/organization gaps per anchor 4.

4 / 5

Progressive Disclosure

The body has real internal structure (numbered sections, clear headers, a one-level reference to "examples/comps_example.xlsx"), but no bundle files exist and everything is inlined in a single monolithic SKILL.md: a full formula reference guide (Section 11), formatting conventions, and industry-specific tables repeated three times — content that clearly belongs in separate reference files per the rubric. This sits between anchor 2 ("content that clearly belongs in separate files is inlined" with minimal structure) and anchor 4 ("most content is appropriately placed"); the doc is well-sectioned, so anchor 3 ("Some structure but... content that should be separate is inline") is the best fit.

3 / 5

Total

13

/

20

Passed

Description

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

A strong, well-scoped description with explicit what/when guidance and useful boundary exclusions. Its main weakness is thin action coverage — a single "Build" verb — and missing the most common practitioner synonyms ("comps", "trading comps").

Suggestions

Add 1-2 more concrete actions beyond "Build" (e.g., "calculate and benchmark valuation multiples, flag over/under-valued peers") to lift specificity.

Include the natural practitioner synonyms "comps" / "trading comps" / "peer benchmarking" in the trigger phrasing, since finance users typically ask for "comps".

DimensionReasoningScore

Specificity

The description names the domain and one concrete deliverable — "Build institutional-grade comparable company analyses with operating metrics, valuation multiples, and statistical benchmarking in Excel/spreadsheet format" — but the only action verb is "Build"; the bulleted lists describe use-cases, not additional capabilities. This matches anchor 3 ("Names domain and 1-2 concrete actions, but not comprehensive") and falls short of anchor 4, which expects several distinct specific actions (e.g., extract/fill/merge in the PDF example).

3 / 5

Completeness

The "what" is explicit (build comps with operating metrics, valuation multiples, statistical benchmarking in Excel) and the "when" is explicit and concrete via "**Perfect for:**" scenarios (M&A, IPO pricing, benchmarking, outlier identification) plus "**Not ideal for:**" exclusions. This is equivalent explicit trigger guidance, so the completeness cap of 3 does not apply, and it matches anchor 5 ("Clearly and explicitly answers both what AND when with concrete trigger phrases") rather than anchor 4 where the "when" would be less specific.

5 / 5

Trigger Term Quality

Good natural-term coverage: "Public company valuation", "M&A", "Benchmarking performance vs. industry peers", "Pricing IPOs or funding rounds", "sector overview reports" are phrases users would actually say. A few common synonyms are missing — notably "comps"/"trading comps", "peer analysis", and ".xlsx" — so it fits anchor 4 ("Good keyword coverage; a few natural terms missing") rather than anchor 5's comprehensive synonym/extension coverage.

4 / 5

Distinctiveness Conflict Risk

"Comparable company analyses" with its Excel deliverable carves a clear niche distinct from generic spreadsheet or valuation skills, and the "Not ideal for" list (conglomerates, distressed, pre-revenue startups) actively reduces mis-triggering. Fits anchor 5 ("Clear niche with distinct triggers; minimal conflict risk"); anchor 4's "minor overlap risk" would apply only if it could plausibly collide with a closely related skill, which the exclusion list forecloses.

5 / 5

Total

17

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (662 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

anthropics/financial-services

Path

plugins/vertical-plugins/financial-analysis/skills/comps-analysis/SKILL.md

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.