Opus finding
VAR_HOTSPOT and bucket priority can shadow MODEL_CONSENSUS / EMERGING for the same skill, but spec says 'first match wins' inconsistently
lowapi-contractmedium
- skills/fork-skill-digest/SKILL.md:122-137
- skills/fork-skill-digest/SKILL.md:174-186
Step 7 mandates that a skill appears in only one bucket (first match wins, with MODEL_CONSENSUS before VAR_HOTSPOT). But the article template in step 11 lists separate Model overrides and Var hotspots sections as if a skill could appear in both. A skill that hits both MODEL_CONSENSUS and VAR_HOTSPOT will only appear under Model overrides, silently dropping the var-hotspot signal from the digest. This is a real loss of analytic signal that the doc never acknowledges.
Recommendation
Either allow MODEL_CONSENSUS and VAR_HOTSPOT (and EMERGING) to coexist for the same skill (since they describe orthogonal dimensions), or explicitly state in the article template that each skill appears in at most one section so the omission is intentional.