Agent skill for specification - invoke with $agent-specification
43
28%
Does it follow best practices?
Impact
51%
1.54xAverage score across 3 eval scenarios
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.agents/skills/agent-specification/SKILL.mdUse case definition and Gherkin acceptance criteria
Use case YAML format
0%
0%
UC ID field
0%
57%
UC actor field
0%
12%
UC preconditions field
0%
12%
UC numbered flow
0%
14%
UC postconditions field
0%
12%
UC exceptions field
0%
12%
Gherkin format
33%
100%
Happy path scenario
66%
100%
Failure scenario
66%
100%
Constraints three categories
100%
100%
Constraint YAML structure
0%
100%
Requirements document structure and YAML requirement formatting
FR YAML format
0%
0%
FR ID scheme
28%
0%
FR acceptance criteria
0%
33%
FR priority field
0%
0%
NFR YAML format
0%
0%
NFR ID scheme
28%
0%
NFR category field
0%
0%
NFR measurement field
0%
37%
SRS Introduction section
100%
100%
Definitions subsection
42%
100%
SRS section numbering
0%
100%
No vague qualifiers
100%
100%
Measurable performance NFR
100%
100%
Data model, API specification, and constraint analysis
Data model YAML format
0%
0%
Entity attributes with types
44%
77%
Primary key annotation
100%
100%
Entity relationships
44%
100%
Foreign key annotation
100%
100%
OpenAPI version declaration
0%
0%
OpenAPI info block
0%
0%
OpenAPI paths block
0%
0%
Request body schema
0%
0%
Multiple response codes
75%
100%
Validation checklist present
66%
77%
Checklist covers key areas
100%
90%
26c35b5
Table of Contents
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.