luna-vitals-extract

Stars11

Forks0

UpdatedJuly 6, 2026 at 14:29

Use when backfilling salus health series for one vault time-bucket (HIMMEL-355). Extracts (date, metric, value) tuples for the tracked vitals from the bucket's notes — deterministic structured entries via the luna-vitals CLI, plus an LLM pass over prose/timeline — and writes ONE per-bucket review artifact for operator review. One bucket per armed slot (single-writer). Never writes 50-Vitals/ directly.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

yotamleo

yotamleo/Himmel

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name

luna-vitals-extract

description

Extract health-series rows for ONE time-bucket into a review artifact. Inputs: a date range <START>..<END> and the artifact output path <ARTIFACT>. Tracked metrics: migraine, skin_flare, sleep_hours, hrv_ms, rhr_bpm.

Locate health-relevant notes in the bucket: use qmd over collection salus (and 20-Timeline/, daily notes) filtered to the date range. Collect the file paths.
Deterministic pass: for each structured file, run bun run <repo>/scripts/luna-vitals/cli.ts parse <file> --note-date <date-if-daily> --out <tmp/det-N.json>.
LLM pass: read the prose/timeline files. Extract ONLY explicit dated values (e.g. "14 Jun 2024 — migraine, bad day" → migraine on 2024-06-14; map qualitative→the metric's scale using the registry 50-Vitals/_series.md). Do NOT infer from relative statements ("worse lately"). Record each as a row {metric,date,value,source} where source = ": ". Write these as one artifact {bucket:"<START>..<END>", rows:[...], conflicts:[]} to <tmp/llm.json> (same schema as the CLI).
Merge this bucket's artifacts, routing the deterministic-parse artifacts and the LLM artifact into their respective pools so deterministic values win on overlap: bun run <repo>/scripts/luna-vitals/cli.ts merge --det <tmp/det-*.json> --llm <tmp/llm.json> --out <ARTIFACT>.
Report the row count per metric and any conflicts. STOP — do not write 50-Vitals/. The operator reviews <ARTIFACT>, then the single-writer merge + write step lands it.

More from this repository

same repository

pr-check

yotamleo/Himmel

Panel-only CR gate for Codex — runs the shell critic panel and CodeRabbit CLI pass over the branch diff, records ledger evidence, and clears the CR marker through the sanctioned chokepoint only when both the panel and CodeRabbit findings are clean (no Critical/Important blockers). Use when the user asks to run /pr-check or clear the CR gate under Codex.

2026-07-3111

handover

yotamleo/Himmel

Use when the user says "new epic", "new task", "new standalone", "end session", "update status", "handover", "handover-resume

2026-07-3111

handover-arm-resume

yotamleo/Himmel

Arm the OS scheduler to relaunch claude at a given time with a given handover. Dedup-guarded. Use when the user asks to arm a resume / schedule a relaunch or run /handover-arm-resume.

2026-07-3011

pipeline-cadence

yotamleo/Himmel

Arm/inspect/remove the recurring luna clip-pipeline cadence (daily harvest+triage, daily synthesize+archive, daily health) via schtasks/cron, each leg pinned to a cheap --model. Dedup-guarded. Use when the user asks to arm/check/disarm the clip-pipeline cadence or runs /pipeline-cadence.

2026-07-3011

memory-compound

yotamleo/Himmel

Use when the per-project auto-memory store (`~/.claude/projects/<project-slug>/memory/`: the always-loaded `MEMORY.md` index + one topic file per fact) is approaching or over its load budget (~24.4KB) — the harness emits a size-limit warning at session load when over budget (e.g. "MEMORY.md is NN KB (limit 24.4KB)"), content past the limit is silently dropped = partial recall. Losslessly compounds the DURABLE gotchas out of the auto-memory into qmd-searchable luna / himmel reference notes (read-many → propagation review → write-once → qmd gate → slim index → delete sources), so the always-loaded index stays lean and adopter-generic learnings land in himmel docs (memory + vault never propagate to other users). Lean-invoke, operator-run on demand — NOT an always-on hook (HIMMEL-569).

2026-07-2011

minerva

yotamleo/Himmel

Use when turning an idea into an implementation plan — runs brainstorm → spec → plan as ONE pipeline with an ADVERSARIAL CRITIC LOOP between each stage. Trigger on "build/implement/design X", "/minerva", or any feature/capability work that should pass through a spec + plan before code. Composes superpowers brainstorming + writing-plans (no fork); adds a spec-critic and a plan-critic.

2026-07-2011

name

luna-vitals-extract

description

Locate health-relevant notes in the bucket: use qmd over collection salus (and 20-Timeline/, daily notes) filtered to the date range. Collect the file paths.
Deterministic pass: for each structured file, run bun run <repo>/scripts/luna-vitals/cli.ts parse <file> --note-date <date-if-daily> --out <tmp/det-N.json>.
LLM pass: read the prose/timeline files. Extract ONLY explicit dated values (e.g. "14 Jun 2024 — migraine, bad day" → migraine on 2024-06-14; map qualitative→the metric's scale using the registry 50-Vitals/_series.md). Do NOT infer from relative statements ("worse lately"). Record each as a row {metric,date,value,source} where source = ": ". Write these as one artifact {bucket:"<START>..<END>", rows:[...], conflicts:[]} to <tmp/llm.json> (same schema as the CLI).
Merge this bucket's artifacts, routing the deterministic-parse artifacts and the LLM artifact into their respective pools so deterministic values win on overlap: bun run <repo>/scripts/luna-vitals/cli.ts merge --det <tmp/det-*.json> --llm <tmp/llm.json> --out <ARTIFACT>.
Report the row count per metric and any conflicts. STOP — do not write 50-Vitals/. The operator reviews <ARTIFACT>, then the single-writer merge + write step lands it.