CtrlK
BlogDocsLog inGet started
Tessl Logo

merger-model

Build accretion/dilution analysis for M&A transactions. Models pro forma EPS impact, synergy sensitivities, and purchase price allocation. Use when evaluating a potential acquisition, preparing merger consequences analysis for a pitch, or advising on deal terms. Triggers on "merger model", "accretion dilution", "M&A model", "pro forma EPS", "merger consequences", or "deal impact analysis".

70

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.

A well-structured, token-efficient merger-model template with clear sequencing, but it stops at scaffolding: the core formulas and validation checkpoints that would make the workflow fully executable and self-checking are not specified.

Suggestions

Add the explicit formulas for pro forma EPS, accretion/dilution %, and breakeven synergies so the pro forma and sensitivity steps are executable rather than implied.

Insert validation checkpoints into the workflow — e.g., confirm sources & uses balance after Step 3 and reconcile pro forma shares after Step 4 before proceeding.

Flesh out Steps 5 and 6 with the concrete computation method (how sensitivity cells and the breakeven synergy solve are derived) instead of one-line directives.

DimensionReasoningScore

Conciseness

Lean template tables and input checklists with no concept explanations Claude already knows; structure earns its tokens rather than padding.

3 / 3

Actionability

Provides concrete input lists and a full line-item scaffold (PPA, sources & uses, pro forma EPS, sensitivity) but omits the actual formulas and computation steps for pro forma EPS, accretion %, and breakeven synergies, leaving key details implied rather than stated.

2 / 3

Workflow Clarity

The seven steps are clearly sequenced, but there are no validation checkpoints or feedback loops (e.g., sources & uses balance check, EPS reconciliation), so checkpoints are missing rather than explicit.

2 / 3

Progressive Disclosure

Self-contained and well-organized into labeled sections with no nested or deep external references; nothing that should be split out is inlined.

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.

A strong, specific description that concretely names its capabilities, provides natural trigger terms, and explicitly states both what it does and when to use it, with minimal conflict risk.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — 'Build accretion/dilution analysis', 'Models pro forma EPS impact, synergy sensitivities, and purchase price allocation' — rather than vague language.

3 / 3

Completeness

Clearly answers both what (build accretion/dilution analysis, model EPS/sensitivities/PPA) and when ('Use when evaluating a potential acquisition, preparing merger consequences analysis for a pitch, or advising on deal terms') with explicit triggers.

3 / 3

Trigger Term Quality

Explicit natural triggers ('merger model', 'accretion dilution', 'M&A model', 'pro forma EPS', 'merger consequences', 'deal impact analysis') that a user would naturally say, in third-person voice.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear M&A merger-modeling niche with distinct triggers, making it unlikely to fire for the wrong skill.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
anthropics/financial-services
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.