# Create Security Assessment Reports

Security findings often become inconsistent reports that are difficult to prioritize. This skill guides structured DOCX reports with risk ratings, evidence, and remediation plans.

## Install

```bash
npx skillstore add bytr-ecosystems/security-report
```

## Metadata

- Status: approved
- Slug: bytr-ecosystems-security-report
- Skillstore revision: r2
- Version status: missing
- Tree hash: 241bd95eac4ff053318482d8ed83cb3f28d16f72bfcbda6461a4aec807b7829b
- Author: BytR-Ecosystems
- GitHub username: BytR-Ecosystems
- License: MIT
- Repository: https://github.com/BytR-Ecosystems/ml-reference-guides/tree/main/llm-platforms/claude/skills/examples/security-report
- Ref: a39a91716eadede5f4cdefd78178fed4e837a128
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/bytr-ecosystems-security-report
- Manifest: https://skillstore.pages.dev/api/skills/bytr-ecosystems-security-report/manifest

## Capabilities

- Guides DOCX report creation with the python-docx library.
- Defines sections for executive summaries, scope, methodology, findings, roadmaps, and appendices.
- Structures findings with identifiers, severity, CVSS, evidence, remediation, and references.
- Maps five risk levels to fixed RGB colors for consistent presentation.
- Recommends severity sorting, page breaks, bordered tables, and remediation timelines.

## Use Cases

- Prepare an Audit Report: Turn approved audit findings into a structured report with an executive summary and remediation roadmap.
- Deliver Penetration Test Results: Present tested vulnerabilities by severity with evidence, CVSS values, references, and recommended fixes.
- Document Compliance Gaps: Organize control gaps, risk ratings, and remediation priorities for leadership and control owners.

## Prompt Templates

### Create a Basic Report

```
Create a DOCX security assessment report for [organization]. Include an executive summary, scope, findings, and remediation roadmap using the supplied evidence.
```

### Format Vulnerability Findings

```
Build a vulnerability assessment report from [findings]. Sort by severity and include identifiers, descriptions, evidence, remediation, and references.
```

### Prepare a Penetration Test Report

```
Generate a penetration test report for [scope]. Add methodology, severity totals, CVSS values, detailed findings, and a prioritized remediation timeline.
```

### Develop a Compliance Gap Report

```
Create a compliance gap report for [framework]. Map each gap to risk, evidence, control owner, target date, and remediation priority.
```

## Limitations

- Does not scan systems, discover vulnerabilities, or validate supplied evidence.
- Requires python-docx and an environment that can create DOCX files.
- Does not include a complete CVSS calculation workflow.
- Links to advanced reference files that are not included in this package.

## Best Practices

- Validate every finding and remove sensitive evidence before generating the report.
- Use consistent severity criteria and confirm every CVSS value.
- Assign remediation owners and realistic target dates before final delivery.

## Anti Patterns

- Do not treat generated text as proof that a vulnerability exists.
- Do not include credentials, personal data, or unnecessary exploit details.
- Do not change risk ratings only to improve the executive summary.

## Security Audit

- Audited at: 2026-07-23T12:08:01.629\+00:00
- Summary: All seven static findings are false positives caused by Markdown fences, inline code, or a formatted path in SKILL.md. The examples use Python document APIs and contain no Ruby or shell command execution. No intent-level security issue was found.

## Stats

- Views: 200
- Downloads: 11
- Favorites: 0
- Popularity score: 0