CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

security-requirement-extraction

Derive security requirements from threat models and business context. Use when translating threats into actionable requirements, creating security user stories, or building security test cases.

Quality

71%

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 ./plugins/security-scanning/skills/security-requirement-extraction/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

51%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 skill is well-structured with exemplary progressive disclosure, deferring the heavy template library to a single clearly signaled reference. However, the body itself relies on concepts Claude already knows and, critically, lacks any worked example or sequenced workflow for the core threat-to-requirement transformation it promises.

Suggestions

Replace the textbook requirement-types and attributes tables with one inline worked example (a sample threat mapped to a full requirement with acceptance criteria and a test case), which would raise both actionability and conciseness.

Add a short sequenced workflow, e.g., 1. enumerate threats from the model, 2. classify each per Template 2 in references/details.md, 3. generate stories/test cases via Templates 3-4, 4. validate that every threat maps to at least one testable requirement.

Trim generic Do's/Don'ts ("Be specific", "Don't forget testability") in favor of the failure modes they guard against, such as an example of a vague requirement next to its testable rewrite.

DimensionReasoningScore

Conciseness

The body is short, but the functional/non-functional/constraint table and the traceability/testability/priority attributes are textbook software-engineering knowledge Claude already has, and Do's/Don'ts like "Be specific" and "Don't forget testability" are generic — some unnecessary explanation that could be tightened.

3 / 5

Actionability

The requirement-category diagram includes one concrete example chain ("Protect customer data" → "Encrypt PII at rest" → "AES-256 encryption with KMS key rotation"), but no inline worked requirement or user story and no concrete steps; all executable templates are deferred to references/details.md, leaving guidance incomplete in the body itself.

3 / 5

Workflow Clarity

No sequenced process exists for moving from a threat model to requirements, stories, or test cases — there is no guidance on which of the four templates in details.md applies to which situation, and no validation checkpoint (e.g., verifying every threat maps to a requirement). The steps are poorly defined rather than merely missing checkpoints.

2 / 5

Progressive Disclosure

The body is a clean overview and the 611-line template library is appropriately split into references/details.md, signaled once with explicit instruction on when to read it; the reference file exists, is one level deep, and contains no nested references — matching the anchor exemplar.

5 / 5

Total

13

/

20

Passed

Description

78%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 well-constructed description with an explicit use-when clause and natural trigger phrases. Its main weakness is that the action space is really one capability restated three ways, and a few common synonyms (compliance, acceptance criteria) are missing from the triggers.

DimensionReasoningScore

Specificity

"Derive security requirements from threat models and business context" names the domain and the core action, but the remaining clauses ("translating threats", "creating security user stories", "building security test cases") are variations of that single action rather than several distinct capabilities, so coverage is not comprehensive as anchor 4 requires.

3 / 5

Completeness

It clearly answers "what" ("Derive security requirements from threat models and business context") and "when" with an explicit "Use when" clause carrying three concrete trigger phrases, matching the anchor-5 exemplar structure.

5 / 5

Trigger Term Quality

"security requirements", "threat models", "security user stories", and "security test cases" are natural phrases users would say, but common variants like "compliance", "acceptance criteria", or "risk register" are absent — good coverage with a few natural terms missing.

4 / 5

Distinctiveness Conflict Risk

The threat-to-requirement niche is mostly distinct, but triggers like "creating security test cases" overlap with adjacent security-testing and threat-modeling skills, so minor overlap risk remains as in anchor 4.

4 / 5

Total

16

/

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

wshobson/agents

Path

plugins/security-scanning/skills/security-requirement-extraction/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.