CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

guided-interview

Conduct a structured, one-question-at-a-time interview to explore a specific topic or decision — each question offers 3-4 concrete, mutually exclusive options plus a free-text path, and later questions adapt to prior answers rather than following a fixed script. Ends with a recap the user confirms before finalizing, and only then produces a synthesized answer or (when the interview clearly feeds downstream work) a written brief. NOT for open-ended ambiguity-surfacing (use socratic-method) or single-fact lookups.

Quality

81%

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

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.

A well-structured, highly actionable instruction skill: a numbered protocol with explicit recap-confirmation checkpoints, feedback loops for mid-interview recovery, BAD/GOOD examples, and clean one-level-deep references to real files. The main weaknesses are moderate redundancy (the one-question rule and mindset material repeated across sections) and a pseudo-executable 'Quick diagnostic' bash snippet that reads as runnable but is not.

Suggestions

Remove or rewrite the 'Quick diagnostic' section — 'echo "$USER_PROMPT" | head -c 200' is not executable ($USER_PROMPT undefined) and its comment falsely claims the command 'Returns interview or answer-directly'; replace with a one-line prose heuristic or delete it.

Trim redundancy: the one-question-per-turn rule appears in Protocol step 2, NEVER rule #1, and Verification; consolidate or cut the 'Mindset' section, which restates the intro rather than instructing.

Consider moving the six NEVER rules with WHY/BAD/GOOD detail into a reference file (alongside question-design.md) to reduce main-file token load, keeping only the rule headlines inline.

DimensionReasoningScore

Conciseness

Mostly efficient, but includes unnecessary material: the 'Mindset' section is explanatory rather than instructional ('The interview is not a checklist to complete — it is a chain of decisions'), the opening paragraph restates the description, the one-question rule is stated three times (Protocol step 2, NEVER rule #1, and Verification), and the 'Quick diagnostic' bash block adds little. Matches the level-3 anchor of mostly efficient with some unnecessary explanation; not level 4 given the number of trims available.

3 / 5

Actionability

For an instruction-only skill the guidance is highly actionable: a numbered 7-step protocol, concrete tool direction ('Use the AskUserQuestion tool for a single question at a time'), literal example opening text, BAD/GOOD contrast pairs, and a troubleshooting table. Minor gap: the 'echo "$USER_PROMPT" | head -c 200' block is presented as a runnable diagnostic but is not executable as written, and its comment claiming it 'Returns interview or answer-directly' is inaccurate. Matches level 4, not level 5, due to that pseudo-executable snippet.

4 / 5

Workflow Clarity

The protocol is a clearly sequenced 7-step workflow with explicit validation checkpoints ('Do not proceed past this point on an unconfirmed recap', 'could I write the recap right now without guessing?') plus feedback loops for error recovery (contradiction handling, scope drift, user override) and a closing Verification checklist. This matches the level-5 anchor of clear sequence with explicit validation and error-recovery loops; not level 4 since checkpoints are explicit rather than minor-gapped.

5 / 5

Progressive Disclosure

The body appropriately splits detail into two existing, one-level-deep references, each clearly signaled with its content summarized ('question-design.md — the 3-4 rule, what makes an option concrete, and when to stop asking'; 'worked-example.md — a fully annotated interview from opening question through recap and confirmation'), with no nested references. Matches the level-5 anchor of a clear overview with well-signaled one-level-deep references; not level 4 since there are no buried or misdirected references.

5 / 5

Total

17

/

20

Passed

Description

75%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 highly specific, well-differentiated description that details the interview mechanics (option counts, adaptation, recap confirmation) and explicitly scopes against socratic-method and single-fact lookups. Its main weakness is the absence of a positive 'Use when...' trigger clause — applicability is conveyed only through purpose and negative scoping, capping completeness.

Suggestions

Add an explicit positive trigger clause, e.g. 'Use when the user asks to be interviewed, walked through a decision, or says help me figure out a topic with enumerable choices' — the current description only states what it is NOT for.

Include common natural phrasings users would actually say ('requirements gathering', 'ask me one question at a time', 'walk me through this decision') to strengthen trigger-term coverage.

Optionally name the downstream artifacts it feeds (plan, ticket, design doc, brief) as trigger nouns, since those are the situations where the skill applies.

DimensionReasoningScore

Specificity

Multiple concrete actions comprehensively cover the skill's behavior: 'Conduct a structured, one-question-at-a-time interview', 'each question offers 3-4 concrete, mutually exclusive options plus a free-text path', 'later questions adapt to prior answers', 'Ends with a recap the user confirms before finalizing', 'produces a synthesized answer or...a written brief'. No coverage gaps visible, matching the level-5 anchor rather than level 4's 'minor gaps'.

5 / 5

Completeness

The 'what' is clear and detailed, but there is no positive 'Use when...' clause; the 'when' is only weakly implied by purpose ('to explore a specific topic or decision') and by negative scoping ('NOT for open-ended ambiguity-surfacing...or single-fact lookups'). Per the guideline that a missing 'Use when...' clause or equivalent explicit positive trigger guidance caps completeness at 3.

3 / 5

Trigger Term Quality

Good natural keywords are present ('interview', 'one-question-at-a-time', 'topic or decision', 'recap', 'brief'), but common user phrasings like 'requirements gathering', 'walk me through a decision', 'help me figure out', or 'ask me questions' are missing — matching the level-4 anchor of good coverage with a few natural terms missing rather than level 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Clear niche with explicit disambiguation from the nearest neighbor skill: 'NOT for open-ended ambiguity-surfacing (use socratic-method) or single-fact lookups'. This matches the level-5 anchor of a clear niche with distinct triggers and minimal conflict risk.

5 / 5

Total

17

/

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

pantheon-org/tekhne

Path

skills/agentic-harness/guided-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.