The body is lean: terse bullet lists defining fields and table templates, with no padding explaining what a thesis or a portfolio is. Every line carries concrete guidance, assuming Claude's competence.

It gives concrete, copy-ready guidance — specific fields to capture (Company, Position, 3-5 Key pillars/risks, Stop-loss trigger), update-log columns, and worked scorecard/catalyst table examples. As an instruction-only skill, the absence of code is not penalized because the guidance is directly actionable.

Five explicitly sequenced steps (Define/Load → Update Log → Scorecard → Catalyst Calendar → Output) with a running scorecard whose Trend and conviction columns act as a feedback loop. Thesis tracking is not a destructive/batch operation, so no validation cap applies.

Content is organized into clearly labeled sections with no nested or multi-level file references; no bundle files exist or are needed, so the self-contained, well-structured body satisfies the top anchor for simple skills.

The description names multiple concrete actions — 'Maintain and update investment theses', 'Track key data points, catalysts, and thesis milestones over time' — matching the anchor for listing several specific concrete actions rather than a single vague domain reference.

It explicitly answers both what ('Maintain and update investment theses... Track key data points, catalysts, and thesis milestones') and when ('Use when updating a thesis with new information, reviewing position rationale, or checking if a thesis is still intact') with explicit triggers, satisfying the top anchor.

It provides natural phrases a portfolio manager would actually say — 'update thesis for [company]', 'is my thesis still intact', 'thesis check', 'add data point to [company]', 'review my positions' — giving good coverage of user-natural terms.

The investment-thesis-management niche is narrow and its triggers are specific to portfolio/thesis work, making it clearly distinguishable and unlikely to fire for unrelated skills.