Agent skill

Reality Check

by boshu2 in boshu2/agentops

Audit claims that work is done or shipped against the diff or repo.

Apache-2.0Auto-check passed

Install Reality Check

skills CLI
$ npx skills add boshu2/agentops --skill reality-check -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install boshu2/agentops reality-check --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/boshu2/agentops.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/reality-check .claude/skills/reality-check && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
reality-check
GitHub stars
448
Used in
1 other repo
Token cost
~1.3k tokens
SKILL.md length
564 words
Files
6 (incl. scripts, references)
Skills in repo
31
Repo updated
First seen
Licence
Apache-2.0

At a glance

Audit claims that work is done or shipped against the diff or repo.

  • Works in 4 steps: Read the exact claim and its source, and… → Inspect the relevant files, command… → When asked about a plan, compare… → …
  • : asked whether something really got done
  • SKILL.md covers Claim comparison, Establish the requested outcome, Goal measurement and Native status, plus 1 more section
  • Runs Shell scripts from its folder

What it does

Reality Check is an agent skill from boshu2/agentops. Audit claims that work is done or shipped against the diff or repo. Use when: asked whether something really got done, even if it looks obvious.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including scripts and reference files (for example `references/goals.md`, `references/status.md` and `schemas/reality-check-report.v1.schema.json`).

The repository describes itself as: DevOps discipline for AI coding agents: shape the work, track it as a graph, and get each change judged by a context that didn't write it. The licence is Apache-2.0.

When your agent uses it

  • : asked whether something really got done
  • Even if it looks obvious

Example prompts

  • “/reality-check”

Requirements

  • A Bash shell

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Read the exact claim and its source, and split it into its separate items.
  2. Inspect the relevant files, command outcomes and artifacts, separating
  3. When asked about a plan, compare proposed scope with the original goal;
  4. Return the ledger with checked and not-checked scope. Keep native tracker,

What it can do on your machine

Read from SKILL.md and the folder at commit 8704853. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 2 files in scripts/ (Shell), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Reality Check loads about 1.3k tokens when it runs, and up to ~1.8k if it reads all its reference files. Until then it costs about 40 tokens; SKILL.md has 564 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~40
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from boshu2/agentops at commit 8704853, republished under its Apache-2.0 licence (© boshu2). 564 words, ~1,311 tokens.

Download SKILL.mdSave it as .claude/skills/reality-check/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
reality-check
description
Audit claims that work is done or shipped against the diff or repo. Use when: asked whether something really got done, even if it looks obvious.
practices
design-by-contract, evidence-based-engineering
hexagonal_role
domain
consumes
caller-question, native-source-evidence
produces
reality-check-report.v1, goal-measurement-report, native-status-snapshot
skill_api_version
1
user-invocable
true
metadata.tier
judgment
metadata.capabilities
compare_claim_to_evidence, measure_declared_goals, report_native_status
metadata.effects
write_advisory_gap_report, write_goal_snapshot, write_requested_rendered_spec
metadata.canonical_status
canonical

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. Neighbours: advice on a plan or change is Review; an acceptance verdict on a finished change is Validate.

Claim comparison

Enumerate every stated claim, including work that was never started, and give each its own disposition: confirmed (cite the evidence), gap (cite what is missing or contradicts it) or unverifiable (name the evidence that would settle it). The named failure mode is auditing only what the diff touched: a claimed item with no trace in the evidence is a gap, not something to leave out of the report.

  1. Read the exact claim and its source, and split it into its separate items.
  2. Inspect the relevant files, command outcomes and artifacts, separating confirmed behavior, concrete gaps, incomplete evidence and changed assumptions. Credit only what the evidence shows: a reported run without its output, behavior left to a default or another component, and a test that exercises code without asserting the claimed outcome are unverifiable, not confirmed. Name the missing evidence instead of resolving an untestable claim by assertion.
  3. When asked about a plan, compare proposed scope with the original goal; additions that lack authority are scope escalation the report cannot approve. Repeated measurements reuse the same question and criteria; a changed question starts a different comparison.
  4. Return the ledger with checked and not-checked scope. Keep native tracker, Git, runtime, deterministic-check and semantic-judgment facts distinct.
