CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

59

Quality

68%

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

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 body is lean, well-structured, and highly actionable with three executable examples and concrete anti-patterns. Main improvements are consolidating the repeated 'no prose-question path' / allow_other guidance and showing return-value handling in code rather than prose.

DimensionReasoningScore

Conciseness

Lean and assumes Claude's competence (no explaining what a CLI picker is), but the 'no prose-question path' line and the free-form + allow_other guidance are restated across When-to-call, Habits, and Anti-patterns and could be tightened.

4 / 5

Actionability

Three complete, copy-paste-ready Python examples (single-select with recommendation, allow_other confirmation, multi-select) plus concrete habits and anti-patterns; minor gaps in that the full parameter schema and return-value handling are shown in prose rather than code.

4 / 5

Workflow Clarity

Single-purpose skill with a clear conceptual sequence (when to call → habits → examples → anti-patterns) and explicit guardrails (treat the returned value as authoritative; don't re-ask; no approval gate between documents), with only minor validation-gap touches keeping it below 5.

4 / 5

Progressive Disclosure

No bundle files exist; the ~100-line body is well-organized with clear section headers and no nested references, appropriate for a self-contained single-purpose skill, though some repeated guidance could be consolidated.

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 is specific and clearly niched around ask_user_question, but lacks an explicit 'Use when...' trigger clause and relies on the tool name rather than natural user phrasings. Strengthening the when-guidance and adding natural trigger synonyms would raise completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when ...' clause naming natural operator phrasings (e.g., 'Use when interviewing the operator, confirming a yes/no, or picking engagement type, attack class, scope window, or posture').

Include common natural synonyms beyond the tool name — 'structured questions', 'picker prompts', 'operator interview', 'multiple-choice confirmations' — to improve trigger-term coverage.

Briefly enumerate the other concrete capabilities (multi_select, recommended-option marking) so the 'what' coverage is comprehensive.

DimensionReasoningScore

Specificity

Names the tool, its single-channel role, and a concrete capability ("free-form fields via allow_other=true") — several specific actions with minor gaps, but not comprehensive coverage of multi_select/recommendation marking.

4 / 5

Completeness

Clearly states what ("How to use ask_user_question — the single operator-input channel") but the when is only weakly implied ("for every interview question") with no explicit 'Use when...' clause, which caps completeness at 3.

3 / 5

Trigger Term Quality

Contains relevant keywords ("interview question", "operator-input", "ask_user_question") but leans on the internal tool name rather than natural user phrasings, missing common variations.

3 / 5

Distinctiveness Conflict Risk

Targets a specific named tool and a clear niche (the single operator-input channel for interview questions), giving it distinct triggers with minimal conflict risk.

5 / 5

Total

15

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
PurpleAILAB/Decepticon
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.