CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ma-playbook

M&A strategy for acquiring companies or being acquired. Due diligence, valuation, integration, and deal structure. Use when evaluating acquisitions, preparing for acquisition, M&A due diligence, integration planning, or deal negotiation.

71

Quality

89%

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

The canonical home for this skill is ma-playbook in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

92%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.

Excellent instruction-only content: lean, concrete, quantified, with clear two-sided workflows and an explicit pre-LOI verification loop that delegates to sibling skills instead of duplicating them. The single significant defect is progressive disclosure: two referenced bundle files (references/integration-playbook.md, references/due-diligence-checklist.md) do not exist, so the skill promises material it cannot deliver.

Suggestions

Create the referenced bundle files references/integration-playbook.md and references/due-diligence-checklist.md, or remove the pointers and inline whatever content is essential — currently the Integration Frameworks and Resources sections promise material that does not exist in the bundle.

Verify the sibling-skill paths (../general-counsel-advisor/scripts/term_sheet_analyzer.py, ../chief-data-officer-advisor/scripts/ai_training_data_audit.py, etc.) resolve in the deployed skill fleet, since the Verification Loop depends on them; note in the body what to do if the sibling tooling is unavailable.

The Keywords section duplicates trigger terms already present in the description frontmatter — fold the few unique terms (LOI, term sheet, earnout, acqui-hire) into the description and drop the section to save tokens.

DimensionReasoningScore

Conciseness

The body is lean and dense — checklists, tables, and quantified red flags ('>30% revenue from 1 customer', '$1-3M per engineer') with zero explanation of concepts Claude already knows. Every section adds non-obvious value (e.g., naming the specific sources to verify multiples against), matching the 'every token earns its place' anchor.

5 / 5

Actionability

Highly actionable for an instruction-only skill: quantified red-flag thresholds, named verification sources with a 'cross-check at least two' rule, a numbered preparation sequence, and exact sibling-script paths to run ('term_sheet_analyzer.py', 'ai_training_data_audit.py') with pass/fail conditions ('Any 🔴 finding goes to outside counsel before signing').

5 / 5

Workflow Clarity

Both Quick Start sequences are explicit (rationale → screening → DD → valuation → negotiation → integration; readiness → data room → advisor → negotiation → transition), and the 'Verification Loop (before any LOI or signature)' adds explicit validation gates and a feedback loop ('Loop the findings back into the negotiation-points table before the next counter') plus checklists for the DD domains — matching the top anchor.

5 / 5

Progressive Disclosure

Section structure and reference signaling are good, but the body cites 'references/integration-playbook.md' and 'references/due-diligence-checklist.md' (both in the Integration Frameworks section and again in Resources) and neither file exists in the bundle — the references/ directory is absent entirely. Scoring against the actual bundle structure, navigation breaks at the point of use, which is a bigger defect than the 'minor organization gaps' of anchor 4 but the structure is still far better than anchors 1-2.

3 / 5

Total

18

/

20

Passed

Description

83%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.

A strong description that clearly states both sides of M&A (acquiring and being acquired), enumerates the core workstreams, and gives an explicit 'Use when...' clause with natural trigger phrases. Third person, no fluff. The only weaknesses are a few missing natural synonyms and minor overlap risk with sibling finance/legal skills.

DimensionReasoningScore

Specificity

The description lists several specific workstreams — 'Due diligence, valuation, integration, and deal structure' — with two-sided framing ('acquiring companies or being acquired'), matching the anchor for several specific actions with minor gaps. It is not a 5 because the capabilities are domain nouns rather than fully concrete actions and coverage has minor gaps (e.g., LOI/term-sheet review is covered in the body but not mentioned).

4 / 5

Completeness

It explicitly answers both: what — 'M&A strategy for acquiring companies or being acquired. Due diligence, valuation, integration, and deal structure.' and when — 'Use when evaluating acquisitions, preparing for acquisition, M&A due diligence, integration planning, or deal negotiation.' This matches the anchor for clear what AND when with concrete trigger phrases.

5 / 5

Trigger Term Quality

'Use when evaluating acquisitions, preparing for acquisition, M&A due diligence, integration planning, or deal negotiation' provides good natural-phrase coverage a user would actually say. A few natural terms are missing ('mergers', 'selling the company', 'LOI', 'term sheet', 'acqui-hire') — several of which the body itself lists as keywords — so it falls short of the comprehensive anchor 5 but sits above anchor 3.

4 / 5

Distinctiveness Conflict Risk

M&A is a clear niche with distinct triggers, but 'valuation' and 'deal negotiation' overlap with the closely related cfo-advisor and general-counsel-advisor skills that this skill's own body delegates to, creating minor overlap risk — matching the 'mostly distinct; minor overlap risk with closely related skills' anchor rather than anchor 5.

4 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

15

/

16

Passed

Repository

alirezarezvani/claude-skills

Path

.gemini/skills/ma-playbook/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.