Conciseness

The body is dense tables and checklists carrying UA-specific numbers (CPI ranges, bid targets, conversion benchmarks) that Claude cannot reliably recall, so nearly every token earns its place; minor trimmable padding ("You are an expert in mobile app user acquisition…", "Works for any budget") keeps it below the lean anchor of 5, while the absence of any explanation of concepts Claude already knows rules out 3.

Actionability

Guidance is concrete down to numbers and placeholders: exact campaign trees ("Brand Campaign (exact match)… Discovery Campaign (Search Match)"), bid tables ("< $0.50", "$2-5"), a fill-in output template, and an optimization checklist — the instruction-only equivalent of copy-paste-ready commands covering the common cases, matching the top anchor rather than the minor-gaps anchor of 4.

Workflow Clarity

A clear sequence runs Initial Assessment → Channel Selection → per-channel setup → Optimization Cadence → Output Format, with checkpoints like "Check for `app-marketing-context.md`" and feedback loops such as "Pause keywords with CPA > 2x target"; it stops short of 5 because there are no explicit error-recovery paths (e.g., what to do when LTV is unknown or actual CPI exceeds target).

Progressive Disclosure

A single, cleanly sectioned file with decision-relevant content inline and a Related Skills pointer, and no bundle files exist; 5 is unavailable because ~200 lines exceeds the under-50-line no-references exception and the per-channel deep dives (ASA/Meta/Google) could live in references/, while the clean organization and coherent inline placement rule out 3.

Specificity

"plan or optimize paid user acquisition campaigns" names the domain with exactly two concrete actions, matching the anchor for 1-2 actions without comprehensive coverage; the remaining sentences are triggers, not capabilities, so it does not reach the several-actions level of 4.

Completeness

It explicitly answers what ("plan or optimize paid user acquisition campaigns") and when ("When the user wants to… Also use when the user mentions…") with concrete trigger phrases, mirroring the anchor-5 example structure; the 'when' clause could not be more explicit, ruling out 4.

Trigger Term Quality

Nine natural trigger phrases including synonyms and the acronym users actually say ("Apple Search Ads", "user acquisition", "paid ads", "UA", "ad campaign", "install campaign", "Facebook ads for apps", "TikTok ads", "cost per install"), giving comprehensive coverage; no central term is missing, so it fits the top anchor rather than the 'a few natural terms missing' anchor.

Distinctiveness Conflict Risk

Explicit boundary guidance ("For organic growth, see aso-audit. For launch-specific UA, see app-launch") plus niche-specific trigger terms establish a clear niche with minimal conflict risk; disambiguation against the closest neighboring skills is explicit, so the minor-overlap anchor of 4 does not fit.