acceptance-criteria-creator
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill acceptance-criteria-creatorAcceptance Criteria Creator - Auto-activating skill for Enterprise Workflows. Triggers on: acceptance criteria creator, acceptance criteria creator Part of the Enterprise Workflows skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%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 when to select this skill over others, as it lacks concrete actions, natural trigger terms, and explicit guidance on when to activate.
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', or '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, the lack of detail about what it actually does could cause confusion with other requirements or documentation skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is essentially an empty placeholder with no actionable content. It describes what it claims to do in vague terms but provides zero actual guidance, examples, templates, or processes for creating acceptance criteria. The entire content could be replaced with a single sentence without losing any practical value.
Suggestions
Add a concrete template or format for acceptance criteria (e.g., Given/When/Then format, or a structured checklist)
Include 2-3 real examples showing input requirements transformed into well-written acceptance criteria
Define a clear workflow: 1) Identify user story, 2) Extract testable conditions, 3) Write criteria in standard format, 4) Validate completeness
Remove all generic boilerplate text ('provides automated assistance', 'follows best practices') and replace with specific, actionable instructions
| 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. | 1 / 3 |
Actionability | There is zero concrete guidance, no code examples, no specific steps, and no actual instructions for creating acceptance criteria. The content describes what the skill supposedly does without showing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill claims to provide 'step-by-step guidance' but contains no actual steps, sequences, or processes for creating acceptance criteria. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of marketing-style text with no structure for discovery. There are no references to detailed materials, examples, or templates that would actually help with acceptance criteria creation. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 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.