acceptance-criteria-creator
Acceptance Criteria Creator - Auto-activating skill for Enterprise Workflows. Triggers on: acceptance criteria creator, acceptance criteria creator Part of the Enterprise Workflows skill category.
36
Quality
3%
Does it follow best practices?
Impact
97%
0.98xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/20-enterprise-workflows/acceptance-criteria-creator/SKILL.mdQuality
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, essentially only providing the skill name and category without any substantive information about capabilities or usage triggers. It fails to help Claude understand what the skill does or when to select it, making it nearly useless for skill selection among multiple options.
Suggestions
Add specific actions the skill performs, e.g., 'Generates acceptance criteria from user stories, formats criteria in Given/When/Then syntax, validates completeness against definition of done standards'
Include a 'Use when...' clause with natural trigger terms like 'user story', 'requirements', 'AC', 'definition of done', 'agile', 'sprint planning', 'feature specification'
Remove the redundant duplicate trigger term and replace with varied natural language users would actually use when needing this skill
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Acceptance Criteria Creator') without describing any concrete actions. There are no specific capabilities listed like 'generates acceptance criteria from user stories' or 'formats criteria in Given/When/Then syntax'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no 'when should Claude use it' guidance. The 'Triggers on' section just repeats the skill name rather than describing use cases. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('acceptance criteria creator' listed twice) and represent the skill name rather than natural user language. Missing terms users would actually say like 'user story', 'requirements', 'definition of done', 'AC', or 'agile'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'acceptance criteria' is somewhat specific to agile/product development contexts, which provides some distinctiveness. However, without concrete actions or clear triggers, it could still conflict with general requirements or documentation skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially an empty placeholder that describes what it claims to do without actually doing it. It contains no actionable content for creating acceptance criteria - no formats, templates, examples, or concrete guidance. The entire content is self-referential boilerplate that wastes tokens explaining trigger phrases rather than teaching the actual skill.
Suggestions
Add concrete acceptance criteria formats with examples (e.g., Given/When/Then, user story format, checklist format) with actual sample criteria
Include a step-by-step workflow for creating acceptance criteria: gather requirements → identify scenarios → write criteria → validate completeness
Provide executable templates or structured formats that Claude can immediately use to generate acceptance criteria
Remove all meta-description content ('This skill activates when...', 'Provides step-by-step guidance...') and replace with actual instructional content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need explained. | 1 / 3 |
Actionability | There is zero concrete guidance on how to actually create acceptance criteria. No examples of acceptance criteria formats, no templates, no specific steps or commands - just abstract descriptions of what the skill supposedly does. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. The skill claims to provide 'step-by-step guidance' but contains no actual steps. There's no process for creating acceptance criteria, no validation checkpoints, nothing actionable. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no actual instructional content to organize. There are no references to detailed materials, examples, or templates that would help with the task. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
0c08951
- 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.