requirement-summary
Alias for requirement-summarizer. Produces a structured summary of a requirements document — the key obligations, grouped by actor and concern, with the MUST/SHOULD/MAY breakdown. Use when onboarding to a large spec, when deciding what to implement first, or when the user asks what a standard actually requires.
Install with Tessl CLI
npx tessl i github:santosomar/general-secure-coding-agent-skills --skill requirement-summary88
Quality
85%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Discovery
85%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description that clearly articulates what the skill does (structured requirements summarization with obligation breakdown) and when to use it (onboarding to specs, prioritization, understanding standards). The main weakness is trigger term coverage could be expanded to include more natural variations users might say when working with specifications.
Suggestions
Add more trigger term variations like 'RFC', 'specification', 'compliance requirements', 'technical standard', or common file patterns to improve discoverability
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Produces a structured summary', 'key obligations', 'grouped by actor and concern', 'MUST/SHOULD/MAY breakdown'. These are concrete, actionable outputs. | 3 / 3 |
Completeness | Clearly answers both what ('Produces a structured summary of a requirements document — the key obligations, grouped by actor and concern, with the MUST/SHOULD/MAY breakdown') and when ('Use when onboarding to a large spec, when deciding what to implement first, or when the user asks what a standard actually requires'). | 3 / 3 |
Trigger Term Quality | Includes some natural terms like 'requirements document', 'spec', 'standard', 'implement', but missing common variations users might say like 'RFC', 'specification', 'compliance', 'obligations', or file extensions. | 2 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on requirements documents with specific RFC-style MUST/SHOULD/MAY terminology. The 'requirement-summarizer' alias and specific use cases make it distinct from general document summarization skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted alias skill that efficiently redirects users to the canonical skill while providing helpful disambiguation. The content is appropriately minimal, clearly structured, and includes a useful 'wrong destination' table that helps users find the right skill if they landed here by mistake. The only limitation is inherent to being an alias - it provides no standalone actionable content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean content that serves its purpose as an alias redirect. Every token earns its place - no unnecessary explanation of what requirements are or how summarization works. | 3 / 3 |
Actionability | As an alias, it correctly points to the actual skill, but provides no executable guidance itself. The quick reference table gives useful context about inputs/outputs, but the actual actionable content lives elsewhere. | 2 / 3 |
Workflow Clarity | For an alias skill, the workflow is crystal clear: follow the link to requirement-summarizer. The disambiguation table provides excellent decision support for users who arrived at the wrong skill. | 3 / 3 |
Progressive Disclosure | Perfect structure for an alias - immediate redirect at top, quick reference for context, and clear navigation table for related skills. One-level-deep references with clear signaling. | 3 / 3 |
Total | 11 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.