CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

interview

Use when the user wants to build or change something but the request is vague or open-ended: 'help me figure out what to build', 'I'm not sure what it should do', 'add X' with no details, or no clear definition of done. Runs a short Socratic interview that turns the idea into goals, constraints, and acceptance criteria before any code is written. Not for simple questions, small clear edits, or an existing Seed.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

77%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 body is exceptionally actionable and the multi-step workflow is clearly sequenced with explicit validation gates and error-recovery loops, which is impressive for a protocol of this complexity. Its weaknesses are redundancy (gates and fan-out rules stated multiple times) and monolithic structure — dense protocol detail is inlined in SKILL.md instead of split into reference files, with one reference (seed-closer.md) lacking a path or retrieval instruction.

Suggestions

Move the fan-out submission contract, data-measurement rules, and language-calibration levels into one or more reference files under references/, keeping a short summary plus a clearly signaled link in SKILL.md.

State each non-skippable gate once — either in the 'Non-Skippable Gates' section or in the corresponding numbered step — and cross-reference the other location instead of re-explaining the rules in both places.

Give seed-closer.md the same treatment as socratic-interviewer.md: an explicit path or a retrieval command so the closer lane's criteria are unambiguously reachable.

DimensionReasoningScore

Conciseness

Almost every sentence is operational (tool names, arguments, meta flags, prefixes) with no padding explaining concepts Claude already knows, but the ~226-line body carries real redundancy: the four gates are stated in "Non-Skippable Gates" and then re-explained in steps 4, 8, and 9, and the fan-out payload rules are restated across multiple long multi-clause paragraphs. This is more than the minor trimming of the level-4 anchor but well short of the padded explanations of level 2.

3 / 5

Actionability

Guidance is fully executable: copy-paste-ready MCP call blocks with exact argument names, a worked multi-section answer payload ("Decision: Stripe Billing..."), exact prefixes like [from-user][refined][closure], exact JSON lane-output schemas, an executable uvx one-liner, and an exact footer format — matching the copy-paste-ready level-5 anchor for an instruction-only skill.

5 / 5

Workflow Clarity

Path A is a clearly sequenced 9-step process with explicit validation checkpoints (Refine gate, Dialectic Rhythm Guard, Seed-ready Acceptance Guard, Restate gate) and genuine feedback loops for error recovery (retry at most 2 then fall back to Path B, restate correction loop capped at two rounds, invalid_result_entry correction path, initial_context_too_large resend protocol). No destructive or batch operations apply, so no cap is triggered.

5 / 5

Progressive Disclosure

No bundle files exist, and while the body has clear section headers, the ~226 lines inline dense protocol detail (the fan-out submission contract, data-measurement rules, language calibration levels) that belongs in separate reference files, and the seed-closer.md reference is dangling — cited with no path or retrieval instruction, unlike socratic-interviewer.md which specifies both. Structure is present and navigable (above level 2) but the inlining and unclear reference sit it at level 3 rather than 4.

3 / 5

Total

16

/

20

Passed

Description

82%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 what the skill does, when to use it with verbatim natural trigger phrases, and when not to use it. The only relative weakness is that it describes a single composite action rather than enumerating multiple specific capabilities.

DimensionReasoningScore

Specificity

The description names one concrete action — "Runs a short Socratic interview that turns the idea into goals, constraints, and acceptance criteria" — with concrete outputs, but does not list several distinct actions as the 4/5 anchors require; it is well above the generic level-2 anchor.

3 / 5

Completeness

It explicitly answers both questions with concrete trigger phrases: an explicit "Use when..." clause with quoted examples, a clear statement of what it does (Socratic interview producing goals, constraints, and acceptance criteria), and even explicit exclusions — a direct match for the level-5 anchor.

5 / 5

Trigger Term Quality

It quotes several natural phrases users would actually say ("help me figure out what to build", "I'm not sure what it should do", "add X" with no details, "no clear definition of done"), but misses common variations like "help me decide" or "define requirements", so it falls short of comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche (vague/open-ended build requests → interview → acceptance criteria) with distinct trigger phrases and an explicit exclusion clause ("Not for simple questions, small clear edits, or an existing Seed") that minimizes overlap with related skills.

5 / 5

Total

17

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

Q00/ouroboros

Path

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