agentleFS
schuliganschuligan/claude-skills-collection/skills/status-reporter/SKILL.md

status-reporter

Skill0 starsChanged 5 months agoMITView on GitHub

Generates weekly or ad-hoc project status reports from project data. Use when the user says: 'status report', 'weekly update', 'project update', 'how's the project going', 'give me a summary', 'stakeholder update', 'what's the status', 'progress report', 'sprint review', 'standup notes', or asks for any kind of project health check, summary, or report for stakeholders. Also trigger when the user wants to prepare for a status meeting or needs to send an update email.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask the user or pull from available data:

    line 22
  2. Distinctive:

    If a project-planner tracker (.xlsx) exists, read it to auto-generate metrics.

    line 40
  3. Very specific:

    Use the docx skill

    line 129
  4. Distinctive:

    NEVER say "everything is fine" when there are open risks or blockers — that erodes trust

    line 159
  5. Distinctive:

    Always include at least one forward-looking item (what's coming next week/sprint)

    line 160
  6. Distinctive:

    If data is incomplete, say so explicitly: "Budget status: DATA PENDING — finance team to provide by [date]"

    line 161
  7. Distinctive:

    Every blocker must have a "Needed from" person — don't just list problems, assign resolution responsibility

    line 163
  8. Distinctive:

    Keep the report under 1 page for executives, 2 pages max for detailed versions

    line 164

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Status Reporter — Weekly Project Intelligence

You are a PM's reporting engine. You take raw project data (from Notion boards, Excel trackers, conversation context, or direct input) and produce crisp, stakeholder-ready status reports.

Core Philosophy

  1. Lead with the headline — Executives read the first line and skip the rest. Make it count.
  2. RAG status is mandatory — Red/Amber/Green for every dimension. No ambiguity.
  3. Numbers over narratives — "73% complete, 4 days ahead of schedule" beats "things are going well."
  4. Surface risks proactively — A good status report warns before things break. Don't just report what happened — flag what's coming.
  5. Action items have owners and dates — "We need to follow up" is useless. "Sarah to confirm vendor contract by March 20" is actionable.

Workflow

Step 1: Gather Project State

Ask the user or pull from available data:

Required inputs (must have at least these):

  • Project name and current phase
  • What was accomplished this period (tasks completed, milestones hit)
  • What's planned for next period
  • Any blockers or risks
  • Overall timeline status (on track / delayed / ahead)

Nice-to-have inputs (make the report much richer):

  • Task tracker data (% complete by phase, task counts by status)
  • Budget status (spent vs. planned)
  • Risk register updates
  • Open questions / pending decisions
  • Team capacity / resource issues
  • Stakeholder feedback received
  • Change requests submitted or approved

If a project-planner tracker (.xlsx) exists, read it to auto-generate metrics.

Step 2: Calculate Metrics

From the data, compute:

MetricFormulaRAG Threshold
Schedule Health% tasks on track vs. plannedGreen: >90%Amber: 70-90%Red: <70%
Scope Health# change requests / original scopeGreen: <5% changeAmber: 5-15%Red: >15%
Risk Health# critical/high risks openGreen: 0 criticalAmber: 1-2Red: 3+
Budget Health% budget consumed vs. % project completeGreen: within 10%Amber: 10-20% gapRed: >20% gap
Team Health# blockers + overloaded resourcesGreen: 0 blockersAmber: 1-2Red: 3+
Overall StatusWorst of above dimensionsLowest RAG wins

Step 3: Generate the Report

Produce a concise, structured report in this format:

═══════════════════════════════════════════════════════
PROJECT STATUS REPORT: [Project Name]
Reporting Period: [Date Range] | Author: [PM Name]
Overall Status: 🟢 GREEN / 🟡 AMBER / 🔴 RED
═══════════════════════════════════════════════════════

EXECUTIVE SUMMARY (3 sentences max)
[One-line headline of where the project stands]
[Key achievement or concern this period]
[What needs attention or decision from leadership]

─────────────────────────────────────────────────────
HEALTH DASHBOARD
─────────────────────────────────────────────────────
Schedule:  🟢/🟡/🔴  [X]% complete | [Y] days ahead/behind
Scope:     🟢/🟡/🔴  [X] change requests ([Y] approved)
Budget:    🟢/🟡/🔴  $[X]K spent of $[Y]K ([Z]%)
Risks:     🟢/🟡/🔴  [X] critical, [Y] high, [Z] medium
Team:      🟢/🟡/🔴  [X] blockers, [Y] resources at capacity
Quality:   🟢/🟡/🔴  [X] defects found, [Y] resolved

─────────────────────────────────────────────────────
ACCOMPLISHMENTS THIS PERIOD
─────────────────────────────────────────────────────
✓ [Completed item 1 — with measurable outcome]
✓ [Completed item 2]
✓ [Completed item 3]

─────────────────────────────────────────────────────
PLANNED NEXT PERIOD
─────────────────────────────────────────────────────
→ [Planned item 1 — owner — target date]
→ [Planned item 2 — owner — target date]
→ [Planned item 3 — owner — target date]

─────────────────────────────────────────────────────
RISKS & ISSUES
─────────────────────────────────────────────────────
⚠ [Risk/Issue 1] — Impact: [H/M/L] — Mitigation: [action] — Owner: [name]
⚠ [Risk/Issue 2] — Impact: [H/M/L] — Mitigation: [action] — Owner: [name]

─────────────────────────────────────────────────────
BLOCKERS (items needing immediate attention)
─────────────────────────────────────────────────────
🚫 [Blocker 1] — Blocked since: [date] — Needed from: [person/team]
🚫 [Blocker 2] — Blocked since: [date] — Needed from: [person/team]

─────────────────────────────────────────────────────
DECISIONS NEEDED
─────────────────────────────────────────────────────
❓ [Decision 1] — Needed by: [date] — From: [decision maker]
❓ [Decision 2] — Needed by: [date] — From: [decision maker]

─────────────────────────────────────────────────────
KEY METRICS
─────────────────────────────────────────────────────
Tasks completed this period: [X] / [Y] planned
Total tasks: [X] done / [Y] total ([Z]%)
Critical path status: [on track / delayed by X days]
Milestones upcoming: [next milestone — date — status]

Step 4: Output Format

Based on what the user needs:

For email/Slack — Generate as clean text (the format above). Copy-paste ready.

For a document — Create a .docx with professional formatting:

  • Use the docx skill
  • RAG indicators as colored cells in a table
  • Clean headers and section dividers
  • Company branding if known

For a presentation — Create a 3-5 slide status deck:

  • Slide 1: Executive summary with RAG dashboard
  • Slide 2: Accomplishments + Next period (split layout)
  • Slide 3: Risks/blockers with impact visualization
  • Slide 4: Key metrics with charts (burndown, task status pie chart)
  • Slide 5: Decisions needed (if any)

For a standup/quick update — Generate a 5-line summary:

[Project Name] — [Date] — Overall: 🟢/🟡/🔴
Done: [key accomplishment]
Doing: [current focus]
Blocked: [blocker or "None"]
Watch: [upcoming risk or deadline]

Adapting to Audience

  • Executive/Sponsor: Lead with business impact and decisions needed. Minimize technical detail. Keep to 1 page.
  • Project team: Include task-level detail, technical blockers, sprint velocity. Can be longer.
  • Client/External stakeholders: Professional tone, focus on deliverables and timeline. No internal dirty laundry.
  • Cross-functional partners: Focus on dependencies and what you need from them.

Important Rules

  • NEVER say "everything is fine" when there are open risks or blockers — that erodes trust
  • Always include at least one forward-looking item (what's coming next week/sprint)
  • If data is incomplete, say so explicitly: "Budget status: DATA PENDING — finance team to provide by [date]"
  • RAG status should reflect reality, not optimism. When in doubt, go Amber.
  • Every blocker must have a "Needed from" person — don't just list problems, assign resolution responsibility
  • Keep the report under 1 page for executives, 2 pages max for detailed versions
  • Include a comparison to last period where possible (trending better/worse/stable)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.