CtrlK
BlogDocsLog inGet started
Tessl Logo

ask-questions-if-underspecified

Clarify requirements before implementing. Use when serious doubts arise.

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

78%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 well-structured, actionable instruction skill with a clear workflow and confirmation checkpoints, avoiding concept padding. It could be tightened slightly in its formatting prescriptions and made more concrete in a few abstract directives.

Suggestions

Condense the question-formatting guidance (lines 40-46) into a shorter list; the bolding/code-block tagging detail is over-prescriptive.

Add one concrete error-recovery checkpoint, e.g. 'If answers contradict each other or reveal new ambiguity, ask a follow-up before proceeding'.

Replace abstract directives like 'eliminate whole branches of work' with a brief concrete example of a branch-eliminating question.

DimensionReasoningScore

Conciseness

The body is directive and assumes Claude's competence without explaining basic concepts, though the question-formatting sub-bullets (bolding, code-block tagging) are mildly over-prescriptive and could be trimmed, fitting the 4 anchor.

4 / 5

Actionability

Concrete question templates and a copy-paste reply-format example provide actionable guidance, but some instructions stay abstract ('Ask 1-5 questions', 'eliminate whole branches of work'), leaving minor gaps versus the fully executable 5 anchor.

4 / 5

Workflow Clarity

The four-step workflow is clearly sequenced with confirmation checkpoints (pause before acting, restate and confirm assumptions), but it lacks an explicit error-recovery feedback loop, matching the 4 rather than 5 anchor.

4 / 5

Progressive Disclosure

Content is organized into clearly labeled sections (When to Use, When NOT to Use, Goal, Workflow, Templates, Anti-patterns, Limitations) with no nested references and no need for external files, giving easy navigation appropriate to a single-file instruction skill.

5 / 5

Total

17

/

20

Passed

Description

46%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 correctly states both what the skill does and when to use it, avoiding fluff and verbosity. Its main weakness is generic trigger language and a single vague action that limits specificity and naturalness.

Suggestions

Add concrete trigger phrases users actually say, e.g. 'Use when a request is ambiguous, has multiple plausible interpretations, or lacks clear scope/constraints'.

List 1-2 more specific actions beyond 'Clarify requirements', such as 'Ask a small numbered set of must-have questions with defaults'.

Tighten the 'when' clause from 'serious doubts arise' to concrete underspecification signals to reduce overlap with general reasoning skills.

DimensionReasoningScore

Specificity

The phrase 'Clarify requirements before implementing' names the domain but offers only a single, fairly generic action, matching the 'minimal or generic' anchor rather than the multi-action anchor at 3.

2 / 5

Completeness

Both 'what' ('Clarify requirements before implementing') and 'when' ('Use when serious doubts arise') are present and explicit, but the 'when' clause is somewhat vague and lacks concrete trigger phrases, fitting the 4 rather than 5 anchor.

4 / 5

Trigger Term Quality

'Use when serious doubts arise' supplies one generic trigger; 'serious doubts' is not a phrase users naturally say, so it misses the natural keyword coverage of the higher anchors.

2 / 5

Distinctiveness Conflict Risk

The clarification niche is somewhat specific, but 'serious doubts arise' is broad enough to overlap with general reasoning or planning skills, matching the 'somewhat specific but could still overlap' anchor.

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
sickn33/antigravity-awesome-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.