CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

structured-questions

How to use ask_user_question — the single operator-input channel for every interview question, including free-form fields via allow_other=true.

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 ./packages/decepticon/decepticon/skills/standard/soundwave/structured-questions/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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 a strong, example-driven reference: executable code for the main question types, concrete habits, and anti-patterns with a clear authority rule for returned answers. The only notable weakness is redundancy — the allow_other free-text-fallback behavior is restated in nearly every section and could be stated once.

Suggestions

State the allow_other=true free-text-fallback behavior once (e.g., in the tool intro) and simply reference it elsewhere; the current body repeats it ~5 times across When-to-call, Habits, the free-form bullet, and Anti-patterns.

Add a compact code example for a free-form field (organization / IP range) using 2-3 plausible guesses + allow_other=true, since that case is currently described only in prose.

DimensionReasoningScore

Conciseness

The body is mostly tight and actionable, but the 'set allow_other=true and the picker appends a free-text fallback' explanation is repeated roughly five times (intro, 'When to call', free-form bullet, Habits, Anti-patterns). This fits 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than level 2, since no section explains concepts Claude already knows.

3 / 5

Actionability

Three complete, copy-paste-ready ask_user_question examples cover the common cases (single-select with recommendation, confirmation with allow_other, multi-select), and concrete rules are given (header ≤ 12 chars, trailing ' (Recommended)', multi_select=true). This matches 'fully executable; copy-paste ready code; specific examples cover the common cases'.

5 / 5

Workflow Clarity

This is a single-purpose skill whose one action is unambiguous ('EVERY operator-facing question goes through the tool with 2-6 options + allow_other=true'), with an explicit post-answer checkpoint ('treat the returned value as authoritative; record it and move to the next dimension') and anti-patterns covering failure modes. The destructive/batch validation cap does not apply, and the simple-skill exception holds: the single action is unambiguous.

5 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent) and none are needed; the ~100-line body is self-contained, well-sectioned, and every piece of guidance belongs inline. It cannot be level 4's 'minor organization gaps' case because nothing warrants splitting into a separate file.

5 / 5

Total

18

/

20

Passed

Description

57%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 identifies a distinct, well-scoped niche tied to one tool, but reads as a scope statement rather than a trigger-rich description. It lacks an explicit 'Use when...' clause and natural trigger synonyms, capping completeness and trigger-term quality at the midpoint.

Suggestions

Append an explicit 'when' clause, e.g., 'Use when interviewing the operator, asking a yes/no confirmation, picking engagement type or OPSEC level, multi-selecting kill-chain phases, or collecting a free-form name / IP / contact.'

Include natural user-facing synonyms such as 'ask the operator', 'picker', and 'multiple-choice question' so the description matches how users actually phrase the need.

Name one or two more concrete capabilities (e.g., 'mark the recommended option', 'multi-select with multi_select=true') to lift specificity beyond the midpoint.

DimensionReasoningScore

Specificity

The description names the tool ('ask_user_question') and one concrete capability ('including free-form fields via allow_other=true'), but does not enumerate several specific actions. It matches 'names domain and 1-2 concrete actions, but not comprehensive' better than the level-4 anchor, which requires several listed actions with only minor gaps.

3 / 5

Completeness

The 'what' is clear ('the single operator-input channel for every interview question'), but there is no 'Use when...' clause or equivalent explicit trigger guidance in the description itself — the guideline caps completeness at 3 for this. It is not level 2 because the 'what' is concrete, not vague.

3 / 5

Trigger Term Quality

Relevant keywords are present ('ask_user_question', 'interview question', 'operator input', 'free-form fields') but common natural variations are missing (e.g., 'ask the operator', 'picker', 'multiple choice', 'confirmation question'). This fits 'some relevant keywords but missing common variations or synonyms' rather than level 4's 'good keyword coverage'.

3 / 5

Distinctiveness Conflict Risk

The description is anchored to a single uniquely-named tool ('ask_user_question') and a clear niche ('the single operator-input channel'), giving distinct triggers with minimal conflict risk against other skills. It does not fall to level 4 because no meaningful overlap risk exists.

5 / 5

Total

14

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

PurpleAILAB/Decepticon

Path

packages/decepticon/decepticon/skills/standard/soundwave/structured-questions/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.