CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

eliciting

Interviewing the USER about their operation. Use before asking a substantive question, consulting a source, handling a correction or conflict, pinning down a quantity, or deciding the account is enough. Not for changing the net; that is `modelling`.

60

Quality

75%

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 ./apps/brunch-agent/src/agents/petrinaut/skills/eliciting/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 tightly written, jargon-consistent operational guide with concrete example questions, a diagnostic failure-mode section, and a verification-oriented closing, scoring uniformly at the 'good with minor gaps' level. Its main deductions are the redundant generic questioning-styles section and occasional principle-level phrasing instead of concrete steps.

DimensionReasoningScore

Conciseness

The body is dense with no padding and assumes Claude's competence throughout, but the 'Questioning styles' section re-explains standard interview types (open-ended, closed-ended, hypothetical, reflective, comparative) Claude already knows, which is trimmable.

4 / 5

Actionability

An instruction-only skill with largely concrete, executable guidance: quoted example questions, a cue-to-suspect-to-ask table, and a precise quantity protocol ('nine times in ten, under how long?'). A few sections remain at the principle level ('Ask the question whose answer could most change what the model will answer') rather than concrete steps.

4 / 5

Workflow Clarity

A clear phase progression (early breadth, later unmet needs) is paired with an explicit error-recovery section ('When the interview goes wrong': symptom to corrective move) and a closing read-back verification. Minor gaps remain, e.g. when to transition from mapping to the closing read-back is implied rather than checkpointed.

4 / 5

Progressive Disclosure

A single-file skill with no bundle and consistently well-organized, clearly headed sections covering choosing questions, moves, cues, quantities, failure modes, length levels, and closing. At ~85 lines it exceeds the under-50-line simple-skill case, and the cue table or interview-length details could arguably live in references, keeping it just below a 5.

4 / 5

Total

16

/

20

Passed

Description

62%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 has a strong, explicit 'when' section with multiple triggers and a rare negative boundary, but the 'what' is a single generic clause and the vocabulary leans on internal jargon ('the account', 'the net') that external users would not say. Overall solid but with clear room to sharpen the capability statement and natural trigger terms.

Suggestions

State what the interview produces or covers, e.g. 'Interviewing the USER about their operation: walking real cases, probing vague claims, resolving conflicts, and pinning down quantities' instead of the single generic clause.

Replace or gloss internal jargon in the description ('the account', 'the net') with natural user-facing terms, since trigger matching depends on phrases a user would actually say.

Add natural trigger synonyms such as 'interview me', 'gather requirements', or 'ask about my process' to broaden keyword coverage.

DimensionReasoningScore

Specificity

The only stated action is the generic 'Interviewing the USER about their operation'; the concrete interview moves the skill actually contains (walking cases, premortems, contrasts) never appear, so it names the domain with minimal actions but gains some concreteness from its trigger situations.

3 / 5

Completeness

Both 'what' and 'when' are present, with an unusually explicit multi-trigger 'when' clause plus a negative boundary ('Not for changing the net; that is modelling'). It falls below anchor 5 because the 'what' is a single thin clause with no stated outcome or scope.

4 / 5

Trigger Term Quality

Some semi-natural phrases ('asking a substantive question', 'correction or conflict', 'pinning down a quantity') are present, but internal jargon ('the account', 'the net', 'modelling') dominates and common user phrasings like 'interview me' or 'ask about my process' are missing.

3 / 5

Distinctiveness Conflict Risk

The explicit exclusion of the sibling skill ('Not for changing the net; that is modelling') carves a clear niche, leaving only minor overlap risk from the broad 'before asking a substantive question' trigger.

4 / 5

Total

14

/

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

hashintel/hash

Path

apps/brunch-agent/src/agents/petrinaut/skills/eliciting/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.