Project Status Report Skill
Write a structured project status report for any project.
From the mohitagw15856/pm-claude-skills README — shows the whole collection, not only this skill. · view on GitHub
How to use it
Claude Code
- Run the line below. It pulls the whole folder into
~/.claude/skills/project-status-report. - Describe your job in plain words. Claude Code follows the skill from there.
Claude Code — installs the whole folder, not just SKILL.md
npx degit mohitagw15856/pm-claude-skills/skills/project-status-report#main ~/.claude/skills/project-status-reportFor one project only, change the path to .claude/skills/project-status-report.
Claude (web or desktop app)
- On this page open ⋯ → Download .md.
- Save it as SKILL.md in a folder, zip the folder, then Customize → Skills → + → Create skill → Upload a skill.
- Pick the file and Save. Claude shows the name and description and runs a security scan.
- Check the skill is switched on.
- Start a new chat and describe your job in plain words. The AI follows the skill from there.
ChatGPT or another app
- ChatGPT: make a Project and paste it into Instructions.
- Neither? Paste it at the top of a new chat — it works for that chat.
Not working?
- Check which app you pasted it into — the steps above name the right one.
- Some skills need the paid tier of Claude or ChatGPT.
Paste into Claude, ChatGPT or Cursor.
Source of Project Status Report Skill
Show the full text126 lines
| name | description |
|---|---|
| project-status-report | Write a structured project status report for any project. Use when asked to write a project update, status report, RAG report, project dashboard narrative, or weekly project communication. Produces a clear status report with RAG ratings, milestone progress, risks, and decisions needed. |
Project Status Report Skill
Produces a clear, structured project status report — the weekly communication that keeps stakeholders informed without requiring a meeting.
Required Inputs
- Project name
- Reporting period
- Current RAG status (Red / Amber / Green)
- Key milestones (due, delivered, coming)
- Issues or blockers
- Decisions needed from stakeholders
- Budget status (if tracked)
- Audience (steering committee / sponsor / PMO / full team)
Output Structure
Project Status Report: [Project Name]
Period: [Date range] | Author: [PM] | Next report: [Date]
Overall Status
| Dimension | Status | Last period | Trend |
|---|---|---|---|
| Overall | Red / Amber / Green | [Last] | Improving / Stable / Declining |
| Schedule | |||
| Budget | |||
| Scope | |||
| Risks |
RAG definitions:
- Green: On track. No significant issues.
- Amber: At risk. Issues identified but mitigations in place.
- Red: Off track. Escalation or decisions required to recover.
Executive Summary
[3-5 sentences. Headline story. If it is Red, say so immediately and why. Never bury bad news after good news.]
Milestone Progress
| Milestone | Due date | Status | Comment |
|---|---|---|---|
| [Milestone] | [Date] | Complete / At risk / Delayed / On track | [One line] |
Completed this period: [What was delivered] Due next period: [What is expected]
Issues and Blockers
[Issue title] — Critical / High / Low
- Description: [What the issue is]
- Impact: [What happens if unresolved]
- Owner: [Who is resolving]
- Action: [What is being done]
- Resolution date: [When it will be closed]
Risks
| Risk | Likelihood | Impact | Mitigation | Owner |
|---|---|---|---|---|
| [Risk] | H/M/L | H/M/L | [Action] | [Name] |
Decisions Required
| Decision | Background | Options | Recommendation | Needed by |
|---|---|---|---|---|
| [Decision] | [Context] | [Options] | [Recommendation] | [Date] |
Budget Summary
| Budget | Actual to date | Forecast | Variance | |
|---|---|---|---|---|
| Total | £ | £ | £ | £ F/A |
Next Period Plan
[3-5 specific bullet points — what will happen next period]
Writing Rules
- Never soften a Red status
- Milestones are binary: complete or not complete
- Decisions must be genuinely actionable
- Keep to one page where possible
Quality Checks
- Red status is stated immediately (not buried after positives)
- Every issue has a named owner and a resolution date
- Decisions required are genuinely actionable by the audience
- Milestones are binary (complete or not complete — no "85% done")
- Executive summary can stand alone for a stakeholder who reads nothing else
Anti-Patterns
- Do not rate project health as Green while listing unresolved critical blockers
- Do not report milestone progress as a percentage — milestones are binary: complete or not complete
- Do not bury risks at the bottom — if something is high risk, it belongs in the executive summary
- Do not leave decisions required without specifying who must decide and by when
- Do not write an executive summary that requires reading the full report to understand — it must stand alone
Example Trigger Phrases
- "Write a project status report for [project]"
- "Generate a RAG status update for [project]"
- "Write the steering committee report for [project]"
| 1 | |
| 2 | name project-status-report |
| 3 | description "Write a structured project status report for any project. Use when asked to write a project update, status report, RAG report, project dashboard narrative, or weekly project communication. Produces a clear status report with RAG ratings, milestone progress, risks, and decisions needed." |
| 4 | |
| 5 | |
| 6 | # Project Status Report Skill |
| 7 | |
| 8 | Produces a clear, structured project status report — the weekly communication that keeps stakeholders informed without requiring a meeting. |
| 9 | |
| 10 | ## Required Inputs |
| 11 | **Project name** |
| 12 | **Reporting period** |
| 13 | **Current RAG status** (Red / Amber / Green) |
| 14 | **Key milestones** (due, delivered, coming) |
| 15 | **Issues or blockers** |
| 16 | **Decisions needed from stakeholders** |
| 17 | **Budget status** (if tracked) |
| 18 | **Audience** (steering committee / sponsor / PMO / full team) |
| 19 | |
| 20 | ## Output Structure |
| 21 | |
| 22 | |
| 23 | |
| 24 | # Project Status Report: [Project Name] |
| 25 | **Period:** [Date range] | **Author:** [PM] | **Next report:** [Date] |
| 26 | |
| 27 | |
| 28 | |
| 29 | ### Overall Status |
| 30 | |
| 31 | | Dimension | Status | Last period | Trend | |
| 32 | |---|---|---|---| |
| 33 | | Overall | Red / Amber / Green | [Last] | Improving / Stable / Declining | |
| 34 | | Schedule | | | | |
| 35 | | Budget | | | | |
| 36 | | Scope | | | | |
| 37 | | Risks | | | | |
| 38 | |
| 39 | RAG definitions: |
| 40 | Green: On track. No significant issues. |
| 41 | Amber: At risk. Issues identified but mitigations in place. |
| 42 | Red: Off track. Escalation or decisions required to recover. |
| 43 | |
| 44 | |
| 45 | |
| 46 | ### Executive Summary |
| 47 | [3-5 sentences. Headline story. If it is Red, say so immediately and why. Never bury bad news after good news.] |
| 48 | |
| 49 | |
| 50 | |
| 51 | ### Milestone Progress |
| 52 | |
| 53 | | Milestone | Due date | Status | Comment | |
| 54 | |---|---|---|---| |
| 55 | | [Milestone] | [Date] | Complete / At risk / Delayed / On track | [One line] | |
| 56 | |
| 57 | **Completed this period:** [What was delivered] |
| 58 | **Due next period:** [What is expected] |
| 59 | |
| 60 | |
| 61 | |
| 62 | ### Issues and Blockers |
| 63 | |
| 64 | **[Issue title] — Critical / High / Low** |
| 65 | **Description:** [What the issue is] |
| 66 | **Impact:** [What happens if unresolved] |
| 67 | **Owner:** [Who is resolving] |
| 68 | **Action:** [What is being done] |
| 69 | **Resolution date:** [When it will be closed] |
| 70 | |
| 71 | |
| 72 | |
| 73 | ### Risks |
| 74 | |
| 75 | | Risk | Likelihood | Impact | Mitigation | Owner | |
| 76 | |---|---|---|---|---| |
| 77 | | [Risk] | H/M/L | H/M/L | [Action] | [Name] | |
| 78 | |
| 79 | |
| 80 | |
| 81 | ### Decisions Required |
| 82 | |
| 83 | | Decision | Background | Options | Recommendation | Needed by | |
| 84 | |---|---|---|---|---| |
| 85 | | [Decision] | [Context] | [Options] | [Recommendation] | [Date] | |
| 86 | |
| 87 | |
| 88 | |
| 89 | ### Budget Summary |
| 90 | |
| 91 | | | Budget | Actual to date | Forecast | Variance | |
| 92 | |---|---|---|---|---| |
| 93 | | Total | £ | £ | £ | £ F/A | |
| 94 | |
| 95 | |
| 96 | |
| 97 | ### Next Period Plan |
| 98 | [3-5 specific bullet points — what will happen next period] |
| 99 | |
| 100 | ## Writing Rules |
| 101 | Never soften a Red status |
| 102 | Milestones are binary: complete or not complete |
| 103 | Decisions must be genuinely actionable |
| 104 | Keep to one page where possible |
| 105 | |
| 106 | ## Quality Checks |
| 107 | |
| 108 | [ ] Red status is stated immediately (not buried after positives) |
| 109 | [ ] Every issue has a named owner and a resolution date |
| 110 | [ ] Decisions required are genuinely actionable by the audience |
| 111 | [ ] Milestones are binary (complete or not complete — no "85% done") |
| 112 | [ ] Executive summary can stand alone for a stakeholder who reads nothing else |
| 113 | |
| 114 | ## Anti-Patterns |
| 115 | |
| 116 | [ ] Do not rate project health as Green while listing unresolved critical blockers |
| 117 | [ ] Do not report milestone progress as a percentage — milestones are binary: complete or not complete |
| 118 | [ ] Do not bury risks at the bottom — if something is high risk, it belongs in the executive summary |
| 119 | [ ] Do not leave decisions required without specifying who must decide and by when |
| 120 | [ ] Do not write an executive summary that requires reading the full report to understand — it must stand alone |
| 121 | |
| 122 | ## Example Trigger Phrases |
| 123 | "Write a project status report for [project]" |
| 124 | "Generate a RAG status update for [project]" |
| 125 | "Write the steering committee report for [project]" |
| 126 |
Discussion
/ar:ar-status — Experiment DashboardShow experiment dashboard with results, active loops, and progress. Use when the user runs /ar:ar-status or asks how an autoresearch experiment is going.Analytics dashboardTurn a LinkedIn Analytics export into an interactive dark-themed React dashboard plus a written strategic analysis with 5 data-backed content recommendations. Reads every sheet in the export, builds charts for engagement trend, follower growth, post performance scatter, day-of-week heatmap, and audience breakdown. Use this skill whenever the user says "analyse my linkedin", "linkedin analytics", "build my dashboard", "review my performance", or uploads a LinkedIn Analytics export file. Requires the user's LinkedIn Analytics export (xlsx) as input.Earnings Preview SkillGenerate a pre-earnings briefing for any stock using Yahoo Finance data. Use this skill whenever the user wants to prepare for an upcoming earnings report, understand what analysts expect, review a company's beat/miss track record, or get a quick overview before an earnings call. Triggers include: "earnings preview for AAPL", "what to expect from TSLA earnings", MSFT reports next week", "earnings preview", "pre-earnings analysis", what are analysts expecting for NVDA", "earnings estimates for", will GOOGL beat earnings", "earnings beat/miss history", upcoming earnings", "before earnings", "earnings setup", consensus estimates", "earnings whisper", "EPS expectations", what's the street expecting", "earnings season preview", any mention of preparing for or previewing an earnings report, or any request to understand expectations ahead of a company's earnings date. Always use this skill when the user mentions a ticker in context of upcoming earnings, even if they don't say "preview" explicitly.Path A — List-styleSave the results of an in-chat data-exploration session as a TL report. Triggers when the user wants to persist a channels / brands / videos (uploads) / sponsorships list or filtered set they've been working with — phrases like "save this as a report", "save the list", "turn this into a campaign", "persist this", "make a report from what you found", "save the result", "I want to come back to this".
Browse more free Claude skills or everything in Data & analytics.