verification-before-completion
Verify Claims Before Completion
AI agents can overstate progress when they rely on assumptions instead of fresh evidence. This skill enforces a clear verification gate before completion, fix, or passing claims.
Stop for confirmation before installing.
Review the plan and obtain explicit user consent before changing files.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "verification-before-completion" from https://skillstore.io/skills/dyai2025-verification-before-completion.md and its manifest at https://skillstore.io/api/skills/dyai2025-verification-before-completion/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "verification-before-completion". I changed the parser. Can I say the bug is fixed?
Expected outcome:
Not yet. Run the regression test that reproduces the parser bug, inspect the output, and only then state whether it is fixed.
Using "verification-before-completion". The linter passed, so is the build good?
Expected outcome:
No. A passing linter does not prove compilation. Run the build command and report its exit status and relevant output.
Using "verification-before-completion". The subagent says it finished the refactor.
Expected outcome:
Verify independently. Review the VCS diff, run the relevant checks, and report the actual state rather than trusting the success message.
Security Audit
SafeMost static findings are false positives caused by Markdown code fences and prose that mention verification concepts. The skill does not instruct hidden command execution, data access, network access, or prompt injection. The packaged SKILL.zip remains an unscanned binary artifact and should be manually reviewed before publication.
Risk Factors
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/dyai2025-verification-before-completion/audits/10?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/dyai2025-verification-before-completion?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/dyai2025-verification-before-completion?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/dyai2025-verification-before-completion/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/dyai2025-verification-before-completion.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
DYAI2025. (2026). verification-before-completion security audit report (audit version 10) [Author version unspecified]. Skillstore. https://skillstore.io/skills/dyai2025-verification-before-completion/audits/10BibTeX citation
@techreport{dyai2025-dyai2025-verification-before-completion-2026,
author = {DYAI2025},
title = {verification-before-completion security audit report (audit version 10)},
institution = {Skillstore},
year = {2026},
number = {10},
url = {https://skillstore.io/skills/dyai2025-verification-before-completion/audits/10},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "verification-before-completion security audit report (audit version 10)"
version: "unspecified"
type: report
authors:
- name: "DYAI2025"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/dyai2025-verification-before-completion/audits/10"
identifiers:
- type: other
value: "skillstore:dyai2025-verification-before-completion:audit:10"
description: "Skillstore immutable audit report identifier"
Compare variants
10 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
codingcossack-verification-before-completion
2026-08-21
zhanlincui-verification-before-completion
2026-08-21
davila7-verification-before-completion
2026-08-21
ancplua-verification-before-completion
2026-08-21
sickn33-verification-before-completion
2026-08-21
cygnusfear-verification-before-completion
2026-08-21
cycleaddict-verification-before-completion
2026-08-21
dyai2025-verification-before-completion
2026-08-21
obra-verification-before-completion
2026-08-21
dimon94-verification-before-completion
2026-08-21
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Prevent premature completion claims
Require an agent to run the relevant command before saying a task is done or fixed.
Improve review readiness
Create a habit of checking tests, builds, and requirements before commits or pull requests.
Verify delegated agent work
Check diffs and run verification instead of accepting another agent's success report at face value.
Try These Prompts
Before you say this is complete, identify the command that proves it, run it, read the output, and report the actual result.
Verify this change with the relevant test and build commands. Only claim success if the fresh output confirms it.
Re-read the requirements, create a checklist, verify each item with evidence, and report any gaps without assuming completion.
An agent reported success. Inspect the diff, verify the intended behavior, run the necessary checks, and report the true status with evidence.
Best Practices
- Choose the verification command that directly proves the claim you want to make.
- Read the full command output and check the exit code before summarizing results.
- Report uncertainty or failures clearly instead of converting them into success claims.
Avoid
- Saying work should pass because the code looks correct.
- Using a partial check as proof for a broader claim.
- Trusting an agent success report without checking the diff and behavior.
Frequently Asked Questions
Does this skill run tests automatically?
When should I use this skill?
Does a passing linter prove the build works?
Can prior test output count as evidence?
How does it help with delegated agent work?
Is this skill useful outside Claude Code?
Developer Details
Author
DYAI2025License
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
1ffa7643651792ccb4bd3b15d924d2c97edff755
Maintenance freshness
7/18/2026
Usage
7 downloads · 260 views