Skip to content

LeoYeAI/agent-master-skills / skills/afterself

afterself

Verified

Digital legacy agent — dead man's switch, final message executor, and ghost mode responder that preserves your digital presence. Use when the user wants to set up a dead man's switch, manage their digital will, or enable ghost mode.

FileKindSize
ETHICS.mdmarkdown5.9 KB
HEARTBEAT.mdmarkdown2.4 KB
SKILL.mdskill md16.0 KB
_meta.jsonconfig273 B
references/action-schema.mdmarkdown5.3 KB
references/escalation-protocol.mdmarkdown1.7 KB
references/ghost-persona-prompt.mdmarkdown3.6 KB
scripts/mortality.jsscript9.4 KB
scripts/persona.jsscript13.6 KB
scripts/state.jsscript18.5 KB
scripts/types.jsscript167 B
scripts/vault.jsscript11.2 KB

references/escalation-protocol.md

View on GitHub
# Escalation Protocol Reference

## Escalation Message Template

Send this to each trusted contact when beginning escalation:

> Hi {contact.name}, this is an automated message from Afterself. The person who set this up has not checked in for an extended period. Have you been in contact with them recently?
>
> Reply YES if they are okay, or NO if you can't reach them either.
>
> This is important — your response helps determine whether to activate their digital will.

## Response Classification

### Alive Keywords
The contact is confirming the person is OK:
- alive, fine, ok, safe, here
- with them, saw them, talked, spoke
- yes, they're good, false alarm

### Absent Keywords
The contact is confirming the person is unreachable:
- no, haven't, can't reach, missing, worried
- gone, not responding, absent, disappeared, confirm

### Ambiguous Response
If the message doesn't match either keyword list, ask for clarification:

> Thanks for responding. To be clear: have you been in contact with the person recently? Reply YES if they're okay, or NO if you can't reach them either.

## Decision Matrix

| Condition | Decision |
|---|---|
| ANY contact confirmed alive | **Stand down** — return to armed state |
| Majority confirmed absent | **Trigger** — begin executor |
| Some absent, none alive, below majority | **Wait** for more responses |
| Escalation timeout, at least one absent | **Trigger** |
| Escalation timeout, no responses at all | **Trigger** (with caution log) |

**Majority** = `ceil(totalContacts / 2)`

A single "alive" confirmation always overrides any number of "absent" confirmations. This is the safety-first approach — false negatives (not triggering when the person is gone) are far less harmful than false positives (triggering when they're alive).
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall