Unify
Harmony analysis across any set of inputs (systems, rules, skills, goals, documents...
Install
npx skills add danielmiessler/LifeOS --skill Unify -g -a claude-code -y- Repository
- danielmiessler/LifeOS19.7k
- Category
- AI and agents
- Updated
- 8d ago
- License
- MIT
- Context cost
- Lightabout 902 tokens
- Runs scripts
- Yes, review before use
What it does
Harmony analysis across any set of inputs (systems, rules, skills, goals, documents, plans), defaulting to all of LifeOS and its subcomponents when none are named. Extracts each input's core principles and ultimate aim, maps where they reinforce, pull in productive tension, duplicate, or work against each other, runs FirstPrinciples, Superior and SystemsThinking (plus other thinking skills as fit) to find the real conflicts, and recommends ranked changes that bring the whole into unity. Read-only; recommends, never edits. USE WHEN unify, harmonize, harmony check, are these in harmony, are these working against each other, do these conflict, where do these contradict, coherence check, unify LifeOS, is LifeOS coherent, are my systems fighting each other, alignment across components, bring these into unity. NOT FOR attacking one plan (RedTeam), feedback loops of one system (SystemsThinking), trimming prompt rules (BitterLessonEngineering), climbing one target (HillClimb), editing personal goals (use Telos).
Unify
Every input worth analyzing exists to achieve something. Put several together and their aims either compound or collide. Unify finds out which, at the level of principles and aims rather than surface wording, and says how to bring the set into one coherent whole.
With no inputs named, the set is LifeOS itself: its constitution, its doctrine, and every subsystem, each judged against the summit they all claim to serve.
Ideal State
- Every judgment rests on each input's own sources, quoted on both sides, and is made against a summit stated with its source.
- Real conflicts, drift, duplication and stragglers are told apart from tensions doing useful work, and only the problems get fixes.
- The result is a short ranked list of changes, each placed where it lands with the check that proves it, and no input is edited until the principal says yes.
Intent Routing
| Intent | Trigger | File |
|---|---|---|
| Harmonize | "unify", "harmony check", "are these in harmony", "do these conflict", "unify LifeOS", any set of inputs to reconcile | Intents/Harmonize.md |
| File | Read when |
|---|---|
Setup.md | Config.md is missing for a no-input run, first-time setup, or the config label list |
Data & Config
Read LIFEOS/USER/CUSTOMIZATIONS/SKILLS/Unify/Config.md for the default LifeOS input set, the summit it is judged against, and any standing exclusions. CLAUDE_CONFIG_DIR overrides the installation root. When the user names no inputs and this file is missing, stop and say so, pointing at Setup.md; never guess a default set or summit. Named inputs need no config, but a summit still has to be stated from their own sources.
