qte77/plugins/docs-generator/skills/generating-report
plugins/docs-generator/skills/generating-report/SKILL.md
--- name: generating-report description: Generates structured reports including status updates, assessments, post-mortems, and executive summaries. Use when writing a report, creating a project status update, or documenting an incident post-mortem. compatibility: Designed for Claude Code metadata: allowed-tools: Read, Write, Glob, Grep, WebSearch, WebFetch argument-hint: [report-type] [topic] stability: stable content-hash: sha256:ed0c11638e37e07dcd465265198d17598dbfc1e9fd6c0d764cc288017
$ install --global
skillsauthnpx skillsauth add qte77/claude-code-plugins plugins/docs-generator/skills/generating-reportInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 17, 2026, 11:29 AM4.3s2 files scanned
SKILL.md
- name:
- generating-report
- description:
- Generates structured reports including status updates, assessments, post-mortems, and executive summaries. Use when writing a report, creating a project status update, or documenting an incident post-mortem.
- compatibility:
- Designed for Claude Code
- allowed-tools:
- Read, Write, Glob, Grep, WebSearch, WebFetch
- argument-hint:
- [report-type] [topic]
- stability:
- stable
- content-hash:
- sha256:ed0c11638e37e07dcd465265198d17598dbfc1e9fd6c0d764cc28801733949ec
- last-verified-cc-version:
- 1.0.34
Report Generation
Target: $ARGUMENTS
Generate a structured report based on the requested type and topic.
References (MUST READ)
Read these before proceeding:
references/report-structure.md— Status, assessment, post-mortem, and executive report formats
Report Types
| Type | Trigger phrases | Output path |
|------|----------------|-------------|
| Status | "status report", "project status", "weekly update" | docs/reports/<date>-status-<slug>.md |
| Assessment | "assessment", "evaluation", "review" | docs/reports/<date>-assessment-<slug>.md |
| Post-mortem | "post-mortem", "incident report", "retrospective" | docs/reports/<date>-postmortem-<slug>.md |
| Executive | "executive summary", "exec summary", "briefing" | docs/reports/<date>-executive-<slug>.md |
Workflow
- Detect report type from arguments — default to Status if ambiguous
- Read reference for the matching report structure
- Glob for existing reports in
docs/reports/to maintain consistency - Gather context:
- Grep for recent changes, TODOs, or relevant code patterns
- Read project README or CHANGELOG if available
- WebSearch for external context if needed
- Generate the report using the appropriate structure
- Output location and suggest distribution/follow-up
Rules
- Always use ISO date format (YYYY-MM-DD) in filenames and content
- Include YAML frontmatter with title, date, type, and author fields
- Post-mortems must be blameless — focus on systems, not individuals
- Status reports must include blockers and next steps
- Executive summaries must fit on one page (roughly 500 words)
- Never fabricate metrics or data — mark unknown values as "TBD"
Related Skills
qte77/triaging-security-report
development
VerifiedTrustedCommunity
Verify an external or AI-generated security report against the actual codebase before acting on it. Use when handed a scanner PDF, automated teardown, audit report, or bug-bounty submission — classifies every finding CONFIRMED / OVERSTATED / FALSE-POSITIVE / FABRICATED and salvages the real work items.
2SKILL.mdUpdated Jul 6, 2026
qte77/auditing-website-seo-geo
development
VerifiedTrustedCommunity
Audits a site's SEO and AI-search (GEO) readiness — meta tags, Open Graph/Twitter, JSON-LD, robots/llms conventions — and generates fixes. Use when reviewing search visibility, social previews, structured data, or LLM/AI-crawler discoverability.
1SKILL.mdUpdated Jun 14, 2026
qte77/writing-readme
documentation
VerifiedTrustedCommunity
Generate or update README.md files across three scopes — repo (with project-type detection), account (GitHub user profile), and org (organization profile). Use when creating, updating, or aligning a README to org conventions.
1SKILL.mdUpdated Apr 19, 2026
qte77/auditing-readme
development
VerifiedTrustedCommunity
Audit README.md files against best practices for repos, accounts, or orgs. Detects missing sections, stale links, inconsistent formatting, and convention violations. Use when reviewing README quality across one or many repos.
1SKILL.mdUpdated Apr 19, 2026