Status Update Writer
Use when the user asks to write a status update, weekly or monthly update, stakeholder update, project update, standup, status report, or QBR. Do NOT use for writing a PRD or a retro doc — those need different structures.
Install
npx skills add aakashg/pm-claude-skills --skill status-update-writergit clone --depth 1 https://github.com/aakashg/pm-claude-skills.git /tmp/pm-claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/pm-claude-skills/skills/status-update-writer ~/.claude/skills/status-update-writerPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Status Update Writer Turn messy notes into a precise stakeholder update that stands alone without a follow-up meeting. ## Step 0 — Read first | Source | Path | What to extract | |--------|------|-----------------| | User's raw notes | whatever they pasted | What actually shipped, real numbers, real dates, real names | | Project context | `CLAUDE.md` | North star metrics, OKRs, company terminology, audience norms | | Cadence formats | `references/cadences.md` | Daily / monthly / QBR variants of the base format | | Last update | any prior update they name | What was promised last week — the delta is the story | | Metrics source | dashboard link or data they provide | Current values only. Never estimate a metric. | If the user gave you no numbers, the update stays qualitative and you say so. Do not fill the gap. ## Constraints Mandatory. - Total update under 200 words for the weekly default. - Never fabricate progress. If the notes are thin, the update is thin. - Never hide bad news. It goes in the TL;DR, never at the bottom. - Never report activity as progress. "Had 6 meetings about the migration" is activity. "Migrated 40% of users at 0.3% error rate" is progress. - Every risk gets a mitigation. An unmitigated risk is just anxiety. - Every blocker gets a named owner and a date. - Every decision request gets a recommendation with reasoning. - Active voice only. "Team shipped the migration," not "The migration was completed."
Details
- Skill name
status-update-writer- Repository
- aakashg/pm-claude-skills
- Path
skills/status-update-writer/SKILL.md- License
- MIT
- Repo updated
- 8 August 2026
FAQ
What does the Status Update Writer skill do?
Use when the user asks to write a status update, weekly or monthly update, stakeholder update, project update, standup, status report, or QBR. Do NOT use for writing a PRD or a retro doc — those need different structures.
How do I install the Status Update Writer skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add aakashg/pm-claude-skills --skill status-update-writer. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Status Update Writer popular?
It lives in aakashg/pm-claude-skills, which has 116 GitHub stars and 35 forks.
Related skills
Idea Validator
116aakashg/pm-claude-skills
Use when the user asks to validate a product idea, stress-test an idea, evaluate whether an idea is good, or decide whether to build something. Do NOT use for prioritizing an existing backlog or reviewing a shipped feature — those need RICE scoring or a design review instead.
Linkedin Post Writer
116aakashg/pm-claude-skills
Use when the user asks to write, draft, or rewrite a LinkedIn post, turn notes or an article into a LinkedIn post, or fix a hook that is not landing. Do NOT use for X/Twitter threads, newsletters, or blog posts — those need different length and hook rules.
Product Designer
116aakashg/pm-claude-skills
Use when the user asks to review a design, critique a UI or mockup, give design feedback, or check a screen for usability and accessibility issues. Do NOT use for visual brand or aesthetic preference debates, or for reviewing copy before layout is settled.
Digital Estate Planner
272curiositech/some_claude_skills
Organizing digital life for legacy, emergency access, and death preparedness. Specializes in password management, account documentation, digital asset preservation, and ensuring loved ones can access what they need.
Review Spec
155serpro69/claude-toolbox
Use after implementing tasks or mid-feature to verify code matches design docs and ensure they are in sync. Detects spec deviations, missing implementations, doc inconsistencies, and outdated docs in design and implementation documentation.
Hiring Manager Deep Dive
272curiositech/some_claude_skills
Prepares for hiring manager rounds at Staff+ (L6+) level — scope of impact, influence without authority, ambiguity navigation, mentorship, strategic thinking. Use when practicing HM rounds or calibrating story depth for target level. Activate on "hiring manager round", "HM screen", "staff level", "scope of impact". NOT for coding interviews, system design, behavioral/values rounds, or resume writing.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.