CtrlK
BlogDocsLog inGet started
Tessl Logo

interview-me

Extracts what the user actually wants instead of what they think they should want. Achieves this through one-question-at-a-time interview until ~95% confidence about the underlying intent. Use when an ask is underspecified ("build me X" without "for whom" or "why now"), when the user explicitly invokes ("interview me", "grill me", "are we sure?", "stress-test my thinking"), or when you catch yourself silently filling in ambiguous requirements before any plan, spec, or code exists.

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exceptionally actionable behavioral skill with a clearly sequenced workflow, explicit validation gates, feedback loops, and a closing checklist. The main cost is token weight from deliberately repeating core rules across the Process, Rationalizations, Red Flags, and Verification sections.

Suggestions

Consolidate the repeated stop rule and "whatever you think" handling: state each once in The Process and have the Rationalizations table and Red Flags reference the step rather than restate it, cutting the biggest source of duplicated tokens.

Move the worked example dialogue (about 30 lines) to a references/example.md file and link it from the Process section, which would simultaneously reduce body size and improve progressive disclosure.

Trim the Verification checklist from 9 items to the 4-5 that aren't already direct restatements of Red Flags entries.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence (no basic-concept padding), but key rules are repeated across three or four sections — the "predict the next three questions" stop rule appears in Steps 1, 6, the rationalizations table, red flags, and the checklist, and "whatever you think" handling appears in Step 5, the table, and red flags. Matches 'mostly efficient but could be tightened'; not a 4 because the repetition is more than minor trimming.

3 / 5

Actionability

Fully executable for an instruction-only skill: copy-paste-ready formats for HYPOTHESIS/CONFIDENCE, the Q/GUESS pair, the six-field restate template, exact scripted responses to each non-yes answer, a concrete save path (docs/intent/[topic].md), and a complete worked example dialogue. Not a 4: no gaps in concrete guidance for the common cases.

5 / 5

Workflow Clarity

Six clearly numbered steps with an explicit confirmation gate ("explicit yes, not 'whatever you think'"), a checkable stop test, an error-recovery feedback loop ("If they correct you, fold the correction in and restate. Loop until an explicit yes"), an escalation floor, and a final verification checklist. Matches the anchor for clear sequence with validation steps, feedback loops, and a checklist.

5 / 5

Progressive Disclosure

No bundle files exist, so all content is inline in a single ~230-line file, but it is well-sectioned with clear headers (When to Use, Process, Example, Red Flags, Verification) and no nested references. Not a 5: it exceeds the short-skill range where a monolithic file scores full marks, and the rationalizations table and example dialogue are borderline candidates for a separate reference file. Not a 3: navigation is easy and nothing is buried.

4 / 5

Total

17

/

20

Passed

Description

86%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that explicitly states both the mechanism (one-question-at-a-time interview to ~95% confidence) and rich, naturally-worded trigger conditions including literal user invocation phrases. Its only weaknesses are a single-process action description and one broad internal-state trigger.

DimensionReasoningScore

Specificity

"Extracts what the user actually wants... through one-question-at-a-time interview until ~95% confidence about the underlying intent" names the domain and 1-2 concrete actions (interview one question at a time, stop at 95% confidence), but describes a single process rather than listing several specific actions, matching the 'not comprehensive' anchor. Not a 4: the action set does not enumerate multiple distinct capabilities; not a 2: the method described is concrete, not generic.

3 / 5

Completeness

Explicitly answers both what ("Extracts what the user actually wants... one-question-at-a-time interview until ~95% confidence") and when ("Use when an ask is underspecified... when the user explicitly invokes..."), with concrete quoted trigger phrases. Matches the anchor for clearly answering both with concrete triggers.

5 / 5

Trigger Term Quality

Quoted invocation phrases users would naturally say — "interview me", "grill me", "are we sure?", "stress-test my thinking" — plus the underspecified-ask pattern ("build me X" without "for whom" or "why now") give comprehensive natural-term coverage for this domain. Not a 4: no common user phrasing for this need is obviously missing.

5 / 5

Distinctiveness Conflict Risk

The niche is clear — pre-spec intent extraction via interactive interview, bounded by "before any plan, spec, or code exists" — with distinct quoted triggers. Not a 5: the trigger "when you catch yourself silently filling in ambiguous requirements" is an internal-state condition with some overlap risk against general clarifying-question behavior and related Define-phase skills.

4 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
addyosmani/agent-skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.