Status Update
Create concise audience-tuned status updates that preserve the ask, risk, timing, and next milestone.
Free
Works with the AI tools you already use
Claude Code
Cursor
Codex CLI
GitHub Copilot
Gemini CLI+20 moreClaude CodeCursorCodex CLIGitHub CopilotGemini CLI
OpenClaw
Manus
Grok+17 agentsStatus Update
Example session with this skill installed
Generate an executive status update based on the last two days of Slack chatter about the API migration. We hit a database lock issue but resolved it. We are 2 days behind schedule now.
- Read your context and instructions
- Compiled the status update
- Generated the document
I have synthesized the Slack context regarding the API migration. The update highlights the resolved database issue while clearly communicating the resulting two-day delay to the executive team.
Project Status: API Migration
Conversation State: Post-incident resolution and schedule recalibration.
Status: Yellow (Delayed)
What Changed: Database locking issues identified during the staging migration were successfully patched and verified.
Progress: Staging migration is 100% complete; production cutover prep has begun.
Risks / Blockers: No active blockers. The primary risk is the compressed testing window for the production environment.
Stakeholder Sensitivities: High sensitivity to the go-live date; the two-day slip impacts the marketing launch window.
Asks: Approval for 4 hours of developer overtime on Friday to recover 50% of the lost time.
Next Milestone: Production environment dry-run scheduled for Wednesday at 10:00 AM.
Executive Version (Send-ready)
Subject: Status Update: API Migration Schedule Adjustment
The team has successfully resolved the database locking issues encountered during the staging phase. While the technical fix is verified, the troubleshooting process has resulted in a two-day delay to the overall timeline. We are currently prepping for the production cutover. To mitigate further delays, we are requesting a brief period of overtime this Friday to recover lost ground. The production dry-run remains set for Wednesday morning.
Next steps
- Review the executive version for tone.
- Confirm if the overtime request should be included in the final send.
- Verify the production dry-run time with the DevOps lead.
status-update.pdf
PDF · document
Example file from a real run - the skill writes it into your workspace.
Connects securely to your tools. The creator never sees your data.
About this skill
Project communication often collapses under the weight of messy Slack threads, fragmented email chains, and incomplete meeting notes. This skill extracts the signal from the noise to generate concise, accurate status updates for stakeholders at every level.
What it does
- Multi-audience tailoring adapt updates for teams, managers, executives, or external partners.
- Context synthesis processes raw ticket data, chat logs, and meeting notes into a coherent narrative.
- Risk isolation distinguishes between internal risks and external blockers to prevent miscommunication.
- Gap detection identifies missing information and labels assumptions to maintain data integrity.
- Progress tracking summarizes recent changes and defines the next immediate milestone.
How it works
- Provide the raw project context, such as a Slack export, email thread, or ticket description.
- Specify the target audience mode: team, manager, executive, or customer.
- Review the generated analysis of state, progress, and stakeholder sensitivities.
- Select the suggested audience-specific version for immediate delivery.
Frameworks & tools
Works with text-based inputs from Jira, Linear, Slack, Microsoft Teams, and email clients.
Why this beats prompting it yourself
Generic prompts often miss the nuance between a technical blocker and a project risk, leading to alarming updates for executives. This skill enforces a strict separation of concerns and explicitly identifies information gaps that manual prompting often overlooks.
Use cases
- Drafting weekly executive summaries from a week of chaotic engineering logs.
- Converting a technical incident report into a professional customer-facing update.
- Syncing a cross-functional team on progress after a long design sprint.
- Preparing a manager-level report that highlights resource needs without burying the lead.
Known limitations
Does not support direct API integration for automated posting; requires manual review and copy-pasting. Accuracy depends on the quality of provided conversation logs.
How to install
Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.
- 1
Download the ZIP
Free skills download straight away. Paid skills unlock right after purchase.
- 2
Unzip into your skills folder
Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.
- 3
Ask your agent to use it
Restart the agent if it was already running. It picks the skill up automatically - no config needed.
Skills folder by agent
Click the path to copy it. Create the folder if it does not exist yet.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free forever
No account required to browse
Trust & safety
Security scanned
Verified clean 1 day ago
- Free to download with an account