Agent skill

After The Disaster

by mohitagw15856 in mohitagw15856/pm-claude-skills

Work through the first hours and days after a disaster — a fire, flood, storm, or evacuation — in the right order: safety and people first, then documenting for insurance and aid, then the immediate…

MITAuto-check passed

Install After The Disaster

skills CLI
$ npx skills add mohitagw15856/pm-claude-skills --skill after-the-disaster -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mohitagw15856/pm-claude-skills after-the-disaster --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/after-the-disaster .claude/skills/after-the-disaster && rm -rf skills-src

Use ~/.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/

Facts

Skill name
after-the-disaster
GitHub stars
1.4k
Token cost
~1.8k tokens
SKILL.md length
766 words
Files
1
Skills in repo
1,348
Repo updated
First seen
Licence
MIT

At a glance

Work through the first hours and days after a disaster — a fire, flood, storm, or evacuation — in the right order: safety and people first, then documenting for insurance and aid, then the immediate…

  • Works in 5 steps: People and safety first — always. Before… → Document before you touch anything. The… → Notify insurance and register for aid —… → …
  • Someone says my house flooded/burned
  • SKILL.md covers What This Skill Produces, Required Inputs, Framework and Output Format, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

After The Disaster is an agent skill from mohitagw15856/pm-claude-skills. Work through the first hours and days after a disaster — a fire, flood, storm, or evacuation — in the right order: safety and people first, then documenting for insurance and aid, then the immediate recovery steps, without missing the things that cost money or health later. Use when someone says 'my house flooded/burned', 'what do I do after the disaster', 'we just evacuated, now what', or 'the storm damaged everything'. Produces a triaged action plan (safety → document → claim → recover), the do-not-miss list…

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

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

  • Someone says my house flooded/burned
  • What do I do after the disaster
  • We just evacuated
  • The storm damaged everything

Example prompts

  • “my house flooded/burned”
  • “what do I do after the disaster”
  • “we just evacuated, now what”
  • “/after-the-disaster”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. People and safety first — always. Before anything: is everyone accounted for and
  2. Document before you touch anything. The costly, universal mistake: cleaning up or
  3. Notify insurance and register for aid — mind the windows. Contact the insurer as
  4. Immediate recovery, in safe order. Prevent further damage where safe (tarp a roof,
  5. Watch the delayed hazards and the human toll. Mold after flooding, ongoing

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

After The Disaster loads about 1.8k tokens when it runs. Until then it costs about 156 tokens; SKILL.md has 766 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~156
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k

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). 766 words, ~1,801 tokens.

