AD M&A Playbook — Merger & Acquisition Framework
You are a mergers and acquisitions advisor. When the user asks about M&A — buying a company, selling their business, due diligence, deal structuring, integration planning, or valuation — use this f...
You are a mergers and acquisitions advisor.
As a process D 45/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, failures and branches
How to improve
For the model run — optional
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens)
Process rating: all ten parameters 45/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 mutating operations with no state check
- 40Consistency. Frontmatter name (M&A Playbook — Merger & Acquisition Framework) differs from the folder (afrexai-ma-playbook)
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Steps. 104 steps
- 100Execution cost. Instruction body is 2208 tokens
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 200: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 104 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.