CtrlK
BlogDocsLog inGet started
Tessl Logo

interview

Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.

54

Quality

61%

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 ./crates/tui/assets/skills/interview/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

The body is a model of brevity for a simple instruction-only skill, well-sectioned and free of unnecessary explanation. Its main weakness is actionability: the workflow is concrete in outline but lacks worked examples or fully specified guidance, and validation checkpoints are implicit.

Suggestions

Add one short worked example of a good single question and a resulting brief/spec to make the guidance copy-paste ready and lift actionability.

Add an explicit checkpoint, e.g. "Confirm the answer resolves the blocking decision before continuing", to give the workflow a validation step.

Tighten conditional phrases like "when possible" and "only when enough answers exist" into concrete, decisive criteria.

DimensionReasoningScore

Conciseness

The ~25-line body is lean and efficient with no padding and no explanation of concepts Claude already knows ("Use when the request lacks a material product or implementation choice", "One focused question at a time"), matching the score-3 anchor "Lean and efficient; assumes Claude's competence; every token earns its place"; it is not the slightly-padded score 2 and far from the verbose score 1.

3 / 3

Actionability

The numbered workflow gives concrete steps ("State the missing decision", "Offer concrete options", "Record the answer", "Produce a short brief/spec") but several are conditional/vague ("when possible", "only when enough answers exist") and there are no concrete examples of a good question or brief, matching score 2's "some concrete guidance but incomplete"; it lacks the copy-paste-ready specificity of score 3 and is well above the abstract score 1.

2 / 3

Workflow Clarity

Steps are clearly sequenced with a failure-mode branch ("If the user declines to answer, proceed with explicit assumptions and label them"), but there are no explicit validation checkpoints or feedback loops; for this non-destructive interview skill that gap does not strictly cap the score, yet it keeps it at score 2 rather than the checkpointed score 3, and above the unsequenced score 1.

2 / 3

Progressive Disclosure

This is a simple single-purpose skill under 50 lines with no need for external references, organized into clearly labeled sections (When to use, Non-goals, Workflow, Failure mode); per the simple-skills scoring note this warrants score 3, and it is not the under-organized score 2 nor the monolithic score 1.

3 / 3

Total

10

/

12

Passed

Description

50%

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 third-person and clearly communicates a narrow, distinctive intent (structured one-question interviews only when material choices are missing), with explicit "when" guidance. It is held back from top marks by abstract rather than comprehensive concrete actions and a lack of common natural trigger phrasings.

Suggestions

Add concrete, copyable trigger phrasings users naturally say, e.g. "Use when the user says 'clarify requirements', 'ask me', or 'what do you need from me'".

Expand the action list with specific concrete verbs (e.g. "Ask, record, summarize, produce a brief/spec") to lift specificity toward score 3.

Sharpen the what-clause into a crisp action list paired with the existing when-clause to fully satisfy both halves of completeness.

DimensionReasoningScore

Specificity

Names the domain and several actions ("Ask one useful structured question", "remember answers and produce a brief/spec") but does not list a comprehensive set of concrete actions, matching the score-2 anchor "Names domain and some actions, but not comprehensive"; it falls short of score 3's "multiple specific concrete actions" and is well above the vague score-1 anchor.

2 / 3

Completeness

It states both what (ask one question, record answers, produce a brief/spec) and when ("only when material product/implementation choices are genuinely missing", "Discoverable facts should be investigated"), with explicit trigger guidance; however the "what" is somewhat abstract rather than a crisp action list, so it sits at score 2 rather than the clearly-dual score 3, and is far above the missing-what-or-when score 1.

2 / 3

Trigger Term Quality

Relevant terms appear ("structured question", "product/implementation choices", "brief/spec", "investigated instead of asked") but common natural phrasings a user would actually say (e.g. "clarify requirements", "ask the user") are missing, matching score 2's "some relevant keywords but missing common variations"; not the full coverage of score 3 nor the jargon-only score 1.

2 / 3

Distinctiveness Conflict Risk

The structured-interview niche is reasonably specific (one question at a time, only for missing material choices) but could still overlap with general planning or clarification skills, matching score 2's "somewhat specific but could still overlap"; it is not the clear-distinct-trigger score 3 nor the generic-conflicting score 1.

2 / 3

Total

8

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
Hmbown/CodeWhale
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.