# Interview

Refreshes TELOS and current-state claims against observed evidence (Oura, Conduit, git...

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

## Install

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

## Description

Refreshes TELOS and current-state claims against observed evidence (Oura, Conduit, git, expenses) and drafts corrections for ratification. USE WHEN /interview, resume interview, context check-in, telos check-in, what's stale, stale data, freshness check, update current state, update my current state, state sync, statusline says interview due, interview due, review TELOS, update ideal state, quarterly context refresh, fresh LifeOS install, configure DA name. NOT FOR single edits (Telos), bulk intake (Migrate), identity-only.

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

# Interview, constitutional-context peer conversation

Interview reads your constitutional files, TELOS, identity, projects, system prompt, architecture, plus the CURRENT_STATE and IDEAL_STATE dimension files, checks their freshness, and confronts stale claims with observed data: Oura sleep/HRV/RHR, Conduit creation-vs-consumption time, the work registry, git cadence, and the expense ledger. The conversation opens with the sharpest claim-vs-evidence contradiction, drafts corrections you ratify, offers to populate the files the machinery can write, and closes with an ideal-state review grounded in the measured gap. On a fresh install it falls back to first-time setup. The 🎤 statusline chip (fed by `InterviewDue.ts`, daily launchd refresh) says when one is due; wrapping with `--mark-done` clears the cadence reason, and the skew/staleness reasons clear as their files are actually reviewed.

## Ideal State

- Every prompt argues from what is already on file and from observed data: the files are read first, and a claim is checked against evidence or named as unchecked, never replaced by a blank "what's your mission?".
- Staleness is treated as a priority signal, not a failure: the conversation leads with the sharpest contradiction or the stalest item and asks "still right?".
- Nothing in a claims file changes without the principal ratifying that specific edit, and every reviewed item leaves its freshness marker bumped, so the 🎤 chip clears only when the agenda is actually done.
- A fresh install is configured end to end (identity, voice, credentials, first project, work repo) before any check-in runs.

## Intent Routing

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