excrtx-behavior-accuracy

Verifies system state with shell commands before asserting completion of external actions.

1|Updated May 26, 2026
One-click install
npx skills add https://github.com/elderbernardi/exocortex.saas --skill excrtx-behavior-accuracy-elderbernardi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: excrtx-behavior-accuracy
Source: https://github.com/elderbernardi/exocortex.saas/tree/main/skills/excrtx-behavior-accuracy
Command: npx skills add https://github.com/elderbernardi/exocortex.saas --skill excrtx-behavior-accuracy-elderbernardi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents often claim they completed actions like closing GitHub issues, making commits, or creating files without actually verifying the result, which erodes trust and hides silent failures. This Skill enforces empirical verification before any completion claim. ## Core Features & Use Cases - Mandatory Verification Commands: Maps each action type to a concrete check, such as gh issue view <N> --json state for issues, git log --oneline -1 for commits, and test -f <path> for file creation. - Evidence-Based Reporting: Requires every completion report to include the actual command output as proof, replacing bare assertions like "done" or "feito". - Draft-First Integration: Combines with draft-first governance so external actions follow a draft, approve, execute, verify, and report sequence. - Use Case: After closing GitHub issue #48, the agent runs gh issue view 48 --json state, confirms the state is CLOSED, and reports the result with the command output as proof. ## Quick Start Ask the agent to close a GitHub issue or create a file and require it to show the verification command output proving the action succeeded.

Frequently Asked Questions about excrtx-behavior-accuracy

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

FAQPage Schema
How do I verify a GitHub issue was actually closed?▼

Run `gh issue view <NUMBER> --json state` and confirm the returned state equals CLOSED before reporting completion. Only assert the issue is closed when this command output confirms it, and include the output as proof in your report.

How to confirm a git commit or push succeeded?▼

For commits, run `git log --oneline -1` and check that the new hash appears in the log. For pushes, run `git status -b` and verify the branch is not ahead of origin before claiming the push completed.

What command verifies a file was created or deleted?▼

Use `test -f <path> && echo "EXISTS"` to confirm file creation, and `test ! -f <path>` to confirm deletion. Only assert the file operation succeeded when the test result matches the expected state.

When should action verification not be applied?▼

Verification is not required for internal reasoning steps, reading files, or searching knowledge bases. It only applies to assertions about actions that change external state, such as closing issues, committing code, sending messages, or deploying.

What should an agent say if it has not verified an action yet?▼

Instead of claiming completion, the agent should state what it is doing, such as "Fiz o commit. Verificando...", then run the verification command and show the output. If verification fails or is ambiguous, it must state what was attempted and what remains uncertain.