merger-model

Build M&A accretion/dilution workbooks in Excel.

Quality

68%

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 content is a well-structured, mostly lean merger-model template with concrete tables, a clear multi-step workflow, and a verification step. It scores solidly across all dimensions with only minor gaps around validation feedback loops and placeholder paths.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient, using tables and terse bullets and assuming finance knowledge rather than explaining it, but the 'Data sources' history of the Cowork plugin context and the provenance 'Attribution' section add tokens that could be trimmed.	4 / 5
Actionability	Concrete, specific guidance is provided via exact input lists, line-item tables, and a recalc command, but there is no executable openpyxl code and the recalc path is a placeholder ('/path/to/excel-author/'), leaving minor gaps.	4 / 5
Workflow Clarity	A clear 7-step sequence runs from inputs to output, and a 'Recalculate before delivery' verification step exists, but it is not integrated as an explicit validation checkpoint with a fix-and-retry feedback loop.	4 / 5
Progressive Disclosure	The file is well-organized with clear section headers and only one-level cross-skill references, and no broken or nested references exist, but with no bundle files the content is entirely inline in a single ~130-line file rather than split into supporting files.	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 specific and clearly targets a distinct finance niche, but it omits any explicit 'use when' trigger guidance and lists only a single concrete action. Adding a trigger clause and one or two more concrete actions would lift the weaker dimensions.

Suggestions

Append an explicit 'Use when ...' trigger clause, e.g. 'Use when evaluating an acquisition, preparing merger consequences analysis, or modeling deal terms.'

Add one or two more concrete actions (e.g. 'model pro forma EPS impact, run synergy sensitivities, allocate purchase price') to move specificity toward score 4-5.

Include natural synonyms and the file extension (e.g. 'merger model', '.xlsx') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description names a precise domain ('M&A accretion/dilution') and one concrete action ('Build ... workbooks in Excel'), but lists only a single action rather than the several specific actions the score-4 anchor requires.	3 / 5
Completeness	It clearly states the 'what' ('Build M&A accretion/dilution workbooks') but has no 'Use when ...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Natural finance keywords a user would say are present ('M&A', 'accretion/dilution', 'Excel', 'workbooks'), but common synonyms and the .xlsx file extension are missing, so it falls short of comprehensive score-5 coverage.	4 / 5
Distinctiveness Conflict Risk	'M&A accretion/dilution' is a distinct niche with minimal conflict risk, but the generic 'Excel' framing and the existence of related financial-modeling skills create minor overlap risk, placing it just below the score-5 anchor.	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
Commit: 6680afb

Reviewed: about 4 hours 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.