Tessl • The package manager for agent skills

Blog Docs Log inGet started

SkillPublic

merger-model

Build M&A accretion/dilution workbooks in Excel.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

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 well-structured, token-efficient checklist of deal inputs, table templates, and expert-level notes that trusts Claude's financial knowledge rather than re-teaching it. Its main weaknesses are a vestigial MCP/data-sources section that references passages that no longer exist, a placeholder path in its only command, and no validation/recovery loop around the recalculation step.

Suggestions

Rewrite the 'Data sources' section to drop the stale framing ('Many passages below say...') and simply state the sourcing hierarchy: prefer a configured financial-data MCP, else EDGAR/IR pages, and flag unsourced cells as [UNSOURCED].

Resolve the placeholder path in the recalc command (e.g., instruct how to locate the excel-author skill's scripts directory) so the single executable command is copy-paste ready.

Add an explicit validation loop around delivery, e.g., 'After recalculation, verify no #REF!/#DIV/0! cells in the output and that accretion/dilution ties to the summary tab before delivering the workbook.'

Dimension	Reasoning	Score
Conciseness	The body is dominated by lean, purposeful step templates and input checklists with no explanations of concepts Claude already knows. One exception: the 'Data sources' section opens with "Many passages below say 'use the S&P Kensho MCP / Daloopa MCP / FactSet MCP'" — a vestigial claim (no such passages follow) wrapped in adaptation narrative that could be trimmed, matching anchor 4 rather than 5.	4 / 5
Actionability	Concrete guidance throughout: named tabs ("Assumptions tab", "Sources & uses", "Sensitivity tables"), explicit line items ("Foregone interest on cash (after tax)", "Intangible amortization (after tax)"), and one executable command ("python /path/to/excel-author/scripts/recalc.py ./out/model.xlsx"). The command path is a placeholder and the underlying EPS/exchange-ratio formulas are left to be inferred rather than stated, which are minor gaps consistent with anchor 4.	4 / 5
Workflow Clarity	A clearly sequenced 7-step workflow (gather inputs, purchase price analysis, sources & uses, pro forma EPS, sensitivity, breakeven, output) with an explicit checkpoint "Recalculate before delivery". Workbook generation is not a destructive or batch operation, so the score-3 cap does not apply; the gap to anchor 5 is the absence of an error-recovery loop around the recalculation step.	4 / 5
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ are absent), and the ~130-line body is well-sectioned with clear headers and clearly signaled external references (the excel-author skill and its recalc script), with no nested reference chains. Minor gaps: the tab templates and the MCP-fallback guidance could live in separate reference files, and the referenced recalc script cannot be verified locally, so it stays at anchor 4.	4 / 5
	Total	16 / 20 Passed

Description

61%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 clear, distinctive niche, but it undersells the skill's actual capabilities and omits any 'when to use' trigger guidance, which caps completeness. Adding a 'Use when...' clause covering deal evaluation, pitch preparation, and merger consequences analysis would substantially improve it.

Suggestions

Add a 'Use when...' clause such as 'Use when evaluating a potential acquisition, preparing merger consequences analysis for a pitch, or advising on deal terms' (the body already contains this language — surface it into the description).

List a few more concrete actions in the description, e.g., 'Build M&A accretion/dilution workbooks in Excel: model pro forma EPS impact, purchase price allocation, sources & uses, synergy sensitivities, and breakeven synergies.'

Include common trigger variations like 'merger model', 'merger consequences analysis', and '.xlsx' to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Build M&A accretion/dilution workbooks in Excel" names the domain and one concrete action (building workbooks), matching the anchor for 1-2 concrete actions without comprehensive coverage. It does not enumerate the several specific actions the skill actually performs (synergy sensitivities, purchase price allocation), so it falls short of anchor 4.	3 / 5
Completeness	The "what" is clear (build M&A accretion/dilution workbooks in Excel), but there is no "Use when..." clause or equivalent trigger guidance anywhere in the description. Per the judging guidelines, a missing 'Use when...' clause caps completeness at 3.	3 / 5
Trigger Term Quality	Terms like "M&A", "accretion/dilution", "workbooks", and "Excel" are natural phrases a user would say when needing this skill, giving good keyword coverage. Common variations such as "merger model", "merger consequences", and the ".xlsx" extension are missing, so it does not reach anchor 5.	4 / 5
Distinctiveness Conflict Risk	The M&A accretion/dilution niche is quite distinct with clear domain-specific triggers, giving minimal conflict risk with unrelated skills. There is minor overlap risk with closely related financial-modeling skills (e.g., general Excel modeling, DCF, 3-statement models), keeping it below anchor 5.	4 / 5
	Total	14 / 20 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
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
Revision: ed728c5

Reviewed: 17 days ago

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.

merger-model

Table of Contents

Is this your skill?