intent
Turn rough ideas into clear work orders before planning or building. Use when request is vague like "add a button", "make it better", "fix the thing". Triggers on ambiguous or underspecified requests. Produces a brief with scope, acceptance criteria, and stop conditions.
95
100%
Does it follow best practices?
Impact
76%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
100%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 is a strong skill description that clearly communicates its purpose, triggers, and outputs. It excels at providing natural language examples of when it should be triggered and specifies concrete deliverables. The description is concise without being vague, and it carves out a distinct niche in the skill selection process.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Turn rough ideas into clear work orders', 'Produces a brief with scope, acceptance criteria, and stop conditions.' These are concrete, well-defined outputs. | 3 / 3 |
Completeness | Clearly answers both what ('Turn rough ideas into clear work orders', 'Produces a brief with scope, acceptance criteria, and stop conditions') and when ('Use when request is vague like...', 'Triggers on ambiguous or underspecified requests') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent natural trigger terms that users would actually say: 'add a button', 'make it better', 'fix the thing', plus meta-terms like 'vague', 'ambiguous', 'underspecified'. These closely match real user language patterns. | 3 / 3 |
Distinctiveness Conflict Risk | Occupies a clear niche as a pre-planning clarification/scoping skill. The trigger on vague/ambiguous requests is distinct from skills that actually build or plan, and the output (brief with scope, acceptance criteria, stop conditions) is unique. | 3 / 3 |
Total | 12 / 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 provides a tight, actionable workflow for requirements clarification. It excels at being concise while maintaining specificity — concrete limits on questions, word counts, and clear gating between steps. The design principles at the top (testable criteria, grounded assumptions over invented ones) set strong guardrails without being verbose.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every sentence carries weight. No unnecessary explanations of what clarification is or why it matters beyond the opening principle statements, which are sharp and useful. The skill assumes Claude's intelligence throughout. | 3 / 3 |
Actionability | Each step has concrete, specific instructions: exact question limits (3 per round, max 8 rounds), word count constraints (≤35 words), specific tool usage (AskUserQuestion with multiSelect), and a precise output structure with named sections. The guidance is immediately executable. | 3 / 3 |
Workflow Clarity | Six clearly sequenced steps with explicit validation checkpoints: the unknowns list check between steps 2-3, the echo confirmation loop in step 3, the assumptions review gate in step 4, and the explicit prerequisite that steps 4-5 must complete before step 6. Feedback loops are well-defined (revise→re-echo, fix→re-validate unknowns). | 3 / 3 |
Progressive Disclosure | For a skill of this size (~50 lines), the content is well-organized with clear section headers and a logical flow. No external references are needed, and the structure naturally progresses from understanding to output. The brief template at the end serves as a clear reference without bloating the main workflow. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- saadshahd/moo.md
- Commit
e876ef5
- 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.