text
Claim: <the claim as stated, and where it came from>
| # | Stated item | Disposition | Evidence, or what would settle it |
|---|---|---|---|
| 1 | <item> | confirmed / gap / unverifiable | <file:line, command output, artifact> |
Checked: <what was inspected>. Not checked: <what was not>.

The ledger reports evidence; it carries no verdict, readiness call or PASS.

A quick answer is inline. A selected durable gap report uses reality-check-report.v1: write reality-check-report.json under the caller's chosen destination, default .agents/scratch/reality-check/<run-id>/, and check it with this skill's scripts/validate-output.sh <report.json>. Record the claim, evidence-backed finding kinds and the per-item dispositions in coverage. The format permits no verdict, readiness or PASS field; observations are not independent semantic judgment.

Show full SKILL.md (235 more words)Show less

Establish the requested outcome

A request to check a stated claim (done, shipped, fixed, every item complete) against the evidence selects the claim comparison above without another question; so do explicit requests to measure declared goals or report native status. A bare readiness question with no claim and no settled purpose is ambiguous: ask once whether the caller wants advisory findings or an acceptance judgment, and wait. A claim audit is not acceptance and cannot substitute for Validate's fresh, author-distinct judgment. If acceptance is wanted, hand off and report a missing fresh reviewer as a gap, never as validation that occurred. Shared routing and handoff detail: advice or acceptance.

Goal measurement

Running ao goals against the declared goals source, its derived snapshots and what to return are in goals. Do not add, remove, prioritize, migrate or repair goals, or turn a measurement gap into assigned work.

Native status

Reading the evidence store with ao status, and what a snapshot cannot show, are in status. A recent artifact timestamp proves evidence recency, not an active worker.

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.

© boshu2, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (scripts, references) in skills/reality-check of boshu2/agentops.

  • SKILL.md
  • references/goals.md
  • references/status.md
  • schemas/reality-check-report.v1.schema.json
  • scripts/validate-output.sh
  • scripts/validate.sh

Open the folder on GitHubat commit 8704853

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in boshu2/agentops, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Reality Check next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Reality Check compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Reality Check this skillboshu2/agentops4481 repos~1.3kAutomated safety check: PassApache-2.0
Dos Verify Done Claimssickn33/agentic-awesome-skills47k1 repos~2.1kAutomated safety check: PassMIT
Claimsruvnet/ruflo74k2 repos~1.1kAutomated safety check: PassMIT
Shipmillionco/react-doctor15k—~716Automated safety check: PassCustom licence
Shipsimstudioai/sim30k—~4.2kAutomated safety check: PassApache-2.0
Ship Itvectorize-io/hindsight47k—~1.9kAutomated safety check: PassMIT

Similar skills

  • Dos Verify Done Claims

    sickn33/agentic-awesome-skills

    Before accepting an agent's 'done / shipped / fixed' claim, verify it against ground truth (git ancestry + the commit's own diff) using the DOS kernel's dos verify and dos commit-audit — never the…

    47k GitHub starsUsed in 1 repo~2.1k tokens
    Media & CreativeAuto-check passed
  • Claims

    ruvnet/ruflo

    Claims-based authorization for agents and operations. An agent skill from ruvnet/ruflo.

    74k GitHub starsUsed in 2 repos~1.1k tokens
    Backend & APIsAuto-check passed
  • Ship

    millionco/react-doctor

    Take the current branch from done-coding to merge-ready in one pass — review the diff against AGENTS.md, deslop, commit and push, open a PR using rule-validate's PR copy, then babysit until mergeable.

    15k GitHub stars~716 tokensUpdated today
    DevelopmentAuto-check passed
  • Ship

    simstudioai/sim

    Commit, push, and open a PR to staging in one shot — runs the cleanup pass and, when migrations changed, the db-migrate safety review first

    30k GitHub stars~4.2k tokensUpdated today
    DevelopmentAuto-check passed
  • Ship It

    vectorize-io/hindsight

    Take a PR from review to merged — run the repo's code-review skill on it in a loop (review, fix, re-review) until nothing is left to fix, applying ALL fixes on the PR branch, wait for CI green, then…

    47k GitHub stars~1.9k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Ship Workflow

    garrytan/gstack

    Takes finished code to a pull request: merges the base branch, runs tests, reviews the diff, bumps VERSION, updates the CHANGELOG, commits, pushes and opens the PR.

    136k GitHub stars~20k tokensUpdated today
    DevelopmentAuto-check: notes

