sc-report

Generate a consolidated security assessment report with CVSS-style severities and remediation roadmap.

7|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/fatihkan/badi --skill sc-report-fatihkan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sc-report
Source: https://github.com/fatihkan/badi/tree/main/.claude/skills/security-check/sc-report
Command: npx skills add https://github.com/fatihkan/badi --skill sc-report-fatihkan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidates verified security findings into a single, actionable report that maps issues to CVSS-style severities and provides a remediation roadmap.

Core Features & Use Cases

  • Executive summary with CVSS-style severity mapping and risk scoring.
  • Detailed finding breakdown by category, including affected files and suggested mitigations.
  • Generates an actionable remediation roadmap and a standardized SECURITY-REPORT.md artifact.
  • Integrates with inputs: security-report/verified-findings.md, security-report/architecture.md, and security-report/dependency-audit.md.

Quick Start

Save the scan results by running the security-check pipeline on your codebase to produce SECURITY-REPORT.md.

Frequently Asked Questions about sc-report

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

FAQPage Schema
How do I generate a consolidated security report from verified vulnerability findings?

Generate a consolidated security report by feeding verified findings, architecture details, and dependency audits into a reporting pipeline that maps vulnerabilities to CVSS-style severities and outputs a standardized SECURITY-REPORT.md artifact.

What is CVSS-style severity mapping in a software vulnerability remediation report?

CVSS-style severity mapping in vulnerability remediation assigns standardized risk scores to findings, categorizing them into an executive summary to prioritize software remediation efforts effectively.

What inputs are required to produce a security assessment report with a remediation roadmap?

Producing a security assessment report requires verified findings, architecture documentation, and dependency audit files as inputs to generate a detailed breakdown and actionable remediation roadmap.

Can I map affected files and suggested mitigations automatically when consolidating security findings?

Yes, consolidating security findings automatically maps issues by category, detailing affected files and providing suggested mitigations within the generated security report artifact.

Does the security report generation pipeline work without external dependencies?

Yes, the security report generation pipeline operates without external dependencies, directly reading standard input files like verified-findings.md and architecture.md to produce the final report.