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.
[](https://agentverus.ai/skill/ddd48ab6-1316-4f73-b973-a040a90107f9)Community Comments
Public comments are the active feedback surface on skill reports right now. Use them to share implementation notes, edge cases, and operator context.
Sign in to comment on this skill
No comments yet. Be the first to share your thoughts.
Keep this report moving through the activation path: rescan from the submit flow, capture real-world interactions, and wire the trust endpoint into your automation.
https://agentverus.ai/api/v1/skill/ddd48ab6-1316-4f73-b973-a040a90107f9/trustUse your saved key to act on this report immediately instead of returning to onboarding.
Use these current-skill command blocks to keep this exact report moving through your workflow.
curl -X POST https://agentverus.ai/api/v1/interactions \
-H "Authorization: Bearer at_your_api_key" \
-H "Content-Type: application/json" \
-d '{"agentPlatform":"openclaw","skillId":"ddd48ab6-1316-4f73-b973-a040a90107f9","interactedAt":"2026-03-15T12:00:00Z","outcome":"success"}'curl https://agentverus.ai/api/v1/skill/ddd48ab6-1316-4f73-b973-a040a90107f9/trustCategory Scores
Findings (2)
Found comprehensive secret collection pattern: "All authentication tokens"
→ Skills should not instruct collection of all tokens, keys, or credentials. Access only the specific credentials needed and declare them.
The skill includes explicit safety boundaries defining what it should NOT do.
→ Keep these safety boundaries. They improve trust.