CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

interview-spec

Deep-dive interview to flesh out a spec or design document

Quality

70%

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

Quality

Content

75%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 content is a tight, well-structured instruction-only skill: the workflow is clearly sequenced with concrete tool directives and useful domain checklists, and there is no padding or explanation of known concepts. The main improvement opportunities are a sample question with option formatting and an explicit verification step before writing the completed spec back.

Suggestions

Include one worked example of a good interview question with 2-3 pre-determined options that represent real tradeoffs, so the "well-crafted options" standard is concrete rather than described.

Add a final verification checkpoint before writing back: re-read the synthesized spec against the interview answers to confirm every critical decision is captured, mirroring the validate-before-write pattern the rubric rewards.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: it never explains concepts Claude already knows, and lists like "Data models, API contracts, state management, concurrency, caching, validation" add domain-specific probing targets rather than padding. A few lines (e.g., "Don't ask about things that are already clearly specified") restate defaults Claude would apply anyway, keeping it just below the fully lean anchor.

4 / 5

Actionability

The guidance is concrete and executable for an instruction-only skill: "identify the 3-5 most critical unknowns", "Use the AskUserQuestion tool with well-crafted options", "Ask 2-4 questions at a time", and "Write the completed spec back to the file". The minor gap is the absence of a worked example showing what a well-crafted question with tradeoff options looks like.

4 / 5

Workflow Clarity

A clear five-step sequence (determine the document → read → analyze → interview → write back) is paired with a numbered interview flow, question batching, and an explicit uncertainty checkpoint ("Ask the user if unclear"). The operation is not destructive or batch, so no validation cap applies; it falls short of 5 only because there is no checkpoint verifying the rewritten spec against the gathered answers before writing back to the file.

4 / 5

Progressive Disclosure

With no bundle files present, the body itself is the entire skill and is well-organized under clear section headers (Question Quality, Question Strategy, Topics to Explore, Interview Flow, Output) with no content that clearly belongs in a separate file. It narrowly misses the level-5 exception for sub-50-line skills since the body runs ~58 lines and the topic matrix would be the natural candidate to externalize if the skill grows.

4 / 5

Total

16

/

20

Passed

Description

50%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 communicates the skill's core purpose clearly and in third person, but it is minimal: one action, no trigger guidance, and no coverage of what the skill actually does end-to-end. It would benefit most from an explicit "Use when..." clause and an enumeration of its concrete capabilities.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to flesh out, refine, or complete a specification, PRD, or design document through an interactive Q&A."

Enumerate the concrete capabilities so the description covers the full scope: analyzing the document for gaps and ambiguities, asking tradeoff-based questions with pre-determined options, and rewriting the completed spec back to the file.

Include natural synonyms users would say ("specification", "requirements doc", "PRD", "design doc") to improve trigger matching and distinctiveness against generic writing/review skills.

DimensionReasoningScore

Specificity

"Deep-dive interview to flesh out a spec or design document" names the domain and one action (interview to flesh out), but does not enumerate the skill's concrete capabilities such as gap analysis, optioned questions, or rewriting the document. It sits at the anchor for domain plus 1-2 concrete actions rather than the level-2 purely generic anchor or the level-4 multi-action list.

3 / 5

Completeness

The description answers "what" (conducts a deep-dive interview to flesh out a spec) but contains no "Use when..." clause or equivalent trigger guidance, which the rubric caps at 3. It is not a 4 because the "when" is entirely absent rather than merely implicit.

3 / 5

Trigger Term Quality

Terms like "interview", "spec", and "design document" are relevant, but common variations users would naturally say ("specification", "requirements", "PRD", "flesh out") are missing. This matches the anchor for some relevant keywords with missing synonyms, below the good-coverage anchor.

3 / 5

Distinctiveness Conflict Risk

"Spec or design document" plus "interview" carves a recognizable niche, but these terms are broad and could overlap with spec-writing, review, or documentation skills, and no distinct trigger phrases differentiate it. Somewhat specific but still overlapping, matching the level-3 anchor.

3 / 5

Total

12

/

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

LibPDF-js/core

Path

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