CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

interview

Aligns on a request's scope before planning — researches the codebase, surfaces unknowns, non-goals, and success criteria, asks batched clarifying questions only when research cannot resolve them, and writes a confirmed `brief.md`. Triggers on "align on scope", "interview me", "clarify the request", "/interview".

Quality

80%

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/analysis/interview/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-organized thin-index body with excellent phase sequencing and gate structure, undermined by a bundle that omits the entire `rules/` library it points to. As shipped, the skill can orient a run but cannot execute phases 0–4, since all procedural detail lives in files that are not present.

Suggestions

Ship the `rules/*.md` files in the bundle (or inline the per-phase procedures into SKILL.md) — six referenced rule files are absent, so phases 0–4 cannot actually be executed from the bundle as provided.

Consolidate the Workflow table and the 'Required reading by phase' table, which repeat the same phase-to-rule-file mapping and roughly double the navigation content.

Add a one-line summary of each rule file's key content (e.g., what the readiness-gate classification criteria are) so a run is not fully blocked when a rule file cannot be loaded.

DimensionReasoningScore

Conciseness

The body is a lean thin index that assumes Claude's competence — no concept explanations, tight tables, pointed principles. It falls short of anchor 5 because the Workflow table and the "Required reading by phase" table largely duplicate the same phase-to-file mapping.

4 / 5

Actionability

Concrete specifics are present inline (batched `AskUserQuestion` rounds of at most 2, artifact path `.agent/{branch}/brief.md`, verdict enum `ready | ready-with-assumptions | blocked`, an example question like "reuse `PrStatusCache` or add a cache?"), but the operative per-phase procedures are deferred entirely to `rules/*.md` files that are absent from the bundle, leaving key execution detail missing — worse than the minor gaps of anchor 4.

3 / 5

Workflow Clarity

Five phases are explicitly sequenced in a table, each with a named gate ("Do not advance until the gate passes"), the adaptive pass behavior is specified, and a Definition of Done checklist closes the loop — matching anchor 5's explicit validation/checkpoint structure. The skill writes no product code, so the destructive/batch validation cap does not apply.

5 / 5

Progressive Disclosure

The index design is exemplary — well-signaled, one-level-deep, load-on-demand references — but scored against the actual bundle, six of the seven referenced files (`rules/research-grounding.md`, `rules/readiness-gate.md`, `rules/consultative-completeness.md`, `rules/question-design.md`, `rules/brief-artifact.md`, `rules/aw-integration.md`) do not exist; only `references/interview-example.md` is present, so navigation from index to detail is broken for nearly every phase. Not score 3, because the problem is not unclear signaling but wholesale missing references that break the disclosure structure.

2 / 5

Total

14

/

20

Passed

Description

88%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: concrete, third-person, non-padded, with explicit trigger phrases and a clear what/when split. Its only weaknesses are a few missing natural trigger synonyms and slight overlap risk with adjacent planning skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "researches the codebase, surfaces unknowns, non-goals, and success criteria, asks batched clarifying questions only when research cannot resolve them, and writes a confirmed `brief.md`" — covering the skill's function comprehensively, matching the anchor-5 example.

5 / 5

Completeness

Both 'what' (research, surface, ask batched questions, write brief.md) and 'when' are answered explicitly with concrete quoted trigger phrases ("Triggers on 'align on scope', 'interview me', 'clarify the request', '/interview'"), matching the anchor-5 pattern; no missing 'Use when' clause.

5 / 5

Trigger Term Quality

Triggers "align on scope", "interview me", "clarify the request", "/interview" are phrases a user would naturally say, but common variations like "scope this", "define requirements", or "help me plan this" are missing, placing it between anchors 3 and 5.

4 / 5

Distinctiveness Conflict Risk

The pre-planning scope-alignment niche is distinct with dedicated triggers unlikely to fire for the wrong skill, but "clarify the request" carries minor overlap risk with general planning/requirements-elicitation skills.

4 / 5

Total

18

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 19 missing

Warning

Total

13

/

16

Passed

Repository

mthines/agent-skills

Path

skills/analysis/interview/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.