CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

legacy-specifier

Extrai especificações de um sistema legado (código existente) quando não há documentação adequada.

Quality

78%

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/legacy-specifier/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 body is a lean, well-structured instruction skill: an unambiguous stepwise process, hard rules that prevent guessing, concrete output artifacts, and a feature template, with no wasted tokens. Its only weakness is the lack of a worked example and an explicit validation pass over drafted specs.

DimensionReasoningScore

Conciseness

The body is written in terse fragments ('Identify behaviors from code, routes, UI, tests'; 'Never guess business intent. If unclear → UNKNOWN + Open Question') with zero padding and no explanation of concepts Claude already knows; the single policy line ('prioritizes accuracy over completeness') earns its place.

5 / 5

Actionability

For an instruction-only skill the guidance is concrete: exact output paths (spec/30-features/<FEATURE-ID>/...), an evidence-source priority order, ID conventions (FEATURE-001), and a template with required fields including GWT scenarios. The minor gap is the absence of a worked example of a filled spec.md.

4 / 5

Workflow Clarity

Steps 0-5 are clearly sequenced, and Rule 1 ('If unclear → UNKNOWN + Open Question') plus Step 5 (open questions and risks) function as uncertainty checkpoints; the skill is analytical rather than destructive, but there is no explicit verify/review step over the drafted specs, keeping it below the feedback-loop anchor.

4 / 5

Progressive Disclosure

No bundle files exist and none are needed; the ~60-line body is cleanly sectioned (Purpose, When to Use, Inputs, Outputs, Rules, Process, Template) with no content that belongs in a separate file, satisfying the simple-skill standard for well-organized sections.

5 / 5

Total

18

/

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 clear, in third person, and names a concrete domain and action with an explicit condition, but it under-sells the skill's specific capabilities and lacks natural trigger phrases and synonyms users would actually say. It sits comfortably at the midpoint-plus of the rubric rather than exemplifying it.

Suggestions

Enumerate the concrete extraction actions in the description itself (e.g. 'Extracts API contracts, observed behaviors from routes/UI/tests, and feature specs from an existing codebase') to raise specificity.

Add an explicit user-facing trigger clause with natural phrases, e.g. 'Use when the user asks to document, reverse-engineer, or extract specs from an existing or legacy codebase'.

Include synonyms and variations users naturally say — 'spec extraction', 'reverse engineer', 'document existing code' — to improve trigger term coverage.

DimensionReasoningScore

Specificity

The description names the domain ('sistema legado', 'código existente') and a single concrete action ('Extrai especificações'), matching the anchor for 1-2 concrete actions rather than several; richer actions like extracting APIs/contracts or behaviors appear only in the body, not the description.

3 / 5

Completeness

It explicitly answers both 'what' ('Extrai especificações de um sistema legado') and 'when' ('quando não há documentação adequada'), but the 'when' clause describes a codebase condition rather than concrete user-trigger situations, so it does not reach the fully explicit trigger-phrase level.

4 / 5

Trigger Term Quality

Terms like 'sistema legado', 'código existente', and 'documentação' are relevant, but common variations users would naturally say — e.g. 'reverse engineer', 'document this codebase', 'write specs' — are missing, fitting the 'some relevant keywords but missing synonyms' anchor.

3 / 5

Distinctiveness Conflict Risk

Spec extraction from legacy/existing code is a mostly distinct niche with only minor overlap risk against general documentation- or spec-writing skills; it is not fully conflict-free since 'especificações' could contend with forward spec-writing skills.

4 / 5

Total

14

/

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/legacy-specifier/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.