CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

requirements-extractor

Converte input não estruturado (texto, notas, docs parciais) em requisitos funcionais (FR) e perguntas abertas. Não inventa requisitos.

Quality

70%

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/requirements-extractor/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 well-structured, lean instruction-only skill: concrete file paths, ID conventions, required fields, and a clearly sequenced process with hard constraints. It falls short of top marks mainly on the absence of a worked example and a final validation checkpoint, plus minor duplication between the Process and Output Format sections.

Suggestions

Add one filled-in example FR (e.g., FR-001 with Title, Description, actor, preconditions, success/failure, priority) so the output format is copy-paste unambiguous.

Add a final verification step to the Process, e.g. 'Before writing files, re-check every FR is atomic and testable; any gap becomes an OQ' — this supplies the missing feedback loop.

Either bundle the named template files under references/ or rephrase 'Use templates:' to 'Structure each output file as follows' so no phantom files are implied.

DimensionReasoningScore

Conciseness

The body is dense and skill-specific with no explanations of concepts Claude already knows, but there is minor redundancy: the FR field list appears in both Step 2 and the Output Format section, and the no-invention rule is stated in the Extraction Rules as well as implied by 'Explicit Unknowns' framing. Not a 5 because those duplications could be trimmed.

4 / 5

Actionability

Concrete guidance throughout: canonical output paths (spec/10-requirements/functional-requirements.md, spec/99-meta/open-questions.md, spec/99-meta/assumptions.md), ID schemes (FR-001, OQ-001, A-001, CAP-<name>), required FR fields, and priority values (P0/P1/P2 or UNKNOWN). Not a 5 because there is no worked example of a complete FR or Open Question, and 'Use templates: functional-requirements.md' references template files that are not bundled, leaving slight ambiguity.

4 / 5

Workflow Clarity

Steps 0-5 are clearly sequenced (intake summary, actors, FRs, capability grouping, unknowns, assumptions) and the Extraction Rules act as an inline checklist; the UNKNOWN fallback ('mark UNKNOWN + add an Open Question') handles the main error path. Not a 5 because there is no final verification step or feedback loop (e.g., confirm every FR is testable and atomic before writing the output files).

4 / 5

Progressive Disclosure

Sections are well organized and all content is appropriately inline for a self-contained ~64-line skill with no bundle files. Not a 5 because the body is marginally over the under-50-line simple-skill threshold, and the 'Use templates:' line names files (functional-requirements.md, open-questions.md, assumptions.md) without bundling them or signaling paths, slightly muddying navigation.

4 / 5

Total

16

/

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 clear, honest 'what' with a useful negative constraint, but it is missing the 'when to use' half entirely, which both caps completeness and weakens trigger quality. It is written in third person and is concise, though it undersells the full capability set the body defines.

Suggestions

Append a 'Use when...' clause, e.g. 'Use when the user provides raw notes, tickets, meeting summaries, or partial docs and needs functional requirements, or when extracting requirements for a PRD/spec.'

Add natural trigger synonyms such as 'requirements', 'PRD', 'spec', and 'user stories' so the description matches how users actually phrase the need.

Mention one or two more concrete outputs (actors, flows with edge cases) to lift specificity from domain+2-actions toward comprehensive coverage.

DimensionReasoningScore

Specificity

The description names the domain and two concrete actions — 'Converte input não estruturado (texto, notas, docs parciais) em requisitos funcionais (FR) e perguntas abertas' — matching the anchor for domain + 1-2 concrete actions. It is not a 4 because the body covers several capabilities (actors, flows, assumptions, capability grouping, output files) that the description omits.

3 / 5

Completeness

The 'what' is clear (convert unstructured input into functional requirements and open questions, with the explicit constraint 'Não inventa requisitos'), but the description contains no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Not a 4 because the 'when' is entirely absent rather than merely under-specified.

3 / 5

Trigger Term Quality

Relevant keywords are present ('requisitos funcionais (FR)', 'perguntas abertas', 'texto, notas, docs parciais') but common variations and synonyms users would naturally say ('PRD', 'spec', 'user stories', 'requirements extraction') are missing, matching the 'some relevant keywords but missing variations' anchor rather than the good-coverage anchor.

3 / 5

Distinctiveness Conflict Risk

The niche — converting unstructured input into functional requirements and open questions — is mostly distinct, with only minor overlap risk against closely related PRD/spec-writing skills. Not a 5 because no explicit triggers are given to demonstrate distinctness, and the enumerated inputs ('texto, notas') are fairly broad.

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/requirements-extractor/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.