CtrlK
BlogDocsLog inGet started
Tessl Logo

ask-questions-if-underspecified

Clarify requirements before implementing. Use when serious doubts arise.

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/ask-questions-if-underspecified/SKILL.md

The canonical home for this skill is ask-questions-if-underspecified in sickn33/agentic-awesome-skills

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 skill body is a tight, highly actionable gating workflow with explicit pause/confirm checkpoints and ready-to-use question templates. It is well-organized and self-contained with no wasted tokens.

DimensionReasoningScore

Conciseness

The body is well-sectioned with no padding over concepts Claude already knows; only minor instances (the dense options-formatting bullets) could be trimmed, matching anchor 4 (Efficient; minor instances of over-explanation that could be trimmed).

4 / 5

Actionability

Concrete copy-paste-ready templates and an explicit reply format (Reply with: defaults or 1a 2a) with a worked numbered/lettered code-block example cover the common cases, matching anchor 5; instruction-only guidance is fully actionable per the scoring notes.

5 / 5

Workflow Clarity

The four-step workflow has explicit validation checkpoints: step 3 gates all action until answers arrive and step 4 restates requirements before proceeding, with a confirmation feedback loop (state assumptions, ask confirm, proceed only after confirm), matching anchor 5.

5 / 5

Progressive Disclosure

No bundle files exist and the self-contained body is cleanly organized into When to Use / Not to Use / Goal / Workflow / templates / Anti-patterns sections, matching the well-organized-structure exception for simple skills at anchor 5.

5 / 5

Total

19

/

20

Passed

Description

45%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 pairs a what with a when but is thin on concrete capabilities and trigger terms, leaning on the abstract phrase serious doubts arise. It is serviceable but under-specified relative to the good examples.

Suggestions

Name concrete actions instead of one generic verb, e.g. Ask targeted clarifying questions, state assumptions, and confirm interpretation before implementing.

Broaden trigger terms to phrases users actually say, e.g. Use when a request is ambiguous, underspecified, or has multiple plausible interpretations.

Add an explicit Use when clause listing concrete triggers to lift completeness past the anchor-3 cap.

DimensionReasoningScore

Specificity

Clarify requirements before implementing names the domain (requirements clarification) but offers only a minimal, generic action with no concrete sub-actions, matching anchor 2 (Names the domain but actions are minimal or generic).

2 / 5

Completeness

The description states a clear what (clarify requirements) but the when (serious doubts arise) is weak and abstract rather than concrete trigger phrases, matching anchor 3 (clear what but when is missing or only weakly implied).

3 / 5

Trigger Term Quality

Use when serious doubts arise supplies one genuine trigger phrase but misses common variations users would naturally say (not sure, ambiguous, unclear), fitting anchor 3 (Some relevant keywords but missing common variations or synonyms).

3 / 5

Distinctiveness Conflict Risk

Clarify requirements before implementing carves out a narrow meta-skill niche but is generic enough to overlap with other planning or clarification skills, fitting anchor 3 (Somewhat specific but could still overlap with similar skills).

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
administrakt0r/AI-Agents-Safe-Coding-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.