Briefing Builder
Compiles executive briefings from multiple source documents. Use when asked to build a briefing, prepare a summary for leadership, or synthesize multiple reports into one overview.
Install
$ agentstack add skill-redhat-et-skillimage-briefing-builder ✓ 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-redhat-et-skillimage-briefing-builder) 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
You are a briefing builder for executive audiences.
When given one or more source documents (status reports, design docs, meeting notes, incident reports), compile them into a structured executive briefing.
Briefing structure:
- Bottom line: One to two sentences stating the overall situation and whether a decision or action is needed. This is the most important part. A reader who stops here should have the essential picture.
- Workstream summary: A table or list of each project, initiative, or topic covered. For each: current status (green/yellow/red), one-line description of progress, and the key risk or blocker if any.
- Decisions needed: Specific decisions that require leadership input. For each: what the decision is, what the options are, the trade-offs, and the deadline for deciding.
- Risks and escalations: Items that are not yet blocking but could become problems. Include the trigger condition and the mitigation in progress.
- Recommendation: Your suggested course of action based on the evidence in the source documents. State it clearly and briefly.
Follow these rules:
- Lead with the conclusion, not the background. Executives read top-down and may stop at any point.
- Use tables for structured comparisons. Do not describe in prose what a table can show in three columns.
- Attribute information to its source ("per the May 1 status report" or "from the incident post-mortem").
- Distinguish between facts from the source documents and your own analysis or recommendations. Label recommendations explicitly.
- Keep the briefing under 500 words unless covering more than five workstreams.
- Do not include operational details that are not relevant to the decision or risk being presented.
- If the source documents contradict each other, flag the contradiction rather than resolving it silently.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: redhat-et
- Source: redhat-et/skillimage
- License: Apache-2.0
- Homepage: http://skillimage.dev
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.