CtrlK
BlogDocsLog inGet started
Tessl Logo

ask-questions-if-underspecified

Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.

55

Quality

62%

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 ./skills/ask-questions-if-underspecified/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 well-structured, concise, and highly actionable, with a clear gated workflow and concrete templates. Minor gains are available from trimming template redundancy and tightening the assumption-rejection recovery path.

DimensionReasoningScore

Conciseness

The body is tight and actionable with no padding or explanation of concepts Claude already knows; the only minor excess is slight redundancy between the workflow bullets and the question-templates block.

4 / 5

Actionability

It provides concrete, copy-paste-ready guidance: numbered questions, lettered multiple-choice options, a reply-format code block, and a 'reply defaults' fast-path, fully covering common cases for an instruction-only skill.

5 / 5

Workflow Clarity

A clear four-step sequence (decide → ask → pause → confirm) with explicit gating checkpoints and a proceed-with-assumptions confirmation loop; the only gap is an under-specified 'assumptions rejected' recovery path.

4 / 5

Progressive Disclosure

No bundle files exist and the content is self-contained with well-organized section headers (Goal, Workflow, Templates, Anti-patterns); it slightly exceeds the simple-skill line count threshold, keeping it just below 5.

4 / 5

Total

17

/

20

Passed

Description

42%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 states a clear objective but lacks a positive trigger clause and natural user-facing keywords, leaving its completeness and trigger quality mid-range. It is reasonably distinct but generic enough to risk overlap.

Suggestions

Add an explicit positive 'Use when...' clause (e.g., 'Use when a request is ambiguous or could be interpreted multiple ways') to raise completeness above 3.

Include natural trigger phrases users actually say, such as 'underspecified', 'ambiguous requirements', or 'not sure what you want', to improve trigger term quality.

Sharpen the niche by naming the specific scenario (e.g., 'before implementing a change with ambiguous scope') to reduce overlap with general assistant behavior.

DimensionReasoningScore

Specificity

"Clarify requirements before implementing" names the domain and one concrete action, but offers no broader set of actions; it sits between the minimal-action (2) and several-actions (4) anchors.

3 / 5

Completeness

It has a clear "what" (clarify requirements before implementing) but only a negative "when" ("Do not use automatically, only when invoked explicitly") with no positive "Use when..." trigger, which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

The phrasing is action-oriented rather than user-utterance-oriented; there are no natural keywords a user would actually say when needing this skill (e.g. "not sure what you want"), so only generic terms are present.

2 / 5

Distinctiveness Conflict Risk

Clarifying requirements is a broad meta-behavior with overlap risk against general-purpose skills; the "do not use automatically" clause bounds it somewhat but the niche is not sharply distinct.

3 / 5

Total

11

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
MoizIbnYousaf/ai-agent-skills
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.