sdd-spec-enforcer

Triggered when managing, creating or validating feature specifications (specs) in spec-*.md

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/sdd-workflow/skills/sdd-spec-enforcer/SKILL.md

Quality

Content

72%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.

The content is a concise, well-structured, copy-paste-ready spec template with clear naming and location rules, scoring high on conciseness, actionability, and progressive disclosure. Its main gap is the absence of any validation procedure, despite 'validating' being part of the skill's stated purpose.

Suggestions

Add a short validation checklist (e.g. required sections present, filename matches the pattern, Acceptance Criteria are numbered) so the 'validating' use case is actionable, not just the 'creating' one.

Include one filled-in example spec so users can see the template populated end-to-end.

Dimension	Reasoning	Score
Conciseness	The body is lean (~35 lines), assumes Claude's competence, and avoids explaining concepts Claude already knows; only the opening framing sentence is mildly trimmable, so it lands at 'efficient; minor instances of over-explanation' rather than the perfectly-lean anchor 5.	4 / 5
Actionability	It gives a concrete filename pattern with a worked example, exact storage paths, and a complete copy-paste template with every section header, so guidance is mostly executable; it stops short of 5 only because no filled-in example spec is shown.	4 / 5
Workflow Clarity	For a single-purpose template skill the creation path is unambiguous, but the description scopes the skill to 'validating' specs and the body provides no validation criteria or checklist to verify a spec conforms, leaving the validation workflow without checkpoints.	3 / 5
Progressive Disclosure	The skill is under 50 lines with no need for external references, and the body is well-organized into clear sections (Nomenclatura, Localização, Formato Obrigatório), satisfying the simple-skill exception for a top score; no bundle files exist to nest.	5 / 5
	Total	16 / 20 Passed

Description

62%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 is short, third-person, and provides an explicit trigger with a concrete file pattern, giving it solid completeness and distinctiveness. Its weakness is mild vagueness in the action verbs ('managing') and limited keyword variation for natural user phrasing.

Suggestions

Replace the generic verb 'managing' with concrete actions a user would name, e.g. 'writing, reviewing, or validating feature specifications'.

Add natural trigger phrasing users actually say, such as 'Use when the user asks to write, update, or check a spec file (spec-*.md)'.

Include a synonym or two (e.g. 'specification') so the description matches a wider range of natural requests.

Dimension	Reasoning	Score
Specificity	Names the domain ('feature specifications (specs)') and three actions ('managing, creating or validating'), but 'managing' is generic and the actions are not comprehensive, fitting the domain-plus-1-2-actions anchor rather than the several-specific-actions anchor.	3 / 5
Completeness	It answers both 'what' (manage/create/validate specs) and 'when' ('Triggered when... in spec-*.md') with an explicit trigger clause, but the 'what' is only moderately specific so it stops short of the fully-concrete anchor 5.	4 / 5
Trigger Term Quality	Includes relevant keywords ('specs', 'spec-*.md', 'feature specifications') but misses common variations a user might actually say (e.g. 'spec file', 'specification doc', 'write a spec'), placing it at 'some relevant keywords but missing synonyms' rather than full coverage.	3 / 5
Distinctiveness Conflict Risk	The 'spec-*.md' file pattern is a distinct, narrow trigger unlikely to fire for unrelated skills, though it could marginally overlap with general documentation skills, so it sits at 'mostly distinct; minor overlap risk' rather than the minimal-conflict anchor 5.	4 / 5
	Total	14 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: JoseMD12/testing-tessl
Path: plugins/sdd-workflow/skills/sdd-spec-enforcer/SKILL.md
Commit: 1cbe5bc

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.