CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

acceptance-writer

Gera critérios de aceite Given/When/Then para requisitos funcionais. Inclui happy path, edge cases e falhas.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/workflow/acceptance-writer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A compact, well-structured instruction skill with a clear purpose, concrete rules, and a coherent multi-step process with a vagueness-handling checkpoint. Its main weaknesses are the absence of a fully worked example acceptance criterion and a small amount of redundant restatement of the coverage categories.

Suggestions

Add one fully worked example in the Template section, e.g. "AC-FR-001-01: Given a registered user with a valid token, When they request their profile, Then the system returns the profile data with 200" — so the output format is unambiguous on first use.

Consolidate the happy-path/failure/edge-case coverage counts into a single place (Rules) and reference it from Purpose/Template to remove the triple restatement.

Add a final verification step to the Process, e.g. "Step 3 — Review all criteria against Rule 2 (testable, unambiguous) before writing the output file", closing the validation gap.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence (it never explains what Given/When/Then is), but the happy/failure/edge-case coverage is restated three times across Purpose ("Happy path + edge cases + failure modes"), Rules ("1 happy path scenario, 2 failure scenarios, 2 edge cases"), and the Template, which is minor trimmable redundancy rather than the 'every token earns its place' level.

4 / 5

Actionability

Concrete, executable guidance throughout: the AC-<FR-ID>-NN naming convention, an enumerated scenario-category checklist, the hard coverage rule, the output file path, and a vagueness protocol (OQ-xxx, PROVISIONAL marking). The minor gap is that no fully worked example of a written Given/When/Then criterion is shown, keeping it below fully copy-paste-ready guidance.

4 / 5

Workflow Clarity

A clearly sequenced process (Step 0 normalize FRs → Step 1 write scenarios per FR → Step 2 add test strategy notes) with a genuine checkpoint in Step 0 (flag vagueness, open an OQ, mark criteria PROVISIONAL). It falls short of level 5 only because there is no final verification pass confirming the generated criteria satisfy Rule 2's testability/unambiguity requirement.

4 / 5

Progressive Disclosure

The skill is under 50 lines, requires no external references (no references/, scripts/, or assets/ directories exist), and is cleanly organized into well-labeled sections (Purpose, When to Use, Inputs, Output Files, Rules, Process, Template), which per the rubric's simple-skill guideline merits a 5.

5 / 5

Total

17

/

20

Passed

Description

53%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description states a concrete, third-person capability with a clear output format, but it omits any "when to use" guidance and only partially covers the natural trigger terms users might say. Adding an explicit use-when clause and common synonyms (including the GWT acronym) would raise both completeness and trigger term quality.

Suggestions

Add an explicit trigger clause, e.g. "Use when acceptance criteria are requested, when a spec needs Given/When/Then scenarios, or when moving requirements to the test/validation phase."

Include common synonyms and phrasings users would naturally say ("GWT", "acceptance criteria", "test scenarios", "critérios de aceite") to broaden trigger term coverage.

If the surrounding workflow is bilingual, mention both Portuguese and English trigger words (e.g. "acceptance criteria / critérios de aceite") so the skill triggers regardless of the user's language.

DimensionReasoningScore

Specificity

"Gera critérios de aceite Given/When/Then para requisitos funcionais. Inclui happy path, edge cases e falhas" names the domain and one concrete action (generating GWT acceptance criteria), with the included items (happy path, edge cases, failures) being facets of that single action rather than several distinct actions, matching the 'names domain and 1-2 concrete actions' anchor.

3 / 5

Completeness

The description clearly answers "what" (generate Given/When/Then acceptance criteria covering happy path, edge cases, and failures) but contains no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Relevant keywords are present ("critérios de aceite", "Given/When/Then", "requisitos funcionais", "happy path", "edge cases") but common variations and synonyms are missing from the description itself (e.g. "GWT" acronym, "acceptance criteria", "test scenarios"), matching the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The Given/When/Then acceptance-criteria-for-functional-requirements niche is mostly distinct, with only minor overlap risk against closely related test-writing or BDD scenario skills; it is not a fully clear niche with minimal conflict risk.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

fernandezbaptiste/cursor-multiagent-system

Path

skills/workflow/acceptance-writer/SKILL.md

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.