requirement-comparison-reporter
Compares two versions of a requirements document and reports additions, removals, semantic changes, and scope drift — distinguishing clerical edits from meaning changes. Use when a spec was revised, when checking if a new version of a standard affects you, or when the user asks what changed between spec versions.
Install with Tessl CLI
npx tessl i github:santosomar/general-secure-coding-agent-skills --skill requirement-comparison-reporter100
Quality
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Discovery
100%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 well-crafted skill description that excels across all dimensions. It provides specific capabilities (comparing versions, identifying semantic vs clerical changes), uses natural trigger terms users would actually say, includes an explicit 'Use when' clause with multiple scenarios, and carves out a distinct niche in requirements/specification document comparison.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Compares two versions', 'reports additions, removals, semantic changes, and scope drift', and 'distinguishing clerical edits from meaning changes'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what (compares versions, reports changes, distinguishes edit types) AND when with explicit 'Use when' clause covering three scenarios: spec revision, standard version changes, and user asking about differences. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'requirements document', 'spec', 'revised', 'standard', 'what changed', 'spec versions'. Good coverage of variations including formal ('requirements document') and informal ('spec') terms. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on requirements/spec document comparison with distinct triggers like 'requirements document', 'spec versions', 'scope drift'. Unlikely to conflict with general document or diff tools due to domain-specific focus. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill that efficiently teaches semantic requirement comparison. It provides concrete classification taxonomy, a clear two-step workflow, a detailed worked example demonstrating the analysis, and a specific output template. The 'hidden weakening' pattern and 'Do not' sections add valuable edge-case guidance without bloat.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, assuming Claude's competence. No unnecessary explanations of basic concepts; every section adds actionable value. Tables are used effectively to compress information. | 3 / 3 |
Actionability | Provides concrete classification taxonomy, step-by-step process, worked example with actual requirement text, component extraction table, and specific output format template. Highly executable guidance. | 3 / 3 |
Workflow Clarity | Clear two-step process (Align → Classify) with explicit sub-steps. The worked example serves as validation of understanding. The 'Do not' section provides error-prevention checkpoints for common mistakes. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from classification → alignment → classification details → worked example → anti-patterns → output format. Self-contained skill that doesn't need external references for its scope. | 3 / 3 |
Total | 12 / 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.