Kubernetes Network Root Cause Analysis
kubeshark/kubeshark
Investigates past Kubernetes incidents from Kubeshark traffic snapshots: takes captures, dissects API calls, extracts PCAPs and compares traffic over time.
Write clear customer-facing outage and service-disruption notifications.
Install Customer Outage Notice
$ npx skills add mohitagw15856/pm-claude-skills --skill customer-outage-notice -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills customer-outage-notice --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-outage-notice .claude/skills/customer-outage-notice && 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-outage-notice" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/customer-outage-notice into .claude/skills/customer-outage-notice/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-outage-notice", 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-outage-noticeType 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-outage-notice -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills customer-outage-notice --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-outage-notice .agents/skills/customer-outage-notice && 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-outage-notice" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/customer-outage-notice into .agents/skills/customer-outage-notice/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-outage-notice", 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-outage-notice -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills customer-outage-notice --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-outage-notice .cursor/skills/customer-outage-notice && 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-outage-notice" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/customer-outage-notice into .cursor/skills/customer-outage-notice/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-outage-notice", 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-outage-notice--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-outage-notice -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills customer-outage-notice --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-outage-notice .gemini/skills/customer-outage-notice && 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-outage-notice" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/customer-outage-notice into .gemini/skills/customer-outage-notice/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-outage-notice", 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-outage-noticeInstalls 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-outage-notice -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-outage-notice .github/skills/customer-outage-notice && 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-outage-notice" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/customer-outage-notice into .github/skills/customer-outage-notice/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-outage-notice", 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-outage-notice -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-outage-notice --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-outage-notice .opencode/skills/customer-outage-notice && 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-outage-notice" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/customer-outage-notice into .opencode/skills/customer-outage-notice/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-outage-notice", 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-outage-notice- GitHub stars
- 1.4k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 538 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Write clear customer-facing outage and service-disruption notifications.
- Asked to write an outage notice
- SKILL.md covers Working from a brief, Required Inputs, Output Format and Quality Checks, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- A status-page update
What it does
Customer Outage Notice is an agent skill from mohitagw15856/pm-claude-skills. Write clear customer-facing outage and service-disruption notifications. Use when asked to write an outage notice, a status-page update, a service-disruption email, a maintenance notice, or an incident update sequence. Produces status-page updates for each phase (investigating → identified → monitoring → resolved), a customer email, and a resolved/post-incident summary, in plain, reassuring language.
Its SKILL.md is about 1.1k 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. 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 an outage notice
- A status-page update
- A service-disruption email
- A maintenance notice
Example prompts
- “/customer-outage-notice”
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 Outage Notice loads about 1.1k tokens when it runs. Until then it costs about 107 tokens; SKILL.md has 538 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). 538 words, ~1,085 tokens.
Download SKILL.mdSave it as
.claude/skills/customer-outage-notice/SKILL.md (or your agent's skills folder).- name
- customer-outage-notice
- description
- Write clear customer-facing outage and service-disruption notifications. Use when asked to write an outage notice, a status-page update, a service-disruption email, a maintenance notice, or an incident update sequence. Produces status-page updates for each phase (investigating → identified → monitoring → resolved), a customer email, and a resolved/post-incident summary, in plain, reassuring language.
Customer Outage Notice Skill
During an outage, customers don't need engineering detail — they need to know you're aware, that you're on it,
and when you'll update them next. This skill writes the notifications across the whole incident lifecycle, in
calm, plain language that reduces support tickets instead of generating them. (For a security/data incident or
a PR crisis, use incident-public-statement or
pr-crisis-response.)
Working from a brief
Given "checkout is down for some users", produce the full set of phased notices anyway — infer the affected scope and a plausible update cadence, label assumptions, and bracket the specific facts (start time, services, ETA) to fill in. Never wait for full detail; teams paste these live and edit the brackets.
Required Inputs
Ask for these only if they aren't already provided (else infer and label):
- What's affected — which service/feature, and for whom (all users, a region, a plan).
- Severity — full outage, partial/degraded, or intermittent.
- Status — investigating, root cause known, fix deploying, or resolved.
- Timing — when it started and the next-update cadence (or ETA, if known).
- Channel — status page, email, in-app banner; and your voice.
Output Format
Outage Communications: [service]
1. Status-page updates — a short post for each phase, each timestamped and committing to a next-update time:
| Phase | Message (template) |
|---|---|
| Investigating | "We're investigating reports of [issue] affecting [scope]. Next update by [time]." |
| Identified | "We've identified the cause of [issue] and are working on a fix. [Scope] remains affected. Next update by [time]." |
| Monitoring | "A fix has been deployed and we're monitoring recovery. You may see [residual effect]. Next update by [time]." |
| Resolved | "This incident is resolved as of [time]. [Service] is operating normally. Thank you for your patience." |
2. Customer email — a slightly fuller version for direct notification: what's affected, what they can/can't do right now, any workaround, and where to follow live status.
3. In-app / banner line — one sentence for a status banner.
4. Resolved summary — a short post-incident note: what happened (plain language), the impact window, what you've done to prevent recurrence, and how to reach support if they're still affected. Keep it blameless and non-technical; link a full post-mortem if one exists.
Show full SKILL.md (187 more words)Show less
Quality Checks
- Every active-incident update commits to a specific next-update time
- Scope is stated honestly (who is and isn't affected) — no vague "some users" when you know more
- Language is plain and calm — no internal jargon, no over-technical root-cause mid-incident
- A workaround or "what you can do now" is included when one exists
- The resolved summary states the impact window and a prevention step
- Updates are written so a non-engineer on the team can post them as-is
Anti-Patterns
- Do not go quiet between updates — a "still working on it, next update by X" beats silence
- Do not minimise ("minor issue") when customers are clearly blocked — it erodes trust
- Do not dump engineering detail or assign blame in a live customer notice
- Do not promise an ETA you're not confident in — commit to an update time instead
- Do not forget the resolved message — leaving an incident "open" worries customers
Based On
Incident-communication practice — phased status updates (investigating/identified/monitoring/resolved), committed update cadence, and blameless plain-language summaries.
Example Trigger Phrases
- "Write an outage notice."
- "Write a status-page update for this incident."
- "Email customers about the service disruption."
- "Write a maintenance notice."
© 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-outage-notice of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Customer Outage Notice 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 Outage Notice this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Kubernetes Network Root Cause Analysiskubeshark/kubeshark | 12k | — | ~5.3k | Automated safety check: Pass | Apache-2.0 | |
| UModel Root Cause Analysisalibaba/UnifiedModel | 415 | — | ~1.9k | Automated safety check: Pass | Custom licence | |
| Learningskortix-ai/suna | 20k | — | ~1.1k | Automated safety check: Pass | Custom licence | |
| Nix Config Debugryan4yin/nix-config | 2.1k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Oncallpigweed-project/pigweed | 548 | — | ~963 | Automated safety check: Pass | Apache-2.0 |
Similar skills
UModel Root Cause Analysis
alibaba/UnifiedModel
Investigates a service incident to its root cause by querying a UModel object graph alongside metrics, logs, topology and recent deployments.
Learnings
kortix-ai/suna
The project's episodic memory: a timestamped ledger of rules paid for with real outages and near-misses, one entry per incident.
Nix Config Debug
ryan4yin/nix-config
A skill your agent uses when something here is broken or stops working: an eval or build error, a failed activation, a dead or restarting unit, a mihomo or DNS outage, an unreachable host or MicroVM…
Oncall
pigweed-project/pigweed
Pigweed oncall rotation runbooks and maintenance workflows (such as rolling CIPD client tools for b/315378787).
Axiom SRE Investigator
openclaw/clawhub
Investigates incidents and production problems with hypothesis-driven debugging, queries Axiom observability data when available, and keeps secrets out of commands and output.
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 Outage Notice
What does Customer Outage Notice do?
Write clear customer-facing outage and service-disruption notifications. Customer Outage Notice is an agent skill from mohitagw15856/pm-claude-skills. Write clear customer-facing outage and service-disruption notifications.
When should I use Customer Outage Notice?
Customer Outage Notice fits situations like: asked to write an outage notice; A status-page update; A service-disruption email; A maintenance notice.
How do I install Customer Outage Notice in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill customer-outage-notice -a claude-code`. Or copy the skill folder (skills/customer-outage-notice in mohitagw15856/pm-claude-skills) into .claude/skills/customer-outage-notice in your project. Claude Code loads it when a task matches its description.
How do I install Customer Outage Notice in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill customer-outage-notice -a codex`. Or copy the skill folder (skills/customer-outage-notice in mohitagw15856/pm-claude-skills) into .agents/skills/customer-outage-notice in your project. Codex loads it when a task matches its description.
Can I use Customer Outage Notice 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-outage-notice -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-outage-notice, .gemini/skills/customer-outage-notice, .github/skills/customer-outage-notice and .opencode/skills/customer-outage-notice in your project.
What does Customer Outage Notice need to run?
SKILL.md names no scripts, command-line tools or credentials: Customer Outage Notice is instructions for the agent only.
Does Customer Outage Notice 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 Outage Notice 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 Outage Notice use?
Customer Outage Notice 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 Outage Notice use?
About 1.1k tokens (SKILL.md is roughly 4.3k 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 Outage Notice?
Skills that share tags, products or a category with Customer Outage Notice: Kubernetes Network Root Cause Analysis (kubeshark/kubeshark, 12k stars), UModel Root Cause Analysis (alibaba/UnifiedModel, 415 stars), Learnings (kortix-ai/suna, 20k stars) and Nix Config Debug (ryan4yin/nix-config, 2.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Customer Outage Notice?
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.