# Superior

Thinking skill for big problems that swaps the solver: reads the scope it was given...

- Repository: https://github.com/danielmiessler/LifeOS (19669 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-10-28
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add danielmiessler/LifeOS --skill Superior -g -a claude-code -y`
Codex: `npx skills add danielmiessler/LifeOS --skill Superior -g -a codex -y`
Cursor: `npx skills add danielmiessler/LifeOS --skill Superior -g -a cursor -y`
Gemini CLI: `npx skills add danielmiessler/LifeOS --skill Superior -g -a gemini-cli -y`

## Description

Thinking skill for big problems that swaps the solver: reads the scope it was given, infers the scope the asker most likely means, maps that, then asks how a vastly smarter, fully informed intelligence with none of our habits or invented limits would do it, and turns every gap between its approach and ours into a change we can make. Built for large scope (how a whole system is implemented, an architecture, a strategy); when the intended scope is unclear or too small, a short interview settles it first. USE WHEN superior, how would a smarter intelligence do this, what would a genius or superintelligence do, if you knew everything, are we thinking too small, best possible approach, how should this whole system be built, analyze how this big thing is implemented. NOT FOR constraint teardown (FirstPrinciples), many options (BeCreative), attacking a plan (RedTeam).

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Superior

Every approach we take is shaped by the mind taking it: what it happens to know, what it has seen done before, what it assumes is expensive or impossible, how much effort it expects to spend. Superior holds the task fixed and replaces that mind. It asks how an intelligence far beyond ours would do this exact task, one that knows everything relevant including the current frontier, carries no habits or inherited conventions, invents no constraints, reasons cleanly from first principles, and cares only about the real goal behind the request. Then it measures the distance between that approach and the one we were about to take, and closes as much of it as reality allows.

Superior is built for big problems: how a whole system is implemented, an architecture, a strategy, a multi-part build. On a one-function question the superior mind and ours give the same answer, so the pass earns nothing. The value appears at scale, where habits and invented limits compound across many decisions.

FirstPrinciples changes what we believe about the problem. Superior changes who is solving it. They pair well: Superior often surfaces a constraint we invented, and FirstPrinciples is the tool for proving it was invented.

## Ideal State

- The pass runs at the proper scope of § Scope Comes First and states it in one line with its reason; an ask too small to earn anything is widened by a scope interview or by stating the inferred scope, never run on the small scope as given. A scope the caller fixed runs as given, with no interview.
- The superior approach comes from the mind defined in § The Superior Mind, written before our current plan is reread (or by a blind agent when anchoring is likely), and is concrete enough to execute.
- Every difference between that approach and ours ends as an executable change or a named real limit, and no constraint the principal actually set is dropped.

## Intent Routing

The rest: https://github.com/danielmiessler/LifeOS/blob/HEAD/LifeOS/install/skills/Superior/SKILL.md
