ask-questions-if-underspecified
Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.
Install with Tessl CLI
npx tessl i github:Dicklesworthstone/pi_agent_rust --skill ask-questions-if-underspecified62
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is severely underdeveloped. It fails to specify what kind of requirements are being clarified, what domain or context it applies to, and provides no actionable trigger guidance beyond 'invoke explicitly.' The description would leave Claude unable to understand when this skill is appropriate even if explicitly requested.
Suggestions
Specify the domain and concrete actions (e.g., 'Gathers software requirements through structured questions about scope, constraints, and acceptance criteria').
Add explicit trigger terms users would naturally say (e.g., 'Use when user mentions requirements gathering, project scoping, feature specification, or asks to define what needs to be built').
Clarify what 'invoked explicitly' means by providing the exact phrase or command users should use to trigger this skill.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language ('Clarify requirements') without specifying concrete actions. It doesn't describe what kind of requirements, how clarification happens, or what domain this applies to. | 1 / 3 |
Completeness | The 'what' is extremely weak ('clarify requirements' is vague), and the 'when' only says 'when invoked explicitly' which provides no guidance on actual use cases or triggers. | 1 / 3 |
Trigger Term Quality | Contains no natural keywords users would say. 'Requirements' is generic and 'invoked explicitly' is technical jargon. Users wouldn't naturally say these terms when needing this skill. | 1 / 3 |
Distinctiveness Conflict Risk | The explicit invocation requirement reduces conflict risk somewhat, but 'clarify requirements' is generic enough to potentially overlap with many planning, scoping, or analysis skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill that demonstrates strong content quality across all dimensions. It provides actionable, concrete guidance with clear workflow steps and practical templates. The anti-patterns section adds value by explicitly stating what to avoid, and the entire skill respects token efficiency while remaining comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, with no unnecessary explanations of concepts Claude already knows. Every section serves a clear purpose, and the question templates are practical without being verbose. | 3 / 3 |
Actionability | Provides concrete, copy-paste ready question templates with specific formats (numbered questions, lettered options, reply formats). The workflow steps are explicit and the code block example shows exactly how to structure questions. | 3 / 3 |
Workflow Clarity | Clear 4-step sequence with explicit checkpoints: decide if underspecified → ask questions → pause before acting → confirm then proceed. Includes explicit validation (pause until answers arrive) and feedback loop (restate assumptions, get confirmation). | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections (Goal, Workflow, Question templates, Anti-patterns). Content is appropriately sized for a single file with no need for external references. Easy to scan and navigate. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- 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.