CtrlK
BlogDocsLog inGet started
Tessl Logo

merger-model

Build accretion/dilution (merger) models in Excel — pro-forma P&L, synergies, financing mix, EPS impact. Pairs with excel-author. Use for M&A pitches, board materials, or deal evaluation.

69

Quality

86%

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

SKILL.md
Quality
Evals
Security

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise and well-structured with a clear stepwise workflow, but it relies on blank template tables instead of executable formulas and lacks an explicit validation loop tying out the produced workbook. Filling in formula logic and adding a verify step would lift the weaker dimensions.

Suggestions

Replace the empty Pro Forma EPS and Sources & Uses tables with concrete openpyxl formulas (or a runnable builder snippet) so the guidance is copy-paste executable rather than scaffolding.

Add an explicit validation checkpoint after the recalc step — e.g., assert pro forma net income reconciles to standalone + target + synergies ± financing adjustments — so the workflow has a real verify/fix loop.

Provide the actual exchange-ratio and foregone-interest formulas inline in Step 4, since the rows are named but the math is left unstated.

DimensionReasoningScore

Conciseness

The body is lean tables and tight lists that assume competence (no padding explaining what a P&L, EPS, or synergy is), with every section earning its place; the MCP-fallback note is useful rather than filler.

3 / 3

Actionability

Most steps are empty scaffolding tables (headers only, no formulas or executable code) plus one concrete recalc command — concrete guidance is present but incomplete, matching the 'pseudocode / missing key details' anchor rather than copy-paste-ready code.

2 / 3

Workflow Clarity

A clear 7-step sequence and a 'recalculate before delivery' checkpoint exist, but there is no verify/error-recovery loop confirming the workbook ties out, leaving validation gaps that cap this at 2.

2 / 3

Progressive Disclosure

A single well-organized SKILL.md with clearly labeled sections and only a one-level reference to the external excel-author skill; no deep nesting and no bundle files to split, so the structure is clean and navigable.

3 / 3

Total

10

/

12

Passed

Description

100%

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, trigger-rich, and complete with an explicit 'Use for...' clause, and it carves a clear niche distinct from the sibling excel-author skill. No vague fluff or over-claims are present.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Build accretion/dilution (merger) models in Excel — pro-forma P&L, synergies, financing mix, EPS impact' — matching the anchor for enumerating several specific capabilities.

3 / 3

Completeness

Explicitly answers both: what ('Build accretion/dilution... models') and when ('Use for M&A pitches, board materials, or deal evaluation'), satisfying the both-what-and-when anchor with an explicit trigger clause.

3 / 3

Trigger Term Quality

Natural user-facing terms 'Excel', 'merger', 'M&A', 'EPS impact', 'accretion/dilution', 'deal evaluation' give strong coverage of phrasing a user would actually say; not merely jargon.

3 / 3

Distinctiveness Conflict Risk

Narrow M&A merger-model niche with 'Pairs with excel-author' clarifies its boundary, so it is unlikely to fire for the wrong generic Excel skill.

3 / 3

Total

12

/

12

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.

Validation13 / 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
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.