vulnerability-report

Generate vulnerability tracking documentation with findings, severity ratings, and remediation status.

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/tektonlabs/ai-software-design --skill vulnerability-report-tektonlabs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vulnerability-report
Source: https://github.com/tektonlabs/ai-software-design/tree/main/.claude/skills/security/vulnerability-report
Command: npx skills add https://github.com/tektonlabs/ai-software-design --skill vulnerability-report-tektonlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security scan results from SAST, DAST, and penetration tests arrive as raw findings that are hard to track, prioritize, and report. This Skill turns them into a structured, signable vulnerability report with severity ratings, CVSS scores, remediation guidance, and SLA tracking. ## Core Features & Use Cases - Structured Findings Documentation: Records each vulnerability with ID, severity, CVSS score, CWE reference, proof of concept, impact, and code-level remediation guidance. - Remediation & SLA Tracking: Tracks remediation progress by severity tier, SLA compliance rates, action items, false positives, and risk acceptances. - Governed Sign-Off: Enforces validation rules and requires CISO approval before the document is accepted, fitting Phase 10 (Security) of a signature-gated SDLC. - Use Case: After a penetration test on a web API, run this Skill to produce a vulnerability report classifying findings from Critical to Low, with dependency CVEs and remediation deadlines, ready for CISO sign-off. ## Quick Start Ask the agent to run /security/vulnerability-report to generate a vulnerability report from your latest security scan results.

Frequently Asked Questions about vulnerability-report

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a vulnerability report from security scan results?▼

Run the vulnerability-report skill after your security assessment is signed. Provide the project name, scan date, scan type (SAST, DAST, or pentest), scope, and tools used, and it generates a structured report with findings, severity ratings, and remediation guidance.

What should a vulnerability report include for security audits?▼

A complete report includes an executive summary with severity counts, detailed findings with CVSS scores and CWE references, proof of concept, remediation steps, dependency vulnerabilities, SLA compliance tracking, false positives, and risk acceptances.

What are the prerequisites for running the vulnerability-report skill?▼

The security-assessment document must exist and be signed before this skill runs. You also need scan results from SAST, DAST, or penetration testing, and an asset inventory is recommended.

Who approves the vulnerability report in this workflow?▼

The CISO holds final approval authority over the vulnerability report. Security Analysts validate findings and Application Owners accept the remediation plan, while DevOps and Technical Leads provide non-gating reviews.

How are vulnerability remediation SLAs tracked?▼

The report includes an SLA compliance table by severity tier: Critical at 24 hours, High at 7 days, Medium at 30 days, and Low at 90 days. It tracks on-track versus overdue counts and remediation progress percentages.