Weekly executive report
Skill ClarentCinematics/Codex-Skills-for-Enterprise/skills/weekly-executive-report
npx -y skills add ClarentCinematics/Codex-Skills-for-Enterprise --skill weekly-executive-reportAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Synthesize scattered weekly updates, project notes, metrics, risks, and team reports into a concise executive-ready weekly report. Use when Codex needs to prepare leadership updates, operating reviews, weekly business reviews, board-style summaries, or cross-functional status narratives.
SKILL.md
1.8 KB, as published. Nobody here has run it
Weekly Executive Report
Workflow
- Identify the reporting period, audience, strategic priorities, and source material boundaries.
- Group updates by business outcome, initiative, team, or workstream depending on the source structure.
- Distinguish progress, measurable impact, risks, decisions needed, and next-week commitments.
- Remove low-signal activity narration unless it explains impact, risk, or required action.
- Produce a polished report with clear escalation points and accountable next steps.
Output Standard
Use this structure by default:
- Headline: one sentence describing the week.
- Executive Summary: 3-5 bullets focused on outcomes, risk, and decisions.
- Progress By Priority: concise updates grouped by priority or workstream.
- Metrics And Signals: reported numbers, trend direction, and caveats.
- Risks / Blockers: impact, owner, urgency, and support needed.
- Decisions Needed: decision, deadline, options, and recommended owner.
- Next Week Commitments: concrete outcomes expected next week.
Rules
- Do not overstate progress beyond the evidence provided.
- Preserve uncertainty when metrics are incomplete or qualitative.
- Escalate only items with business impact, timeline risk, resource risk, or executive dependency.
- Keep the report concise enough for a senior leader to scan in under five minutes.
References
Read references/report-patterns.md when the user asks for a board-facing, operating-review, or team-of-teams format.