executive-reporting
/executive-reporting
Write shift, daily, weekly, executive and incident reports in BLUF style with risk expressed in business terms, and save them with save_report; use whenever a report or summary for humans is requested or scheduled.
- Author
- gensecaihq ↗
- Repository
- Wazuh-Autopilot ↗
- Licence
- MIT
- Last repository change
- 24.09.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 24.09.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Write shift, daily, weekly, executive and incident reports in BLUF style with risk expressed in business terms, and save them with save_report; use whenever a report or summary for humans is requested or scheduled.
Original author description
Write shift, daily, weekly, executive and incident reports in BLUF style with risk expressed in business terms, and save them with save_report; use whenever a report or summary for humans is requested or scheduled.
How it works
- Style rules
- Data
- Templates
- Output
SKILL.md preview
---
name: executive-reporting
description: Write shift, daily, weekly, executive and incident reports in BLUF style with risk expressed in business terms, and save them with save_report; use whenever a report or summary for humans is requested or scheduled.
allowed-tools: search_cases get_case list_actions get_wazuh_alert_summary get_wazuh_weekly_stats get_top_security_threats generate_security_report get_wazuh_vulnerability_summary save_report
metadata:
category: reporting
display_name: Executive Reporting
standards: [nist-800-61r3, nist-csf-2]
version: "1.0"
---
# Executive Reporting
Reports exist so humans can decide. Lead with the conclusion (BLUF — bottom line up
front), quantify, and translate technical risk into business impact.
## Style rules
- First paragraph: 2–3 sentences — the most important thing, its impact, and any
decision needed.
- Numbers with comparison ("17 incidents, up 26% vs last week").
- Business language for executive reports: affected service, customers, revenue or
regulatory exposure, downtime — not rule ids.
- Separate facts from assessments; use calibrated words (likely, very likely).
- No blame; name roles, not people.
- Keep executive reports ≤ 1 page; analyst reports can include tables.
## Data
| Need | Source |
|---|---|
| Cases in period | `search_cases(query="", status=...)` then `get_case` for top items |
| Actions | `list_actions(case_id)` for major cases |
| Alert volume | `get_wazuh_alert_summary`, `get_wazuh_weekly_stats` |
| Top threats | `get_top_security_threats` |
| Vulnerabilities | `get_wazuh_vulnerability_summary` |
| Pre-built summary | `generate_security_report` (use as input, verify numbers) |
## Templates
**Shift handover** (kind `shift`): open cases by severity · new since last shift ·
pending approvals (with expiry) · actions executed and verification status · watch items
for next shift.
**Daily** (`daily`): BLUF · alert volume and trend · incidents opened/closed · notable
cases (≤ 5, one line each) · automation stats · issues (agent coverage, ingestion lag).
**Weekly** (`weekly`): BLUF · KPIs vs prior week (see `soc-metrics`) · top ATT&CK
techniques · top targeted assets · vulnerability posture (Act/Attend counts) ·
detection tuning done/proposed · recommendations.
**Executive** (`executive`): BLUF · risk posture (improving / stable / worsening, why) ·
material incidents and business impact · decisions/investment asks · 3 KPIs max.
**Incident** (`incident`, per case — NIST 800-61r3 post-incident style): summary ·
timeline (from `incident-timeline`) · impact · root cause / initial access · actions and
verification · what went well · what to improve (detection, process, controls) ·
follow-up items with owner roles.
## Output
- `save_report(kind, title, body_md)` where kind ∈ `shift|daily|weekly|monthly|executive|incident`.
- Title format: `<Kind> report — <period or case number>`.
- Include a "Data sources" footer listing tools used and the time range.
Versions
The database has no other skills named executive-reporting.
Database snapshot: 13.11.2026 · package version baa292fa6ef5 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100executive-decision-memo
Draft, review, and format official executive memorandums, decision records, policy directives, and formal letters using strict Bottom Line Up Front (BLUF) and structured hierarchy rules. Use whenever the user asks to write an executive memo, decision record, policy directive, or… - 100report-generator
Generate professional reports with charts, tables, visualizations, and structured narratives. Covers data-driven PDF/HTML reports, weekly status reports, executive summaries, and recurring team updates. Use when a user asks to create a report, generate a data report, build a… - 100create-stakeholder-update
Create a stakeholder update when the user asks to write a status update, send a project update, prepare an executive summary, or draft a BLUF update - 90executive-summary
Compresses long reports, memos, and analyses into a decision-ready one-page summary (250-350 words) - bottom line up front, 3-5 evidence-backed key findings, a specific owned-and-dated recommendation, risks with mitigations, and the exact decision or resource being requested -… - 90technical-writing-guide
Use when structuring or rewriting standalone technical explanations, reports, status updates, documentation, recommendations, or operational handoffs so readers see the outcome, decision, action, or status first. Triggers on bottom line up front, BLUF, outcome-first writing,… - 100business-writing
Write executive-grade business communication with BLUF (bottom line up front), active verbs, and zero buzzwords. Use when the user writes memos, status updates, emails to leadership, decision briefs, meeting recaps, or any business/corporate communication.