reality-check

Featured

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.

AI & Automation 446 stars 41 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 91/100

Stars 20%
88
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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...

Details

Author
boshu2
Repository
boshu2/agentops
Created
10 months ago
Last Updated
today
Language
Go
License
Apache-2.0

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

reality-check

Use this skill to give a team lead or engineering manager a fast, honest, CURRENT-STATE picture of their team or project — what's actually happening right now, pulled from live sources (issue tracker, VCS, monitoring) via MCP tools when available, or asked for directly when not. Trigger on "what's actually going on with my team right now", "give me a reality check", "what's on fire", "quick pulse check before my 1:1s", "are we actually on track". This is deliberately lighter-weight and NOT a scored assessment — for a structured, evidence-scored engagement across CI/CD, testing, code review, monitoring, DX, and ownership, use the audit skill instead. Standalone — no prior audit is required.

4 Updated 2 days ago
EmanueleMinotto
AI & Automation Listed

reality-check

Use whenever someone hands you an AI-generated technical plan, recommendation set, setup guide, or tool/config list and says "validate this", "fact-check this", "is this real", "is this accurate", "did it hallucinate", "sanity-check this", "pressure-test this", "is this overkill", or asks whether a plan is feasible and worth doing. Trigger hardest when the content reads as machine-written and is dense with checkable specifics that could be fabricated — repo URLs, CLI flags, file paths, versions, env vars, named "best-practice" patterns, time estimates. The job: pressure-test the thing for hallucinations, factual errors, and unnecessary complexity, then verify every surviving claim against live sources before the user acts on it. Do NOT trigger for a bare dependency question — whether a specific package is real, alive, and maintained is leftpad's registry rung, so "should we add this package" or "is this crate abandoned" goes there. This VERIFIES an existing plan's accuracy and practical value, not choosing be

0 Updated 2 weeks ago
scoobydrew83
Code & Development Listed

reality-check

Verify a file's actual implementation matches its inferred purpose. Use when reviewing unfamiliar files, debugging unexpected behavior, or validating code-to-intent alignment.

1 Updated today
NomadicDaddy