requirement-coverage-checker
Checks whether an implementation covers a set of requirements by tracing each requirement to code, tests, or both — and flagging gaps where a requirement has no evidence of implementation. Use when auditing for compliance, when answering "is this spec implemented", or before claiming a standard is supported.
Install with Tessl CLI
npx tessl i github:santosomar/general-secure-coding-agent-skills --skill requirement-coverage-checker100
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 clearly articulates the specific capability (tracing requirements to code/tests and flagging gaps), provides explicit 'Use when' guidance with natural trigger phrases, and occupies a distinct niche that won't conflict with general code analysis skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'tracing each requirement to code, tests, or both' and 'flagging gaps where a requirement has no evidence of implementation'. Uses third person voice correctly. | 3 / 3 |
Completeness | Clearly answers both what ('Checks whether an implementation covers a set of requirements by tracing...and flagging gaps') AND when ('Use when auditing for compliance, when answering "is this spec implemented", or before claiming a standard is supported'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'compliance', 'spec implemented', 'standard is supported', 'requirements', 'auditing'. These are terms users would naturally use when needing this capability. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on requirement-to-implementation tracing and compliance auditing. Distinct triggers like 'spec implemented', 'compliance', and 'standard is supported' make it unlikely to conflict with general code review or testing skills. | 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 provides a complete, actionable framework for requirement coverage auditing. The worked example is particularly strong, showing not just the happy path but also how to identify partial coverage and miscoverage. The 'traps' section adds significant value by anticipating common failure modes.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, with no unnecessary explanations of concepts Claude would already know. Every section adds value—tables are used effectively to compress information, and examples are concrete without padding. | 3 / 3 |
Actionability | Provides highly concrete guidance with specific search strategies, a detailed worked example showing exact code patterns and file locations, and a complete output format template. The 'traps' table gives specific detection methods. | 3 / 3 |
Workflow Clarity | Clear 3-step process (decompose → search → rate) with explicit validation through trace strength ratings. The worked example demonstrates the complete workflow with a real audit scenario showing how to identify gaps and miscoverage. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from concepts to steps to examples to output format. At ~120 lines, the content is appropriately self-contained without needing external references. Tables and headers enable quick navigation. | 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.