CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

merger-model

Build M&A accretion/dilution workbooks in Excel.

Quality

69%

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

Fix and improve this skill with Tessl

tessl review fix ./optional-skills/finance/merger-model/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 body is a lean, well-sequenced modeling template with concrete scaffolds and a validation step, consistently one notch below excellent. The main deficits are implicit key formulas, a missing failure/recovery loop around recalculation, and a stale data-sources lead-in.

Suggestions

Add a short feedback loop after recalculation, e.g. "If recalc.py reports broken references or the accretion cell doesn't populate, fix the formula and re-run before delivery."

State the core share-count mechanics explicitly (new shares = stock-portion equity value / acquirer price; pro forma shares = acquirer shares + new shares) so the EPS bridge is fully executable.

Rewrite the "Data sources" lead-in — no passages in this body reference Kensho/Daloopa/FactSet MCPs, so the paragraph should stand alone or be trimmed.

DimensionReasoningScore

Conciseness

The body is efficient — input checklists, exact line-item tables, and pointed notes with no explanations of concepts Claude already knows. Minor trimming is possible: the "Data sources" lead-in ("Many passages below say 'use the S&P Kensho MCP...'" — no such passages exist in this body) is stale, and the attribution/environment meta-text adds tokens without guiding the task. This sits between "mostly efficient with some unnecessary explanation" and "lean with every token earning its place".

4 / 5

Actionability

Concrete, executable guidance throughout: exact table scaffolds (Sources & Uses, Pro Forma EPS line items), specific sensitivity grids (15%-30% premium × $0-$100M synergies; cash/stock mix), and a runnable recalc command. Minor gaps remain — key formulas such as exchange ratio and new shares issued are left implicit, and the sensitivity/premium ranges are hard-coded rather than parameterized from gathered inputs.

4 / 5

Workflow Clarity

A clear 7-step sequence (inputs → purchase price → sources & uses → pro forma EPS → sensitivities → breakeven → output) with a validation checkpoint ("Recalculate before delivery: python .../recalc.py"). It falls short of anchor 5 because there is no explicit error-recovery loop (e.g., what to do if recalc fails or totals don't tie) and no tie-out checks between Sources & Uses and the purchase price analysis.

4 / 5

Progressive Disclosure

The ~130-line body is well-sectioned with clear headers, and conventions/scripts are cleanly delegated to the external excel-author skill rather than inlined. No bundle files exist to verify, and no content that belongs in a separate file is inlined; it is not a 5 because navigation depends on an external skill's conventions without bundled fallback material for key formulas or output formatting.

4 / 5

Total

16

/

20

Passed

Description

53%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 is concise and names a distinctive niche, with a clear "what" but no "when". It lacks the capability breadth (PPA, sources & uses, sensitivities, breakeven) and natural trigger phrases ("merger model", "deal analysis") that would make it comprehensive.

Suggestions

Add an explicit trigger clause, e.g. "Use when asked for a merger model, accretion/dilution analysis, or merger consequences analysis for a deal."

Enumerate the concrete outputs to raise specificity: "...covering purchase price analysis, sources & uses, pro forma EPS, synergy sensitivities, and breakeven synergies."

Include natural synonyms users say — "merger model", "M&A analysis", "deal accretion" — alongside "accretion/dilution" to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain ("M&A accretion/dilution") and one concrete action ("Build ... workbooks in Excel"), matching the anchor for 1-2 concrete actions but not comprehensive — capabilities like purchase price allocation, sources & uses, or sensitivity analysis are absent. Anchor 4 requires several specific actions, which this single-action description does not meet.

3 / 5

Completeness

It has a clear "what" ("Build M&A accretion/dilution workbooks in Excel") but no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 2 because the "what" is concrete and specific, not vague.

3 / 5

Trigger Term Quality

"M&A", "accretion/dilution", and "Excel" are natural terms a user would say, but common variations and synonyms such as "merger model", "merger consequences analysis", or "deal analysis" are missing. This matches the anchor for some relevant keywords with missing variations rather than good coverage.

3 / 5

Distinctiveness Conflict Risk

"M&A accretion/dilution" is a clear niche with minimal conflict risk, but "workbooks in Excel" creates minor overlap with closely related skills (the skill's own metadata lists excel-author, dcf-model, 3-statement-model). This fits "mostly distinct; minor overlap risk with closely related skills" rather than the fully distinct anchor 5.

4 / 5

Total

13

/

20

Passed

Validation

81%

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

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository

NousResearch/hermes-agent

Path

optional-skills/finance/merger-model/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.