reality-check
From the author
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.
Install
npx skills add hashgraph-online/awesome-codex-plugins --skill reality-check -a claude-code
Installs to .claude/skills/reality-check/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Download .zip
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
- Ships scripts we have not reviewedLow
Why 82
Security85
Provenance78
Maintenance100
Licence100
Adoption51
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- auditsuboss87/FDEOpsAudit an inherited engagement or implementation against its evidence. Use when taking over work or joining mid-project; distinguish verified facts from inherited claims.Other★ 947
- completion-verificationcbrock84/headcountVerifies that work is actually complete before it is claimed to be — running the checks, reading the output, and confirming the original request was satisfied rather than approximated. Use this before saying something is done, fixed, or passing; before committing or opening a pull request; and whenever a claim of success has not been backed by command output.Engineering★ 2.1K
- receipts-auditmohitagw15856/pm-claude-skillsAudit any document against its own sources — every factual claim extracted and graded as evidenced, partially evidenced, unsupported, or contradicted, with the exact source line that supports or fails it. Use when asked to fact-check a document against its sources, check whether a report's claims are backed up, verify a deck against the data, or ask 'does this doc have receipts?'. Produces a claim ledger, unsupported claims ranked by load-bearingness, a fix-or-drop call per claim, and an honesty score with stated method.Documents★ 1.5K
- principle-prove-it-worksmichael-denyer/pstack-claudeApply after completing a task, before declaring done. Verify against the real artifact (run the feature, read the actual value, inspect the diff), not a proxy, self-report, or 'it compiles.'Productivity★ 3.3K
- quality-checkinghuangjia2019/claude-code-engineeringValidate API documentation against quality standards. Use when you need to verify generated docs are complete and correct.Engineering★ 1.1K
- kiro-verify-completiongotalab/cc-sddVerify completion and success claims with fresh evidence. Use before claiming a task is complete, a fix works, tests pass, or a feature is ready for GO.Testing★ 3.7K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in