Generating Report
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.
Install
$ agentstack add skill-qte77-claude-code-plugins-generating-report ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-qte77-claude-code-plugins-generating-report) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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/-status-.md | | Assessment | "assessment", "evaluation", "review" | docs/reports/-assessment-.md | | Post-mortem | "post-mortem", "incident report", "retrospective" | docs/reports/-postmortem-.md | | Executive | "executive summary", "exec summary", "briefing" | docs/reports/-executive-.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"
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: qte77
- Source: qte77/claude-code-plugins
- License: Apache-2.0
- Homepage: https://qte77.github.io/claude-code-plugins/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.