Skip to main content

create-an-emergency-information-file

Prepare a concise, secure emergency reference that authorized people can retrieve and act on. Use when household continuity depends on information held by one person.

Source facts

Repository
protosphinx/sphinxstack
Last source activity
July 29, 2026 at 13:55
Detected SKILL.md language
English
Stars
3
Forks
0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer
2 files

Showing SKILL.md

SKILL.md
Source instructions · Read-only preview
name
create-an-emergency-information-file
category
start
description
Prepare a concise, secure emergency reference that authorized people can retrieve and act on. Use when household continuity depends on information held by one person.
# create-an-emergency-information-file Make essential information usable without turning the file into a master key for the household. Prefer locators and access instructions over unnecessary secret duplication. ## When to use - Use for household emergencies, hospitalization, evacuation, caregiving handoff, travel disruption, or death. - Seek professional guidance for medical directives, estate documents, guardianship, and jurisdiction-specific authority. ## Procedure 1. Define realistic scenarios, authorized readers, activation conditions, and what each reader may do. 2. Record household members, dependents, pets, emergency contacts, care needs, accessibility needs, and preferred communication. 3. Add current clinician, medication, allergy, insurance, property, utility, school, work, and service contact locators as appropriate. 4. Index identity, medical, legal, financial, property, and continuity documents by secure location. 5. Document home access, shutoff, evacuation, meeting point, device, backup, and essential-service instructions without exposing them broadly. 6. Reference password-manager or sealed-access procedures rather than listing reusable passwords. 7. Mark who has legal or practical authority for care, property, money, accounts, or decisions; do not infer authority from relationship. 8. Encrypt or physically secure copies, keep an appropriate offsite copy, and log who receives access. 9. Walk an authorized person through a scenario and fix ambiguous, stale, or inaccessible instructions. 10. Review on a schedule and after household, medication, contact, policy, device, or authority changes. ## Failure plan - Do not place full credentials, card numbers, identity numbers, or protected health detail in an easily copied file. - Do not present informal wishes as legal authority. - If access requires the unavailable person’s device or memory, redesign it. - Revoke and replace copies when an authorized holder or household relationship changes. ## Done - An authorized person can find essential contacts, records, care instructions, and access paths under stress - Sensitive details are minimized and protected with tested fallback access - Authority, version, recipients, review date, and revocation process are explicit
View on GitHub