CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

requirement-summarizer

Extract and summarize core features, constraints, and priorities from requirement documents. Use when analyzing PRDs, RFCs, business requirements, user stories, epics, or any requirement documentation to identify must-have features, technical constraints, priority levels (P0/P1/P2/MoSCoW), and key decision points. Triggers when users ask to summarize, analyze, extract, or understand requirements from documents.

Quality

80%

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/requirement-summarizer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 well-structured, genuinely actionable instruction skill with a concrete output template, explicit quality checks, and thoughtful edge-case and document-type guidance. Its main weakness is redundancy across the Best Practices, Tips, and Example Usage sections, which inflates length without adding new guidance. The self-contained single-file organization works at this size but could shed weight by moving the template to a reference file.

Suggestions

Merge "Tips for Effective Summarization" into "Best Practices" — they overlap heavily (pattern grouping, inferring priorities, traceability) and the duplication costs tokens without new guidance.

Trim the "Example Usage" response approaches to just the user-request quotes, since the numbered steps restate the Workflow section verbatim.

Add brief guidance for oversized or multi-document inputs (e.g., how to batch or consolidate summaries), the main actionable gap for real requirement sets.

DimensionReasoningScore

Conciseness

The body mostly assumes Claude's competence (no basic concept explanations) but includes redundancy: "Tips for Effective Summarization" substantially repeats "Best Practices" (e.g., grouping scattered requirements, inferring priorities), and the "Example Usage" response approaches restate the workflow steps. This matches anchor 3 ('some unnecessary explanation or could be tightened') rather than 4's 'minor instances'.

3 / 5

Actionability

Provides a fully concrete markdown output template, an explicit quality-check list, and specific conventions like marking inferred priorities with "(inferred)" — actionable executable guidance for an instruction-only skill. Minor gaps (no handling for very large or multi-document inputs) keep it below anchor 5.

4 / 5

Workflow Clarity

A clear five-step sequence (read → extract → generate → quality checks → edge cases) with a validation checkpoint ("Before presenting the summary, verify...") and edge-case recovery guidance. It falls short of anchor 5 because the quality checks are a one-pass list rather than an explicit validate-fix-retry feedback loop, though no destructive/batch cap applies.

4 / 5

Progressive Disclosure

No bundle files exist, so the skill is a single self-contained file with well-organized, clearly headed sections — good structure with no buried or nested references. It stays at anchor 4 rather than 5 because the ~70-line inline output template is borderline content that could be split into a reference file to keep SKILL.md leaner.

4 / 5

Total

15

/

20

Passed

Description

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

A strong description that explicitly states concrete capabilities and clear trigger conditions with good natural-term coverage including framework-specific vocabulary. The only weakness is minor overlap risk with generic summarization skills and a few missing natural synonyms. Third-person voice is used correctly and there is no fluff.

DimensionReasoningScore

Specificity

"Extract and summarize core features, constraints, and priorities" lists several concrete actions (extract, summarize, identify) with specific outputs like priority levels and key decision points. It falls short of anchor 5 because coverage of actions is narrower than the comprehensive multi-action examples, but exceeds anchor 3's '1-2 concrete actions'.

4 / 5

Completeness

Explicitly answers 'what' ("Extract and summarize core features, constraints, and priorities from requirement documents") and 'when' ("Use when analyzing PRDs, RFCs..." and "Triggers when users ask to summarize, analyze, extract, or understand requirements from documents") with concrete trigger phrases, matching the anchor-5 example pattern exactly.

5 / 5

Trigger Term Quality

Includes strong natural terms users would say: "PRDs, RFCs, business requirements, user stories, epics", "P0/P1/P2/MoSCoW", and "summarize, analyze, extract, or understand". A few natural variations (e.g., 'product requirements doc', 'spec', 'acceptance criteria') are missing, placing it at anchor 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

Clear niche (requirement analysis) with distinct triggers like PRD, RFC, user stories, and MoSCoW, but "any requirement documentation" plus the generic "summarize... requirements from documents" phrasing creates minor overlap risk with general document-summarization skills. Anchor 4 ('mostly distinct; minor overlap risk') is the best fit.

4 / 5

Total

17

/

20

Passed

Validation

100%

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

ArabelaTso/Skills-4-SE

Path

skills/requirement-summarizer/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.