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 a single clear, honest public statement about an incident.
Install Incident Public Statement
$ npx skills add mohitagw15856/pm-claude-skills --skill incident-public-statement -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills incident-public-statement --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/incident-public-statement .claude/skills/incident-public-statement && 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 "incident-public-statement" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/incident-public-statement into .claude/skills/incident-public-statement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "incident-public-statement", 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/incident-public-statementType 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 incident-public-statement -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills incident-public-statement --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/incident-public-statement .agents/skills/incident-public-statement && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "incident-public-statement" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/incident-public-statement into .agents/skills/incident-public-statement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "incident-public-statement", 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 incident-public-statement -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills incident-public-statement --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/incident-public-statement .cursor/skills/incident-public-statement && 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 "incident-public-statement" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/incident-public-statement into .cursor/skills/incident-public-statement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "incident-public-statement", 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/incident-public-statement--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 incident-public-statement -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills incident-public-statement --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/incident-public-statement .gemini/skills/incident-public-statement && 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 "incident-public-statement" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/incident-public-statement into .gemini/skills/incident-public-statement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "incident-public-statement", 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 incident-public-statementInstalls 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 incident-public-statement -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/incident-public-statement .github/skills/incident-public-statement && 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 "incident-public-statement" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/incident-public-statement into .github/skills/incident-public-statement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "incident-public-statement", 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 incident-public-statement -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 incident-public-statement --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/incident-public-statement .opencode/skills/incident-public-statement && 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 "incident-public-statement" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/incident-public-statement into .opencode/skills/incident-public-statement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "incident-public-statement", 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
incident-public-statement- GitHub stars
- 1.4k
- Token cost
- ~974 tokens
- SKILL.md length
- 476 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Write a single clear, honest public statement about an incident.
- Works in 6 steps: Acknowledge — name the issue plainly in… → What happened — a brief, factual account… → Impact — who/what is affected,… → …
- Asked to draft a public statement
- 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
What it does
Incident Public Statement is an agent skill from mohitagw15856/pm-claude-skills. Write a single clear, honest public statement about an incident. Use when asked to draft a public statement, a press statement, or an official response to a security breach, outage, data incident, recall, or public controversy. Produces a ready-to-publish statement — acknowledgement, what happened, impact, what you're doing, what affected people should do, and a commitment to update — plus a short and a long version.
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. 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 draft a public statement
- A press statement
- An official response to a security breach
- Public controversy
Example prompts
- “/incident-public-statement”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Acknowledge — name the issue plainly in the first sentence; don't bury it.
- What happened — a brief, factual account (confirmed only); say what's still being investigated.
- Impact — who/what is affected, specifically and honestly.
- What we're doing — the actions taken and underway, with accountability (no blame-shifting).
- What you should do — the clear next step for affected people, or "no action needed" if true.
- Our commitment — that you'll share an update by a stated time, and how to get help/contact.
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
Incident Public Statement loads about 974 tokens when it runs. Until then it costs about 112 tokens; SKILL.md has 476 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). 476 words, ~974 tokens.
Download SKILL.mdSave it as
.claude/skills/incident-public-statement/SKILL.md (or your agent's skills folder).- name
- incident-public-statement
- description
- Write a single clear, honest public statement about an incident. Use when asked to draft a public statement, a press statement, or an official response to a security breach, outage, data incident, recall, or public controversy. Produces a ready-to-publish statement — acknowledgement, what happened, impact, what you're doing, what affected people should do, and a commitment to update — plus a short and a long version.
Incident Public Statement Skill
A public statement is judged in seconds: does it acknowledge the problem, take responsibility, and tell people
what to do? This skill writes that statement — honest, human, and specific — avoiding both the legalese that
reads as evasion and the over-promising that creates the next problem. (Need the whole coordinated response,
not just the statement? Use pr-crisis-response.)
Working from a brief
Given a one-line incident description, produce the full statement anyway — infer the likely impact and next steps, label assumptions, and clearly bracket only the genuinely incident-specific facts the user must confirm before publishing (numbers, dates, scope). Never refuse for missing detail; flag legally sensitive claims for review.
Required Inputs
Ask for these only if they aren't already provided (else infer and label):
- What happened — the incident, when it started/was discovered, and current status.
- Who's affected and how — scope and the concrete impact on them.
- What you're doing — the response so far and what's next.
- What affected people should do — the specific action (reset password, watch for X, no action needed).
- Voice & constraints — tone, and anything legal/regulatory you can't yet say.
Output Format
Public Statement: [incident]
Statement (publish-ready) — in this order:
- Acknowledge — name the issue plainly in the first sentence; don't bury it.
- What happened — a brief, factual account (confirmed only); say what's still being investigated.
- Impact — who/what is affected, specifically and honestly.
- What we're doing — the actions taken and underway, with accountability (no blame-shifting).
- What you should do — the clear next step for affected people, or "no action needed" if true.
- Our commitment — that you'll share an update by a stated time, and how to get help/contact.
Then provide:
- Short version — 2–3 sentences for social / status page / SMS.
- Notes — bracketed facts to confirm before publishing, and any line flagged for legal review.
Show full SKILL.md (174 more words)Show less
Quality Checks
- The first sentence acknowledges the issue directly — no warm-up, no burying
- Only confirmed facts are stated; open items are named as "under investigation"
- It takes responsibility without speculating on cause or shifting blame
- Affected people get a clear, specific action (or an honest "no action needed")
- It commits to a next update by a stated time
- Both a full and a short version are provided; sensitive claims flagged for review
Anti-Patterns
- Do not open with self-congratulation or context-setting — lead with the acknowledgement
- Do not use evasive legalese ("issues may have impacted some users") when you can be specific
- Do not speculate on cause or promise outcomes you can't guarantee
- Do not state numbers/scope you haven't confirmed — bracket them for confirmation
- Do not omit what the reader should actually do next
Based On
Incident communication practice — prompt acknowledgement, factual transparency, accountability, and clear guidance for affected people.
Example Trigger Phrases
- "Draft a public statement."
- "Write a press statement about the breach."
- "Write our official response to the outage."
- "Respond publicly to this controversy."
© 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/incident-public-statement of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Incident Public Statement 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 |
|---|---|---|---|---|---|---|
| Incident Public Statement this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~974 | Automated safety check: Pass | MIT | |
| Kubernetes Network Root Cause Analysiskubeshark/kubeshark | 12k | — | ~5.3k | Automated safety check: Pass | Apache-2.0 | |
| Nix Config Debugryan4yin/nix-config | 2.1k | — | ~1.2k | Automated safety check: Pass | MIT | |
| 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 | |
| Oncallpigweed-project/pigweed | 548 | — | ~963 | Automated safety check: Pass | Apache-2.0 |
Similar skills
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…
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.
Oncall
pigweed-project/pigweed
Pigweed oncall rotation runbooks and maintenance workflows (such as rolling CIPD client tools for b/315378787).
Loop Triage Report
cobusgreyling/loop-engineering
Turns CI failures, open issues, recent commits and chat threads into a prioritized markdown report that an automation loop can act on without inventing architecture work.
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 Incident Public Statement
What does Incident Public Statement do?
Write a single clear, honest public statement about an incident. Incident Public Statement is an agent skill from mohitagw15856/pm-claude-skills. Write a single clear, honest public statement about an incident.
When should I use Incident Public Statement?
Incident Public Statement fits situations like: asked to draft a public statement; A press statement; an official response to a security breach; public controversy.
How do I install Incident Public Statement in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill incident-public-statement -a claude-code`. Or copy the skill folder (skills/incident-public-statement in mohitagw15856/pm-claude-skills) into .claude/skills/incident-public-statement in your project. Claude Code loads it when a task matches its description.
How do I install Incident Public Statement in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill incident-public-statement -a codex`. Or copy the skill folder (skills/incident-public-statement in mohitagw15856/pm-claude-skills) into .agents/skills/incident-public-statement in your project. Codex loads it when a task matches its description.
Can I use Incident Public Statement 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 incident-public-statement -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/incident-public-statement, .gemini/skills/incident-public-statement, .github/skills/incident-public-statement and .opencode/skills/incident-public-statement in your project.
What does Incident Public Statement need to run?
SKILL.md names no scripts, command-line tools or credentials: Incident Public Statement is instructions for the agent only.
Does Incident Public Statement 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 Incident Public Statement 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 Incident Public Statement use?
Incident Public Statement 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 Incident Public Statement use?
About 974 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 Incident Public Statement?
Skills that share tags, products or a category with Incident Public Statement: Kubernetes Network Root Cause Analysis (kubeshark/kubeshark, 12k stars), Nix Config Debug (ryan4yin/nix-config, 2.1k stars), UModel Root Cause Analysis (alibaba/UnifiedModel, 415 stars) and Learnings (kortix-ai/suna, 20k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Incident Public Statement?
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.