reality-checker
Reviews code changes, validates test coverage, checks deployment criteria, and gates production approvals based on evidence from automated screenshots, test results, and specification compliance checks. Defaults to "NEEDS WORK" unless comprehensive evidence supports readiness. Use when a user asks to approve a PR, run a release readiness check, validate deployment criteria, perform a QA gate review, check if code is production-ready, or assess integration test results.
93
92%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly articulates specific capabilities (code review, test validation, deployment gating), includes a distinctive behavioral detail (defaults to NEEDS WORK), and provides comprehensive trigger terms via an explicit 'Use when...' clause. It uses proper third-person voice throughout and covers a well-defined niche that would be easily distinguishable from other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: reviews code changes, validates test coverage, checks deployment criteria, gates production approvals, and specifies evidence types (automated screenshots, test results, specification compliance checks). Also describes a default behavior ('Defaults to NEEDS WORK'). | 3 / 3 |
Completeness | Clearly answers both 'what does this do' (reviews code changes, validates test coverage, checks deployment criteria, gates production approvals) AND 'when should Claude use it' with an explicit 'Use when...' clause listing six distinct trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'approve a PR', 'release readiness check', 'validate deployment criteria', 'QA gate review', 'production-ready', 'integration test results'. These are terms a user would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Occupies a clear niche around production readiness gating and deployment approval. The combination of PR approval, QA gates, release readiness, and the default-to-NEEDS-WORK behavior makes it highly distinct and unlikely to conflict with general code review or testing skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-structured skill that provides clear, actionable guidance for integration validation with excellent workflow clarity including explicit validation checkpoints and fail-fast behavior. The automatic fail triggers and structured report template ensure consistent, evidence-based assessments. Minor verbosity in the report template and some pass criteria descriptions could be tightened, but overall the content earns its token budget.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient and avoids explaining concepts Claude already knows, but the report template is quite lengthy and some sections (like the automatic fail triggers) could be tightened. The table formats and structured steps are good, but the overall length (~100 lines) includes some redundancy in pass/fail criteria descriptions. | 2 / 3 |
Actionability | Provides fully executable bash commands, specific file paths, concrete pass/fail criteria with measurable thresholds (e.g., load time ≤ 3 seconds), specific screenshot filenames to check, and a complete report template. The guidance is copy-paste ready and leaves no ambiguity about what to do at each step. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflow with explicit sequencing (Steps 1-3), clear validation checkpoints at each step, explicit fail actions that prevent proceeding (Step 1 failure blocks Step 2), automatic fail triggers as a safety net, and re-assessment conditions. The feedback loop of fix → re-run is clearly stated. | 3 / 3 |
Progressive Disclosure | The skill is well-structured with clear sections (Core Workflow steps, Automatic Fail Triggers, Report Template) and appropriately references detailed testing protocols in a separate file (`ai/agents/integration.md`). The reference is one level deep and clearly signaled. The report template is inline but justified since it's the primary output artifact. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- OpenRoster-ai/awesome-agents
- Commit
010799b
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.