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
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 essentially a boilerplate template with no substantive content. It only states the skill's name and category without describing any concrete capabilities, use cases, or meaningful trigger terms. The duplicate trigger term and absence of a 'Use when...' clause make it nearly useless for skill selection among multiple options.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates structured acceptance criteria from user stories, creates Given/When/Then scenarios, and validates completeness of requirements.'
Add a 'Use when...' clause with natural trigger terms like 'acceptance criteria', 'user story', 'definition of done', 'requirements', 'BDD scenarios', 'given when then', 'story validation'.
Remove the duplicate trigger term and expand with varied natural language phrases users might actually say, such as 'write acceptance criteria', 'create AC for a ticket', or 'define done criteria'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Acceptance Criteria Creator') and its category ('Enterprise Workflows') but does not describe any concrete actions like 'generates acceptance criteria from user stories' or 'creates Given/When/Then scenarios'. No specific capabilities are listed. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of what the skill actually does beyond its name, and no explicit 'Use when...' clause with meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just 'acceptance criteria creator' repeated twice. There are no natural keyword variations a user might say, such as 'user story', 'requirements', 'definition of done', 'given when then', 'BDD', or 'story criteria'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'acceptance criteria' is somewhat specific to a particular domain (agile/product management), which provides some distinctiveness. However, the lack of detail about what it actually does and the generic 'Enterprise Workflows' category could cause overlap with other enterprise or agile-related 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 an empty shell with no substantive content. It repeatedly references 'acceptance criteria creator' without ever defining what acceptance criteria are, how to write them, what format to use, or providing any concrete examples or templates. It reads as an auto-generated placeholder that provides zero value to Claude.
Suggestions
Add concrete acceptance criteria templates and formats (e.g., Given/When/Then BDD syntax, checklist format) with complete examples showing input user stories mapped to output acceptance criteria.
Include a clear workflow: e.g., 1) Parse the user story, 2) Identify testable conditions, 3) Write criteria in specified format, 4) Validate criteria against INVEST principles or a completeness checklist.
Remove all generic filler sections (Purpose, When to Use, Example Triggers, Capabilities) that describe the skill meta-information rather than providing actionable instructions.
Add at least one fully worked example showing a real user story transformed into a set of acceptance criteria, so Claude has a concrete pattern to follow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic filler that tells Claude nothing useful. It explains what triggers the skill, restates the skill name repeatedly, and provides no actual domain knowledge or instructions that Claude doesn't already know. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no examples of acceptance criteria formats, no templates, no specific steps. Every section is vague and abstract, describing rather than instructing. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. The skill claims to provide 'step-by-step guidance' but contains no steps, no sequence, and no validation checkpoints for creating acceptance criteria. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic placeholder text with no references to detailed materials, no linked resources, and no meaningful structural organization beyond boilerplate headings. | 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
4dee593
- 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.