The body is lean — bullet lists and tables that assume Claude's familiarity with PE/finance concepts, with no padding explaining what EBITDA or a 100-day plan is. It is not a 2 because nearly every token is actionable structure rather than redundant explanation that could be tightened.

Provides concrete, copy-paste-ready templates: an EBITDA bridge table by year, a KPI dashboard with owners and reporting frequency, and a 100-day plan with specific day ranges and tasks. It is not a 2 because the guidance is specific and directly usable rather than abstract or pseudocode-level.

A clear six-step sequence (Baseline → Levers → EBITDA Bridge → 100-Day Plan → KPI Dashboard → Output) with built-in feedback ('Adjust plan based on early learnings', 'pressure-test assumptions with operating partners'). It is not capped at 2 because this is a non-fragile planning workflow rather than a destructive/batch/XML/DB operation, so hard validate-retry gates are not required and the sequencing plus adjustment notes satisfy the top anchor.

No bundle files exist in references/scripts/assets, and the body references none; the content is self-contained and well-organized into clearly labeled sections and tables. It is not a 2 because organization is clean with no monolithic wall of text or nested references to score against.

Lists multiple concrete actions — 'Structure post-acquisition value creation plans with revenue, cost, and operational levers mapped to an EBITDA bridge' and 'Includes 100-day priorities, KPI targets, and accountability frameworks' — matching the top anchor for specific concrete actions. It is not a 2 because it goes beyond naming a domain to enumerating several distinct deliverables rather than only some actions.

Explicitly answers both what ('Structure post-acquisition value creation plans...') and when ('Use when planning post-close execution, preparing operating partner materials, or building a board-ready value creation roadmap'), with explicit triggers. It is not a 2 because the 'Use when' clause is present and concrete, not merely implied.

Provides a dedicated trigger list — 'value creation plan', '100-day plan', 'post-close plan', 'EBITDA bridge', 'operating plan', 'value creation levers' — natural phrases a user would say when needing this skill. It is not a 2 because coverage spans multiple common variations rather than just one or two relevant keywords.

Targets a clear niche (post-acquisition PE value creation) with distinct triggers ('EBITDA bridge', '100-day plan'), making it unlikely to fire for unrelated skills. It is not a 2 because the scope is specialized and clearly bounded rather than broadly overlapping with general planning skills.