CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

interview-me

Analyze underspecified requests with a short decision interview. Use this skill when guessing would risk the wrong plan.

Quality

66%

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

Fix and improve this skill with Tessl

tessl review fix ./Skills/product-strategy/interview-me/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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.

The skill body is well-structured with a clear sequenced workflow and explicit terminal states, and it avoids explaining concepts Claude already knows. Its weaknesses are a verbatim duplicated section (Avoid/Anti-Patterns), missing executable details such as an example question and exact validation commands, and a progressive-disclosure reference that points to a path absent from the bundle.

Suggestions

Delete the "Anti-Patterns" section or the "Avoid" section — they are verbatim duplicates of the same three bullets.

Add a concrete example of one interview question with its 3-5 choices and a decision-log entry format, and name the exact Plugin Eval / skill audit commands in the Validation section.

Fix the "Progressive Disclosure" reference: either point to files that actually exist in the bundle (e.g., references/evals.yaml) or remove the dangling `Infrastructure/references/deferred-skill-context/...` path.

DimensionReasoningScore

Conciseness

The body is mostly compact bullet fragments with no basic-concept explanations, but the "Anti-Patterns" section duplicates the "Avoid" section verbatim (three identical bullets), a clear redundancy to trim. This fits anchor 3 (mostly efficient but could be tightened) rather than 2, since the padding is limited to one duplicated section.

3 / 5

Actionability

There is concrete guidance ("Ask one high-impact question with 3-5 choices and one recommended default", "End with approved, needs-input, or blocked plus the next route") but key executable details are missing: no example question, no decision-log format, and "Run Plugin Eval and strict skill audit" never names the actual commands. This matches anchor 3, not 4, due to those gaps.

3 / 5

Workflow Clarity

The 5-step workflow is clearly sequenced with a conditional gate ("Ask a second question only if a material blocker remains") and an explicit terminal state ("approved, needs-input, or blocked"). This fits anchor 4; it is not 5 because there is no validate-fix-retry feedback loop, and the destructive/batch cap does not apply since this is not a destructive or batch skill.

4 / 5

Progressive Disclosure

Sections are well-organized for a short skill, but the "Progressive Disclosure" section references `Infrastructure/references/deferred-skill-context/product-strategy-interview-me/`, which does not exist in the bundle (references/ contains only contract.yaml, evals.yaml, task-profile.json). Scored against the actual bundle structure, the dangling reference fits anchor 3 rather than 4, where references would resolve to real files.

3 / 5

Total

13

/

20

Passed

Description

62%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.

The description is concise, in third person, and answers both what and when with an explicit 'Use when' clause. Its main weaknesses are thin action coverage and the absence of natural trigger phrasings users would actually say, leaving it mid-scale on specificity and trigger quality.

Suggestions

Add 2-3 more concrete actions to the description, e.g., "Asks one high-impact question with 3-5 options and a recommended default, records decisions and assumptions, and returns an approval status".

Include natural trigger phrases users would say, such as "fuzzy", "ambiguous", "unclear requirements", or "not sure what to decide" in the 'Use when' clause.

DimensionReasoningScore

Specificity

"Analyze underspecified requests with a short decision interview" names the domain and one concrete action (a decision interview), matching the anchor for 1-2 concrete actions without comprehensive coverage. It does not list several specific actions, ruling out 4, and the action is concrete rather than generic, ruling out 2.

3 / 5

Completeness

Both parts are explicit: what ("Analyze underspecified requests with a short decision interview") and when ("Use this skill when guessing would risk the wrong plan"). The 'when' clause is present but abstract rather than concrete trigger phrases, fitting anchor 4 rather than 5.

4 / 5

Trigger Term Quality

Terms like "underspecified requests", "guessing", and "wrong plan" are relevant but miss the natural phrases a user would actually say ("fuzzy request", "ambiguous", "unclear requirements", "clarify"). Some relevant keywords with missing synonyms fits anchor 3, not 4 which requires good coverage with only a few terms missing.

3 / 5

Distinctiveness Conflict Risk

The "short decision interview" niche with the trigger "when guessing would risk the wrong plan" is mostly distinct with only minor overlap risk against generic clarification or planning skills, fitting anchor 4. It is not 5 because "underspecified requests" is a broad condition several planning-adjacent skills could claim.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

jscraik/Agent-Skills

Path

Skills/product-strategy/interview-me/SKILL.md

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.