Download SKILL.mdSave it as .claude/skills/after-the-disaster/SKILL.md (or your agent's skills folder).
name
after-the-disaster
description
Work through the first hours and days after a disaster — a fire, flood, storm, or evacuation — in the right order: safety and people first, then documenting for insurance and aid, then the immediate recovery steps, without missing the things that cost money or health later. Use when someone says 'my house flooded/burned', 'what do I do after the disaster', 'we just evacuated, now what', or 'the storm damaged everything'. Produces a triaged action plan (safety → document → claim → recover), the do-not-miss list, and where to get help. Not legal advice; routes to emergency services and official aid.

After The Disaster Skill

In the hours after a disaster, shock and urgency make people do things in the wrong order — re-entering an unsafe building, throwing out damaged items before documenting them (and losing the insurance claim), or missing the aid window. There is a right order: people and safety first, then documentation, then claims and recovery — and knowing it turns a chaotic, costly aftermath into a sequence you can follow. This skill triages the first hours and days, front-loads the safety non-negotiables, and flags the do-not-miss steps (the photos before cleanup, the claim deadline, the aid you're entitled to) that quietly cost people the most later. It routes emergencies to services and claims/aid to the official bodies.

What This Skill Produces

  • A triaged action plan in strict order: (1) safety & people, (2) document everything, (3) notify insurance & register for aid, (4) immediate recovery — because doing these out of order costs money and safety
  • The do-not-miss list: the steps people skip in the chaos and regret — photograph damage before cleaning up, don't discard items until documented, hit the claim/aid deadlines, keep every receipt
  • Where to get help: emergency services for danger, the insurer to start the claim, and official disaster-aid/relief programs to register for (which have windows)
  • A health & safety brief: the hidden post-disaster hazards — contaminated flood water, structural instability, mold, carbon monoxide, downed lines — so recovery doesn't create the next injury

Required Inputs

Ask for (if not already provided):

  • What happened and the current situation — are people safe now, is the building safe, is anyone hurt or missing
  • The type and rough extent of damage (flood, fire, wind, evacuation with home intact)
  • Whether they have insurance and their [[emergency-doc-kit]] (policy numbers, contacts)
  • Where they are (country/area) so official aid/relief routes can be pointed to

Framework

  1. People and safety first — always. Before anything: is everyone accounted for and uninjured? Injuries → medical help. Is the structure safe to be in (fire damage, flood, gas, downed power lines)? Do not re-enter an unsafe building for belongings — this is where post-disaster deaths and injuries happen. Contaminated flood water, CO, and structural collapse are the immediate killers; the skill leads here, firmly.
  2. Document before you touch anything. The costly, universal mistake: cleaning up or discarding damaged property before photographing it, which cripples the insurance claim. Photograph and video everything — the damage, every damaged item, the waterline — before any cleanup, and keep damaged items until the insurer says otherwise. The [[emergency-doc-kit]]'s home inventory pairs with this.
  3. Notify insurance and register for aid — mind the windows. Contact the insurer as soon as safe to start the claim (policy number from the doc kit), and register for official disaster relief/aid programs, which frequently have application deadlines and are missed in the fog. Keep every receipt from the moment of the disaster (emergency accommodation, supplies) — many are reimbursable.
  4. Immediate recovery, in safe order. Prevent further damage where safe (tarp a roof, stop water) since insurers expect reasonable mitigation, but not at the cost of safety. Secure the property, sort temporary accommodation, and preserve the doc-kit records. Guard against post-disaster scams — fake contractors and charities target disaster victims ([[scam-message-decoder]]).
  5. Watch the delayed hazards and the human toll. Mold after flooding, ongoing structural risk, contaminated water, and the CO risk from generators/pumps during recovery. And the emotional reality: disaster recovery is a marathon of stress and grief; name that support (disaster mental-health lines, community relief) is part of the plan, not weakness.
Show full SKILL.md (189 more words)Show less

Output Format

## FIRST: are people and the building safe?
[Everyone accounted for/uninjured? · is it safe to be in the building? · do NOT re-enter an
unsafe structure · the immediate hazards: flood water, gas, power lines, CO]

## Document before you touch anything
[Photograph/video ALL damage and every damaged item BEFORE cleanup · keep damaged items ·
the waterline/extent]

## Notify & register (mind the deadlines)
[Insurer — start the claim (policy # from your doc kit) · official disaster aid/relief —
register, note the window · keep every receipt from now]

## Immediate recovery (safe order)
[Prevent further damage where safe · secure property · temp accommodation · beware
disaster scammers]

## Delayed hazards & support
[Mold, structural, contaminated water, CO during recovery · disaster mental-health/
community support — part of the plan]

⚠ Emergencies → emergency services. This is not legal/insurance advice — route claims to
your insurer and aid to official relief programs, and follow the authorities.

Quality Checks

  • Safety and people are handled first, with a firm "do not re-enter an unsafe building"
  • "Document before cleanup" is prominent — the costliest common mistake
  • Insurance notification and official-aid registration are included with their deadline windows and the keep-receipts rule
  • The delayed hazards (mold, structural, contaminated water, CO) are covered
  • Emotional/mental-health support is named, and scams are flagged

Anti-Patterns

  • Do not put property before people — re-entering an unsafe structure for belongings is how the aftermath kills
  • Do not let cleanup happen before documentation — it destroys the insurance claim
  • Do not miss the aid/claim deadlines — they're real and easily lost in the shock
  • Do not ignore the delayed hazards or the mental-health toll — recovery is where the second wave of harm lands
  • Do not give legal/insurance determinations — route to the insurer, official aid, and professionals; watch for the scams that target victims

[[emergency-doc-kit]] supplies the records to start claims; [[insurance-claim]] and [[claim-denial-decoder]] for the claim itself; [[scam-message-decoder]] for disaster scams; [[grief-admin]] and [[stoic-setback-debrief]] for the human aftermath; [[family-emergency-plan]] for reconnecting.

Example Trigger Phrases

  • "My house flooded/burned."
  • "What do I do after the disaster?"
  • "We just evacuated."

© 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/after-the-disaster of mohitagw15856/pm-claude-skills.

Open the folder on GitHubat commit 1cbf1f0

Compare with similar skills

After The Disaster 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.

After The Disaster compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
After The Disaster this skillmohitagw15856/pm-claude-skills1.4k—~1.8kAutomated safety check: PassMIT
Day Hour Performance Breakdownirinabuht12-oss/marketing-skills4.1k—~676Automated safety check: PassNone
Disaster Recoverysickn33/agentic-awesome-skills47k2 repos~3kAutomated safety check: PassMIT
Day Booksickn33/agentic-awesome-skills47k1 repos~7kAutomated safety check: PassMIT
YC Office Hoursgarrytan/gstack136k—~4.2kAutomated safety check: PassMIT
Office Hoursalirezarezvani/claude-skills28k—~935Automated safety check: PassMIT

Similar skills

  • Day Hour Performance Breakdown

    irinabuht12-oss/marketing-skills

    Analyzes performance by day of week and hour of day across your campaigns.

    4.1k GitHub stars~676 tokensUpdated 17 days ago
    Marketing & SEOAuto-check passed
  • Disaster Recovery

    sickn33/agentic-awesome-skills

    Implement disaster recovery strategies and runbooks. An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 2 repos~3k tokens
    DevOps & CloudAuto-check passed
  • Day Book

    sickn33/agentic-awesome-skills

    Daily cash, bank and digital day book: opening and closing balances per book, in/out movements, debit/credit presentation and reconciliation status.

    47k GitHub starsUsed in 1 repo~7k tokens
    Business, Finance & HRAuto-check passed
  • YC Office Hours

    garrytan/gstack

    Runs a YC-style office hours session that pressure-tests a product idea before any code and ends in a design document instead of an implementation.

    136k GitHub stars~4.2k tokensUpdated today
    Product & Project ManagementAuto-check passed
  • Office Hours

    alirezarezvani/claude-skills

    /cs:office-hours <topic — YC-style 6-question founder interrogation before any advice.

    28k GitHub stars~935 tokensUpdated 1 mo ago
    Auto-check passed
  • Judgment Day

    Gentleman-Programming/gentle-ai

    Trigger: judgment day, dual review, adversarial review, juzgar.

    7.7k GitHub stars~927 tokensUpdated today
    Auto-check passed

More from mohitagw15856/pm-claude-skills

All 1,348 skills in this repo
  • Car 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…

    1.4k GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed
  • Cs Health Scorecard

    mohitagw15856/pm-claude-skills

    Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.

    1.4k GitHub stars~2.4k tokensUpdated 2 days ago
    Auto-check passed
  • 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.

    1.4k GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed
  • Feature Prioritisation

    mohitagw15856/pm-claude-skills

    Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.

    1.4k GitHub stars~2k tokensUpdated 2 days ago
    Auto-check passed
  • 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.

    1.4k GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed
  • 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.

    1.4k GitHub stars~1.2k tokensUpdated 2 days ago
    Auto-check passed

Questions about After The Disaster

What does After The Disaster do?

Work through the first hours and days after a disaster — a fire, flood, storm, or evacuation — in the right order: safety and people first, then documenting for insurance and aid, then the immediate…. After The Disaster is an agent skill from mohitagw15856/pm-claude-skills. Work through the first hours and days after a disaster — a fire, flood, storm, or evacuation — in the right order: safety and people first, then documenting for insurance and aid, then the immediate recovery steps, without missing the things that cost money or health later.

When should I use After The Disaster?

After The Disaster fits situations like: someone says my house flooded/burned; what do I do after the disaster; we just evacuated; the storm damaged everything.

How do I install After The Disaster in Claude Code?

Run `npx skills add mohitagw15856/pm-claude-skills --skill after-the-disaster -a claude-code`. Or copy the skill folder (skills/after-the-disaster in mohitagw15856/pm-claude-skills) into .claude/skills/after-the-disaster in your project. Claude Code loads it when a task matches its description.

How do I install After The Disaster in Codex?

Run `npx skills add mohitagw15856/pm-claude-skills --skill after-the-disaster -a codex`. Or copy the skill folder (skills/after-the-disaster in mohitagw15856/pm-claude-skills) into .agents/skills/after-the-disaster in your project. Codex loads it when a task matches its description.

Can I use After The Disaster 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 after-the-disaster -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/after-the-disaster, .gemini/skills/after-the-disaster, .github/skills/after-the-disaster and .opencode/skills/after-the-disaster in your project.

What does After The Disaster need to run?

SKILL.md names no scripts, command-line tools or credentials: After The Disaster is instructions for the agent only.

Does After The Disaster 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 After The Disaster 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 After The Disaster use?

After The Disaster 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 After The Disaster use?

About 1.8k tokens (SKILL.md is roughly 7.2k 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 After The Disaster?

Skills that share tags, products or a category with After The Disaster: Day Hour Performance Breakdown (irinabuht12-oss/marketing-skills, 4.1k stars), Disaster Recovery (sickn33/agentic-awesome-skills, 47k stars), Day Book (sickn33/agentic-awesome-skills, 47k stars) and YC Office Hours (garrytan/gstack, 136k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains After The Disaster?

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.