ask-questions-if-underspecified

Clarify requirements before implementing. Use when serious doubts arise.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

85%

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 clear sequencing and concrete templates; its only weakness is mild redundancy and generic boilerplate in the closing sections.

Suggestions

Trim the "Limitations" section by removing the generic validation/expert-review boilerplate that is not specific to this skill.

Merge "Anti-patterns" into "When NOT to Use" to eliminate the duplication of the "don't ask what you can discover" guidance.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and does not explain concepts Claude already knows, but the "Limitations" section contains generic boilerplate and "Anti-patterns" partly duplicates "When NOT to Use", so it could be tightened.	2 / 3
Actionability	It gives concrete, copy-paste-ready guidance: numbered question templates, a `1b 2a 3c` compact reply format, a `defaults` fast-path, and a full example block.	3 / 3
Workflow Clarity	The four-step workflow is clearly sequenced with an explicit pause-checkpoint (step 3) and a confirmation feedback loop when the user asks to proceed without answers (step 3/4).	3 / 3
Progressive Disclosure	The skill is self-contained with well-organized sections (When to Use, Workflow, Templates, Anti-patterns, Limitations) and no nested or external references, so no bundle structure is needed.	3 / 3
	Total	11 / 12 Passed

Description

67%

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 covers both what and when with an explicit trigger, but its single action and the unnatural "serious doubts arise" phrasing limit specificity and trigger quality.

Suggestions

Replace "serious doubts arise" with natural user phrasing such as "when a request is ambiguous or missing key details" to improve trigger term quality.

Name a couple of concrete actions (e.g., "identify missing scope, constraints, or acceptance criteria and ask targeted clarifying questions") to raise specificity.

Sharpen the trigger so it is less likely to fire for general planning tasks, improving distinctiveness.

Dimension	Reasoning	Score
Specificity	"Clarify requirements before implementing" names a domain (requirements) and one action (clarify), but does not list multiple specific concrete actions, so it is not comprehensive enough for a 3.	2 / 3
Completeness	It explicitly answers both "what" ("Clarify requirements before implementing") and "when" ("Use when serious doubts arise") with an explicit trigger clause, satisfying the 3 anchor.	3 / 3
Trigger Term Quality	"Use when serious doubts arise" provides a trigger clause, but "serious doubts arise" is not phrasing a user would naturally say, and no common variations are covered.	2 / 3
Distinctiveness Conflict Risk	The clarification niche is somewhat specific, but the "serious doubts arise" trigger is broad enough that it could still overlap with general reasoning or planning skills.	2 / 3
	Total	9 / 12 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Commit: 6b7501e

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.