Six lean lines with zero padding and no explanation of concepts Claude already knows; every directive earns its place, matching the 3 'lean and efficient' anchor.

Concrete behavioral directives ('Ask the questions one at a time', 'provide your recommended answer', 'explore the codebase instead') give specific, actionable guidance; absence of code is appropriate for this instruction-only skill per the rubric's code_vs_instruction note.

The single-purpose process is clearly sequenced (interview -> walk each branch one-by-one -> recommend answers -> defer to codebase exploration), and as a simple non-destructive skill it qualifies for 3 under the simple_skills note without needing validation checkpoints.

At under 50 lines with no external references needed and no bundle files present, the well-organized short body meets the 3 threshold for simple skills per the rubric's judging guidelines.

Names a concrete domain (interviewing about a plan/design) and elaborates the action ('resolving each branch of the decision tree'), but describes one enriched action rather than a list of multiple distinct concrete actions, so it sits below the 3 anchor.

It clearly answers both what ('Interview the user relentlessly... resolving each branch of the decision tree') and when (explicit 'Use when... stress-test a plan, get grilled... or mentions "grill me"'), matching the 3 anchor.

Natural phrases a user would actually say appear explicitly: 'stress-test a plan', 'get grilled on their design', and the literal 'grill me', giving good coverage of likely trigger language.

The grilling/interviewing niche with the distinctive 'grill me' trigger is clearly distinguishable from other skills and unlikely to fire for the wrong skill.