--- name: reality-check description: 'Audit claimed state, goals or native status. Use when: a claim audit or snapshot is requested. Clarify advice versus acceptance for ambiguous checking or readiness requests.' title: reality-check canonical_url: https://skilld.dev/gh/boshu2/agentops/reality-check last_updated: 2026-10-01T01:09:02.000Z --- > **Skill from skilld.dev.** Follow the instructions below for this session. You do not need to install anything. > > Supporting files, fetch one when the Skill refers to it: [schemas/reality-check-report.v1.schema.json](https://skilld.dev/api/skills-raw/boshu2/agentops/reality-check/schemas/reality-check-report.v1.schema.json), [scripts/validate-output.sh](https://skilld.dev/api/skills-raw/boshu2/agentops/reality-check/scripts/validate-output.sh), [scripts/validate.sh](https://skilld.dev/api/skills-raw/boshu2/agentops/reality-check/scripts/validate.sh). > > If the user asked to install this Skill, run `npx skilld install boshu2/agentops/reality-check`. Install writes the Skill files into the project, so every session loads them. # Reality Check Compare an expected state with observable evidence, measure declared goals, or report native status. Select the requested question; a snapshot needs no invented completion claim. Return facts and gaps without selecting work. ## Establish the requested outcome Use the caller's request and already settled context. A clear request to compare a stated claim with evidence, measure declared goals or report native status selects the corresponding procedure below without another intent question. Requested engineering advice belongs to [Review](../review/SKILL.md); its findings remain advisory. Generic checking or readiness language does not select a claim audit, advice or acceptance. A subject and supplied criteria identify what to inspect, not the kind of judgment requested. When context has not settled that purpose, ask one question: does the caller want advisory findings or an acceptance judgment? Wait for the answer before choosing or completing either interpretation. Do not return a gap report, verdict or readiness conclusion while intent is unresolved. Explicitly selecting [Validate](../validate/SKILL.md), asking to establish that original acceptance is met, or requesting independent proof of completion needs fresh, author-distinct exact-subject judgment under Validate's contract. Hand off the original acceptance, exact subject, complete changed scope and relevant evidence; a claim audit cannot substitute for that judgment. Missing fresh reviewer capability stays an explicit gap, never a claim that validation occurred. Clear native work still needs zero mandatory skills or skill chain. ## Claim comparison 1. Read the exact claim and its source. For a completion claim, enumerate every stated goal, including work that was never started. Give each a disposition: confirmed with evidence, concrete gap or unverifiable. 2. Inspect relevant files, command outcomes and artifacts. Separate confirmed behavior, concrete gaps, incomplete evidence and changed assumptions. Name the missing evidence instead of resolving an untestable claim by assertion. 3. Compare proposed scope with the original goal when asked about a plan. Report additions that lack authority as scope escalation; the report cannot approve them. Repeated measurements use the same question and criteria; a changed question starts a different comparison. 4. Return the cited findings with checked and not-checked scope. Keep native tracker, Git, runtime, deterministic checks and semantic judgments distinct. A quick answer can be inline. A selected durable gap report retains `reality-check-report.v1`: write `reality-check-report.json` under the caller's chosen destination, default `.agents/scratch/reality-check//`, and run `skills/reality-check/scripts/validate-output.sh `. Include the checked claim, evidence-backed finding kinds and goal-by-goal dispositions for completion/status claims. This format permits no `verdict`, `readiness` or `PASS` field; observations are not independent semantic judgment. ## Goal measurement Inspect the declared goals source; prefer `GOALS.md` when it and legacy YAML both exist. Preserve directive and gate identities and report each executable check with its actual outcome. Run the requested `ao goals` command once: `measure --json`, `validate --json`, `drift`, `history`, `export`, `meta --json`, `scenarios` or `render`. These commands do not edit the goals source, but `measure`, `drift` and `export` may write best-effort derived snapshots under `.agents/ao/goals/baselines/`. `render --out ` writes a caller-selected spec; never target the goals source or another non-derived file. Use stdout when no output file is requested. Return command, exit code, goal-level results, aggregate measurement, missing evidence and checked/not-checked scope. Do not add, remove, prioritize, migrate or repair goals, or turn a measurement gap into assigned work. ## Native status Use `ao status` for the local evidence-store view. It validates content-addressed intent and verdict artifacts before counting them, reports corruption or unavailable sources, and shows evidence recency. Its durable stores are `.agents/ao/intents/sha256` and `.agents/ao/verdicts/sha256`; a count is not a per-artifact digest inventory. Inspect a specific digest or timestamp only when that artifact is part of the requested question. Report caller-supplied subject manifests from their named location. Otherwise mark manifests, runtime phase, elapsed execution, tool-call activity and remaining work as not checked. An artifact's recent timestamp proves evidence recency, not an active worker. Read other tracker, Git or factory facts only from their own authorized source; do not blend factory completion, green checks and a fresh verdict into one health judgment. Report unavailable evidence explicitly. ## Boundary Return the selected report or snapshot. This skill neither changes native state nor issues semantic PASS, repairs records, schedules or retries work. The documented goal snapshots and requested report/spec writes are its only output side effects. A native caller pursuing an authorized outcome uses these facts and continues its work; the reporting mode does not decide completion for it.