Skip to content
cccskills
FreePublished on GitHubEnglish overview

Unify

Compare systems, rules, documents, plans, or goals to identify shared aims, useful tensions, duplication, and genuine conflicts. The skill grounds findings in the inputs and returns ranked recommendations for improving coherence; it analyzes read-only and does not edit them.

OriginalShow the original description

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).

danielmiessler/LifeOS19,635 stars(GitHub 19,635 + cccskills 0)

Run score Not tested

See how to install

Good for

  • Check whether several strategy documents align
  • Find conflicts among rules and workflows
  • Review coherence across system components
  • Get ranked recommendations without changing files

Overview

What it does

Unify reads a set of systems, rules, skills, goals, documents, or plans and identifies their aims and guiding principles. It maps where the inputs support one another, have useful tensions, duplicate each other, or genuinely conflict. It checks the source material behind each input instead of treating different wording as proof of disagreement. The result is a ranked set of recommendations for improving coherence, grounded in the inputs.

When it helps

Use Unify to check whether several policies or plans point in the same direction, or to find conflicts and duplication among operating rules. If you do not name a set of inputs, the skill analyzes the LifeOS components specified in its configuration.

Example requests

  • “Check these three strategy documents for conflicts.”
  • “Are the approval, scheduling, and monitoring rules in harmony?”
  • “Check overall coherence.”

Notes

The analysis is read-only and does not edit the inputs. An analysis of LifeOS as a whole requires a configuration file when you do not specify the inputs.

This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.

Document check

AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).

SafetyAre sending data, deleting files, and running commands disclosed?
AGoodThe skill is read-only; changes remain recommendations until the user agrees.
Easy setupDoes it need few tools or API keys, and are they documented?
BPartly lackingNamed inputs need no config, but default LifeOS analysis requires Config.md.

Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 28, 2026. Treat it as a guide and read the original before installing.

Disagree? Request a re-evaluation

Tell us which point is wrong and why. No login needed. We will check it against the SKILL.md, redo the evaluation, and show the result here.

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

Files included (5)

  • SKILL.md5.3 KB
  • Intents/Harmonize.md8.0 KB
  • Setup.md2.7 KB
  • Tools/CheckReport.help.md1.3 KB
  • Tools/CheckReport.ts7.5 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

IntentTriggerFile
Harmonize"unify", "harmony check", "are these in harmony", "do these conflict", "unify LifeOS", any set of inputs to reconcileIntents/Harmonize.md
FileRead when
Setup.mdConfig.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.

Gotchas

  • Analysis means read-only. Unify recommends; it never edits an input, even an obviously broken one. Doctrine and identity changes, and anything a self-initiated analysis proposes, stay recommendations until the principal says yes (self-initiated or scheduled analysis loops recommend, and never change the system on their own).
  • Routing-table entries are not sources. CLAUDE.md describes every subsystem in one line, and that line is often stale or marketing-shaped. Characterizing a component from it produces confident wrong findings; read its system doc or ISA.
  • Vocabulary collisions look like conflicts (2026-10-08, first full LifeOS run). Two components using one word for different things (or two words for one thing) is drift, not opposed aims; that run's "spec" and "claim" findings were renames. Name it as drift; the fix is a rename, not a redesign.
  • Long agent hand-backs get cut off. Brief each reader to write its full report to one scratchpad file and hand back only the path. If a reader is blocked mid-report, don't route the content around the block; name it in the report as a coverage gap.

Examples

Example 1: Default scope

User: "Run Unify"
→ Harmonize on the default LifeOS set from Config.md
→ Per-component aims, harmony map, conflicts vs tensions, unifying principle
→ Ranked recommendations, each filed as an Upgrades proposal on the principal's yes

Example 2: Named inputs

User: "Are the approval rules, the scheduling rule, and the monitoring layer in harmony?"
→ Harmonize on exactly those three
→ Where self-initiated loops, scheduled workflows and Vigil routing agree or collide
→ Recommendations scoped to those three

Example 3: Outside LifeOS

User: "Unify these three strategy docs" (paths given)
→ Harmonize on the documents
→ Same report shape, judged against the summit the docs share

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

AnnualReports

FreeSummary

Find and fetch vendor cybersecurity reports, then compare their findings on topics such as ransomware, breaches, cloud security, and AI. Analyses identify the reports consulted and cite each figure by vendor, year, and report, including where sources disagree.

  • Find reports in a cybersecurity topic area
  • Fetch a specific vendor report
  • Compare ransomware findings across reports
danielmiessler/LifeOS19.6KUpdated Oct 28, 2026

Compare a component's own design needs with the goals of the larger system through three structured passes. The result identifies conflicts, recommends an appropriate scope, and assesses whether the proposed design fits the whole.

  • Choosing between a service, a library, and inline code
  • Comparing feature requests with product goals
  • Checking how new components fit an existing system
danielmiessler/LifeOS19.6KUpdated Oct 28, 2026

Aphorisms

FreeSummary

Find quotes that fit a text’s themes, with attribution and a short reason for each suggestion. Add sourced quotes, research thinkers, and organize a quote collection by theme and usage history to avoid repetition.

  • Finding a fitting quote for a newsletter
  • Saving sourced quotes without duplicates
  • Researching a thinker’s quotes by theme
danielmiessler/LifeOS19.6KUpdated Oct 28, 2026

Art

FreeSummary

Create blog illustrations, technical diagrams, comparisons, comics, and icons through workflows tailored to each format. The skill guides composition, color, and model selection, then stages generated images for review before they are used in a project.

  • Creating blog header illustrations
  • Explaining a system with a technical diagram
  • Visualizing comparisons and timelines
danielmiessler/LifeOS19.6KUpdated Oct 28, 2026

ArtDirection

FreeSummary

Assess the visual quality of images, films, slides, and site captures against a brief and craft criteria. Two vision judges score the work and rank defects, guiding bounded revision; delivery is gated on a passing critique, with human calibration labels recorded separately.

  • Reviewing a render and listing the most important visual defects
  • Iterating on a film or slide deck until it meets a defined bar
  • Checking whether an image reads as professional
danielmiessler/LifeOS19.6KUpdated Oct 28, 2026

ArXiv

FreeSummary

Find arXiv papers by topic, research category, or paper ID. Retrieve titles, authors, abstracts, and links, check new submissions, and add AlphaXiv's AI-generated overviews when available to help decide which papers to read.

  • Checking new AI and machine learning papers
  • Finding papers on a specific research topic
  • Looking up a paper by its ID or arXiv URL
danielmiessler/LifeOS19.6KUpdated Oct 28, 2026

See all skills by danielmiessler

Report a problem with this skill