LifeOS
Install and onboard a user into LifeOS, the Life Operating System (current state →...
Install
npx skills add danielmiessler/LifeOS --skill LifeOS -g -a claude-code -y- Repository
- danielmiessler/LifeOS19.7k
- Category
- Git and review
- Updated
- 8d ago
- License
- MIT
- Context cost
- Mediumabout 1,925 tokens
- Runs scripts
- Yes, review before use
What it does
Install and onboard a user into LifeOS, the Life Operating System (current state → ideal state via TELOS + the Algorithm). The agentic installer detects your OS + harness, wires hooks with permission, scaffolds your USER tree, pulls in sources you provide, and runs the TELOS / current→ideal interview that seeds your Pulse dashboard. USE WHEN install LifeOS, set up LifeOS, lifeos setup, lifeos-setup, lifeos interview, onboard me, run the interview, integrate LifeOS into my harness, update LifeOS, uninstall LifeOS, first-time setup, lifeos doctor, check my install, what capabilities are broken, pulse setup, set up pulse, install pulse, audit pulse setup, is Pulse healthy, report a LifeOS bug, file an issue upstream, report this to the project, contribute this fix, open a PR to LifeOS, suggest a feature, ask the LifeOS project. NOT FOR building or cutting a LifeOS release (private release tooling), editing TELOS after onboarding (use Telos / Interview), or LifeOS system maintenance (use the private maintenance skill).
LifeOS
The install and onboarding surface for LifeOS, the Life Operating System. One command takes a stranger on any harness from nothing to a working, personalized install whose Pulse dashboard already shows their current state vs ideal state, without making them adopt a whole new harness.
Ideal State
- A stranger on any supported OS and harness ends with a working, personalized install: Core placed after one consent, every enhancement they did not decline, identity placeholders gone, the
lifeoslaunch command wired, and Pulse showing their own current and ideal state. - Every change to the user's machine was shown before it happened and is reversible: settings and shell rc are backed up first, updates and uninstalls move or back up instead of deleting, and nothing the user authored is overwritten.
- Setup completes and its hooks and integration are in place before the Interview writes anything.
- Nothing changes without an explicit yes, during the install and afterwards, unless the user turned on the opt-in
automodecomponent (Intents/Setup.mdstep 7), which ships off and needs a clear yes. - Every "installed", "updated" or "removed" claim rests on the evidence the intent names, and a capability the user declined is reported as declined, never as broken.
- Feedback sent upstream is redacted, reproducible and posted only on the user's own yes.