More from boshu2/agentops

All 31 skills in this repo
  • Agent Native

    boshu2/agentops

    Dispatch independent tasks to parallel workers or subagents without write collisions.

    448 GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed
  • Council

    boshu2/agentops

    Compare independent opinions from several models or contexts without inflating agreement.

    448 GitHub starsUsed in 1 repo~3k tokens
    Auto-check passed
  • Craft Goal

    boshu2/agentops

    Draft or lint a bounded long-running goal prompt with a finish line and hard limits.

    448 GitHub starsUsed in 1 repo~2.7k tokens
    Auto-check passed
  • Doc

    boshu2/agentops

    Write or update READMEs, docs, repo instructions and handoff notes, checked against source.

    448 GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed
  • Idea Genie

    boshu2/agentops

    Brainstorm evidence-backed options for what to build, or stress-test an idea.

    448 GitHub starsUsed in 1 repo~1.8k tokens
    Auto-check passed
  • Implement

    boshu2/agentops

    Change or repair code, config or services without weakening tests; report what ran and what did not.

    448 GitHub starsUsed in 1 repo~2.3k tokens
    Auto-check passed

Questions about Reality Check

What does Reality Check do?

Audit claims that work is done or shipped against the diff or repo. Reality Check is an agent skill from boshu2/agentops. Audit claims that work is done or shipped against the diff or repo.

When should I use Reality Check?

Reality Check fits situations like: : asked whether something really got done; even if it looks obvious.

How do I install Reality Check in Claude Code?

Run `npx skills add boshu2/agentops --skill reality-check -a claude-code`. Or copy the skill folder (skills/reality-check in boshu2/agentops) into .claude/skills/reality-check in your project. Claude Code loads it when a task matches its description.

How do I install Reality Check in Codex?

Run `npx skills add boshu2/agentops --skill reality-check -a codex`. Or copy the skill folder (skills/reality-check in boshu2/agentops) into .agents/skills/reality-check in your project. Codex loads it when a task matches its description.

Can I use Reality Check in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add boshu2/agentops --skill reality-check -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/reality-check, .gemini/skills/reality-check, .github/skills/reality-check and .opencode/skills/reality-check in your project.

What does Reality Check need to run?

Going by SKILL.md and its folder, Reality Check needs a shell for the scripts in its folder. Our summary lists: A Bash shell.

Does Reality Check access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Reality Check safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Reality Check use?

Reality Check is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Reality Check use?

About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 530 tokens, read only when the agent opens those files.

What are the alternatives to Reality Check?

Skills that share tags, products or a category with Reality Check: Dos Verify Done Claims (sickn33/agentic-awesome-skills, 47k stars), Claims (ruvnet/ruflo, 74k stars), Ship (millionco/react-doctor, 15k stars) and Ship (simstudioai/sim, 30k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Reality Check?

boshu2 (a GitHub user) maintains it in boshu2/agentops, which has 448 GitHub stars. The repository holds 31 skills in this directory. The repository was last updated on October 9, 2026.

Source: boshu2/agentops on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.