Oncall
pigweed-project/pigweed
Pigweed oncall rotation runbooks and maintenance workflows (such as rolling CIPD client tools for b/315378787).
Write the customer-facing incident update during an outage — status-page post or email — that's honest about impact without over-promising.
Install Customer Incident Update
$ npx skills add mohitagw15856/pm-claude-skills --skill customer-incident-update -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills customer-incident-update --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/customer-incident-update .claude/skills/customer-incident-update && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "customer-incident-update" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/customer-incident-update into .claude/skills/customer-incident-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-incident-update", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/customer-incident-updateType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill customer-incident-update -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills customer-incident-update --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/customer-incident-update .agents/skills/customer-incident-update && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "customer-incident-update" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/customer-incident-update into .agents/skills/customer-incident-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-incident-update", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill customer-incident-update -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills customer-incident-update --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/customer-incident-update .cursor/skills/customer-incident-update && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "customer-incident-update" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/customer-incident-update into .cursor/skills/customer-incident-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-incident-update", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/customer-incident-update--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill customer-incident-update -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills customer-incident-update --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/customer-incident-update .gemini/skills/customer-incident-update && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "customer-incident-update" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/customer-incident-update into .gemini/skills/customer-incident-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-incident-update", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills customer-incident-updateInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill customer-incident-update -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/customer-incident-update .github/skills/customer-incident-update && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "customer-incident-update" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/customer-incident-update into .github/skills/customer-incident-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-incident-update", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill customer-incident-update -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills customer-incident-update --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/customer-incident-update .opencode/skills/customer-incident-update && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "customer-incident-update" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/customer-incident-update into .opencode/skills/customer-incident-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-incident-update", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
customer-incident-update- GitHub stars
- 1.4k
- Token cost
- ~972 tokens
- SKILL.md length
- 464 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Write the customer-facing incident update during an outage — status-page post or email — that's honest about impact without over-promising.
- Works in 5 steps: Match the tense to the stage. "We're… → Impact before cause. Customers care… → Commit to the next update, not the fix.… → …
- Asked to write a status page update
- SKILL.md covers What This Skill Produces, Required Inputs, Framework: Honest Status Comms and Output Format, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Customer Incident Update is an agent skill from mohitagw15856/pm-claude-skills. Write the customer-facing incident update during an outage — status-page post or email — that's honest about impact without over-promising. Use when asked to write a status page update, draft customer comms for an outage, post an incident notice, or tell customers about downtime. Produces the update in the right tense for the incident stage (investigating / identified / monitoring / resolved), with impact scope, any workaround, and a concrete next-update time. Distinct from incident-postmortem (the internal retro).
Its SKILL.md is about 970 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering Incident response and Runbooks and postmortems. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to write a status page update
- Draft customer comms for an outage
- Post an incident notice
- Tell customers about downtime
Example prompts
- “/customer-incident-update”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Match the tense to the stage. "We're investigating" ≠ "we've identified" ≠ "we're monitoring the fix." Don't skip ahead.
- Impact before cause. Customers care what's broken for them; causes come in the postmortem, not mid-incident.
- Commit to the next update, not the fix. "Next update by 15:00 UTC" is a promise you can keep; "fixed within the hour" often isn't.
- No speculation. If you don't know the cause, say you're investigating — a wrong guess published is worse than an honest unknown.
- Own it plainly. Brief, human, no corporate throat-clearing; apologise once, then inform.
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Customer Incident Update loads about 972 tokens when it runs. Until then it costs about 136 tokens; SKILL.md has 464 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 464 words, ~972 tokens.
Download SKILL.mdSave it as
.claude/skills/customer-incident-update/SKILL.md (or your agent's skills folder).- name
- customer-incident-update
- description
- Write the customer-facing incident update during an outage — status-page post or email — that's honest about impact without over-promising. Use when asked to write a status page update, draft customer comms for an outage, post an incident notice, or tell customers about downtime. Produces the update in the right tense for the incident stage (investigating / identified / monitoring / resolved), with impact scope, any workaround, and a concrete next-update time. Distinct from incident-postmortem (the internal retro).
Customer Incident Update
During an outage, silence is the second failure. But the customer update is its own craft: say what's affected without guessing at causes, commit to a next-update time you can keep, and never promise a fix-by you don't control. This writes the post for the stage you're in — the messy middle included — so customers feel informed, not managed.
What This Skill Produces
- The update, in the tense of the current stage (investigating / identified / monitoring / resolved)
- The impact line — who and what is affected, in the customer's terms
- The workaround — if one exists, stated plainly
- The next-update commitment — a specific time, always
- Channel variants — a terse status-page version and a fuller email if needed
Required Inputs
Ask for these if not provided:
- Stage — investigating, identified, monitoring, or resolved
- Impact — which product/region/customers, and what they can't do right now
- What's known — only what you're confident of; unknowns stay unknown in the post
- Workaround — any, or none
- Audience — all customers, affected only, or enterprise accounts (tone shifts)
Framework: Honest Status Comms
- Match the tense to the stage. "We're investigating" ≠ "we've identified" ≠ "we're monitoring the fix." Don't skip ahead.
- Impact before cause. Customers care what's broken for them; causes come in the postmortem, not mid-incident.
- Commit to the next update, not the fix. "Next update by 15:00 UTC" is a promise you can keep; "fixed within the hour" often isn't.
- No speculation. If you don't know the cause, say you're investigating — a wrong guess published is worse than an honest unknown.
- Own it plainly. Brief, human, no corporate throat-clearing; apologise once, then inform.
Output Format
Status-page post
[Investigating/Identified/Monitoring/Resolved] — [title] · [timestamp] [Impact: who/what]. [What we're doing]. [Workaround, if any]. Next update by [time].
Show full SKILL.md (178 more words)Show less
Email (if broader comms needed)
- Subject: [clear, non-alarmist]
- Body: impact → status → workaround → next update → apology
- Sign-off
Update ladder (for the incident's life)
- The follow-on posts you'll publish as the stage changes, pre-drafted
Quality Checks
- The tense matches the actual stage — no claiming a fix that isn't confirmed
- Impact is stated in customer terms, up top
- A specific next-update time is given
- No cause is speculated when it isn't known
- No fix-by time is promised that depends on an unknown
- Tone is human and brief — one apology, no jargon
Anti-Patterns
- "Some users may be experiencing issues" when it's a full outage — minimising erodes trust faster than the outage.
- Promising a resolution time you can't control.
- Publishing a guessed cause that turns out wrong.
- No next-update time — leaves customers refreshing in the dark.
- Skipping stages — jumping to "resolved" before monitoring confirms it.
Example Trigger Phrases
- "Write a status page update — we're investigating an outage."
- "Draft customer comms for the API downtime, identified stage."
- "Post an incident notice for enterprise accounts."
- "We've deployed a fix and are monitoring — write the update."
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/customer-incident-update of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Customer Incident Update next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Customer Incident Update this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~972 | Automated safety check: Pass | MIT | |
| Oncallpigweed-project/pigweed | 548 | — | ~963 | Automated safety check: Pass | Apache-2.0 | |
| Activation Governance Chaos RolloutAli-Marandi/DataSense | 107 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Incident Response686f6c61/alfred-dev | 117 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Superset Incident Triagesuperset-sh/superset | 15k | — | ~1k | Automated safety check: Pass | Custom licence | |
| Post-Incident DebriefVeryGoodOpenSource/vgv-wingspan | 109 | — | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
Activation Governance Chaos Rollout
Ali-Marandi/DataSense
Design, validate, and govern fail-closed customer-activation automations that use an Outbox/worker pattern.
Incident Response
686f6c61/alfred-dev
Protocolo de respuesta ante incidentes en produccion: triaje, mitigacion, causa raiz y postmortem.
Superset Incident Triage
superset-sh/superset
Does a read-only first pass on a possible production incident: gathers deploy, Sentry and health-check signals, proposes a severity and status message, then stops for human approval.
Post-Incident Debrief
VeryGoodOpenSource/vgv-wingspan
Produces a blameless post-incident debrief with timeline, root cause and follow-up actions after an outage, failed release or significant bug, while details are fresh.
SRE Engineer
Jeffallan/claude-skills
Defines SLIs, SLOs and error budgets, and sets up golden-signal monitoring, blameless postmortems, toil automation and chaos experiments for production systems.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Categories
Questions about Customer Incident Update
What does Customer Incident Update do?
Write the customer-facing incident update during an outage — status-page post or email — that's honest about impact without over-promising. Customer Incident Update is an agent skill from mohitagw15856/pm-claude-skills. Write the customer-facing incident update during an outage — status-page post or email — that's honest about impact without over-promising.
When should I use Customer Incident Update?
Customer Incident Update fits situations like: asked to write a status page update; draft customer comms for an outage; post an incident notice; tell customers about downtime.
How do I install Customer Incident Update in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill customer-incident-update -a claude-code`. Or copy the skill folder (skills/customer-incident-update in mohitagw15856/pm-claude-skills) into .claude/skills/customer-incident-update in your project. Claude Code loads it when a task matches its description.
How do I install Customer Incident Update in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill customer-incident-update -a codex`. Or copy the skill folder (skills/customer-incident-update in mohitagw15856/pm-claude-skills) into .agents/skills/customer-incident-update in your project. Codex loads it when a task matches its description.
Can I use Customer Incident Update in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill customer-incident-update -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/customer-incident-update, .gemini/skills/customer-incident-update, .github/skills/customer-incident-update and .opencode/skills/customer-incident-update in your project.
What does Customer Incident Update need to run?
SKILL.md names no scripts, command-line tools or credentials: Customer Incident Update is instructions for the agent only.
Does Customer Incident Update access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Customer Incident Update safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Customer Incident Update use?
Customer Incident Update is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Customer Incident Update use?
About 972 tokens (SKILL.md is roughly 3.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Customer Incident Update?
Skills that share tags, products or a category with Customer Incident Update: Oncall (pigweed-project/pigweed, 548 stars), Activation Governance Chaos Rollout (Ali-Marandi/DataSense, 107 stars), Incident Response (686f6c61/alfred-dev, 117 stars) and Superset Incident Triage (superset-sh/superset, 15k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Customer Incident Update?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.