agent-reliability

Enforces verification, honesty, and scope-discipline rules for AI coding agents.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/astroville/sprout --skill agent-reliability-astroville
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-reliability
Source: https://github.com/astroville/sprout/tree/main/.claude/skills/agent-reliability
Command: npx skills add https://github.com/astroville/sprout --skill agent-reliability-astroville

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding agents frequently hallucinate file paths and APIs, claim work is done without running tests, drift beyond the requested scope, or stop mid-task. This Skill provides behavioral guardrails that prevent these failure modes during code changes. ## Core Features & Use Cases - Verification rules: Requires reading files before editing, running tests or linters after changes, and re-reading diffs before declaring completion. - Hallucination prevention: Mandates grounding claims in actual source reads, marking assumptions explicitly, and stating uncertainty instead of inventing answers. - Scope and persistence discipline: Enforces one logical change at a time, the Two-Reading Rule for ambiguous requirements, and continuing multi-step tasks until a true blocker is hit. - Use Case: An engineer agent implementing a multi-phase spec loads this skill so it verifies each change with the test suite, never silently reclassifies acceptance criteria, and produces a Completion Ledger accounting for every item. ## Quick Start Load the agent-reliability skill so the agent verifies every code change with tests and never claims completion without checking its work.

Frequently Asked Questions about agent-reliability

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stop an AI coding agent from hallucinating file paths and APIs?▼

Require the agent to read directories and source files before referencing them, and to mark each load-bearing claim as read or assumed. This skill's grounding rule forces assumed claims to be verified or downgraded before any proposal is written.

How to make an AI agent verify its code changes before finishing?▼

Mandate that the agent runs the project's test suite, linter, or type checker after every change and re-reads its own diff. This skill also requires establishing a passing baseline before modifying code so regressions are attributable.

What is the Two-Reading Rule for ambiguous requirements?▼

When a requirement has two plausible readings, the agent must name both and pick the more thorough one or ask. It may not silently choose the easier interpretation, and verbs that could mean show or make work default to make it work.

When should an AI agent stop a multi-step task?▼

Only on a true blocker: an unrecoverable tool error, missing credentials, a decision only the user can make, or two failed attempts at the same approach. Stopping early to ask whether to continue is treated as a failure mode.

Does this skill replace implementation or design guidelines?▼

No. It complements skills like implementation-principles, which cover what to build. This skill covers how to stay reliable while building: verification, honesty, scope discipline, and error recovery.