Agent skill
security-vulnerability-report
Respond to security vulnerability reports. Use when a researcher reports a security issue or asks about bug bounty policy.
Stars
163
Forks
31
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/security-vulnerability-report
Metadata
Additional technical details for this skill
- metrics
- sample_size: 32 avg_thread_length: 3.31 top_phrases: - phrase: "for the heads up" count: 13 percent: 40.6 - phrase: "thanks for the heads" count: 12 percent: 37.5 - phrase: "the heads up we'll" count: 6 percent: 18.8 - phrase: "heads up we'll look" count: 6 percent: 18.8 - phrase: "up we'll look into" count: 6 percent: 18.8 - phrase: "we'll look into this" count: 6 percent: 18.8 - phrase: "look into this asap" count: 5 percent: 15.6 - phrase: "on sun jan 25" count: 2 percent: 6.3 - phrase: "sun jan 25 2026" count: 2 percent: 6.3 - phrase: "jan 25 2026 at" count: 2 percent: 6.3
- validation
- required_phrases: - "for the heads up" forbidden_patterns: [] max_length: 500
- sample size
- 32
- related skills
-
[ "website-bug-report", "api-documentation-question", "nonprofit-government-discount", "student-discount-request" ] - trigger phrases
-
[ "respond security", "security vulnerability", "vulnerability reports" ]
SKILL.md
Security Vulnerability Report
Response Patterns (from samples)
Common openings:
- "No worries! Thanks for your concern!"
- "Hey Kiran,"
- "Hey Simon,"
Common core lines:
- ">>"
- ">"
- "Thanks for the heads up! We'll look into this ASAP."
Common closings:
- "Thanks for the heads up! We'll look into this ASAP."
- "Thanks for the heads up!"
- "Best,"
Phrases That Work (4-gram frequency)
- "for the heads up" — 13 (40.6%)
- "thanks for the heads" — 12 (37.5%)
- "the heads up we'll" — 6 (18.8%)
- "heads up we'll look" — 6 (18.8%)
- "up we'll look into" — 6 (18.8%)
- "we'll look into this" — 6 (18.8%)
- "look into this asap" — 5 (15.6%)
- "on sun jan 25" — 2 (6.3%)
- "sun jan 25 2026" — 2 (6.3%)
- "jan 25 2026 at" — 2 (6.3%)
Tone Guidance (observed)
- Openings trend toward: "No worries! Thanks for your concern!"
- Closings often include: "Thanks for the heads up! We'll look into this ASAP."
What NOT To Do
- Don't introduce policy details that are not present in the verified response lines above.
- Don't paraphrase or reframe the customer's question in a way that changes meaning.
- Don't add refund/discount promises unless they appear in the extracted responses for this topic.
Validation
Draft must:
- Include at least one of the required phrases from the validation block
- Stay consistent with the observed response patterns above
- NOT introduce policy details that are not present in the verified response lines above.
Didn't find tool you were looking for?