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.From its SKILL.md
npx -y skills add lingxling/awesome-skills-cn --skill security-requirement-extractionAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
1.4 KB, 210 tokens by cl100k_base, as published. Nobody here has run it
Security Requirement Extraction
Transform threat analysis into actionable security requirements.
Use this skill when
- Converting threat models to requirements
- Writing security user stories
- Creating security test cases
- Building security acceptance criteria
- Compliance requirement mapping
- Security architecture documentation
Do not use this skill when
- The task is unrelated to security requirement extraction
- You need a different domain or tool outside this scope
Instructions
- Clarify goals, constraints, and required inputs.
- Apply relevant best practices and validate outcomes.
- Provide actionable steps and verification.
- If detailed examples are required, open
resources/implementation-playbook.md.
Resources
resources/implementation-playbook.mdfor detailed patterns and examples.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
What ships with it
23.6 KB alongside SKILL.md
GitHub clipped this repository’s file list, so this is at least 1 file and may be more.
resources/
- implementation-playbook.md23.6 KB