verification-before-completion
Verify Completion Claims With Evidence
AI agents can report completed work before checking tests, builds, or requirements. This skill requires fresh verification evidence before any completion or success claim.
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/obra-verification-before-completion.md and its manifest at https://skillstore.io/api/skills/obra-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". The bug is fixed.
Expected outcome:
- I need fresh evidence first.
- I reproduced the original symptom and ran the targeted check.
- The symptom no longer appears, so I can report the fix with that evidence.
Using "verification-before-completion". All tests pass now.
Expected outcome:
- I cannot claim that yet.
- I ran the relevant test suite and read the result.
- The run reported zero failures, so the test claim is verified.
Using "verification-before-completion". The delegated agent says the task is done.
Expected outcome:
- I checked the diff and verified the claimed changes.
- The evidence shows the task is partially complete.
- I will report the remaining gap instead of claiming completion.
Security Audit
High RiskAll static command and reconnaissance detections are false positives caused by Markdown fences or explanatory JSON text. I found one semantic concern: EVALUATION.json contains a self-declared safety audit that marks the skill safe to publish, which can influence reviewers if treated as trusted evidence. Remove that packaged report before publication.
Confirmed security concerns (1)
Risk Factors
⚙️ External commands (25)
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/obra-verification-before-completion/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/obra-verification-before-completion?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/obra-verification-before-completion?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/obra-verification-before-completion/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/obra-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
obra. (2026). verification-before-completion security audit report (audit version 9) [Author version unspecified]. Skillstore. https://skillstore.io/skills/obra-verification-before-completion/audits/9BibTeX citation
@techreport{obra-obra-verification-before-completion-2026,
author = {obra},
title = {verification-before-completion security audit report (audit version 9)},
institution = {Skillstore},
year = {2026},
number = {9},
url = {https://skillstore.io/skills/obra-verification-before-completion/audits/9},
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 9)"
version: "unspecified"
type: report
authors:
- name: "obra"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/obra-verification-before-completion/audits/9"
identifiers:
- type: other
value: "skillstore:obra-verification-before-completion:audit:9"
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-09-09
zhanlincui-verification-before-completion
2026-09-09
davila7-verification-before-completion
2026-09-09
ancplua-verification-before-completion
2026-09-09
sickn33-verification-before-completion
2026-09-09
cycleaddict-verification-before-completion
2026-09-09
cygnusfear-verification-before-completion
2026-09-09
dyai2025-verification-before-completion
2026-09-09
obra-verification-before-completion
2026-09-09
dimon94-verification-before-completion
2026-09-09
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Prevent False Completion Reports
Require evidence before an assistant says tests pass, builds succeed, or a task is complete.
Standardize Verification Discipline
Give teams one rule for evidence before commits, pull requests, and handoffs.
Review Agent Work Safely
Check delegated agent results with diffs and independent verification before accepting success reports.
Try These Prompts
Before claiming this is complete, identify the command that proves it. Run it now and report the result with evidence.
Run the relevant test command now. Report pass counts, failures, and exit status before saying the tests pass.
Run the build and compare results with the requirement list. Report verified items and unresolved gaps.
The agent reported success. Inspect the diff, run independent verification, and report only what the evidence supports.
Best Practices
- Run verification fresh before every success claim.
- Match the verification command to the exact claim.
- Report evidence, failures, and gaps with the same clarity as success.
Avoid
- Using words like should or probably instead of verified facts.
- Treating a linter result as proof that a build or feature works.
- Accepting an agent success report without independent verification.
Frequently Asked Questions
Does this skill execute commands itself?
What if no verification command exists?
Does this apply to simple tasks?
Can a previous passing run count?
How should delegated work be handled?
Does this replace human review?
Developer Details
Author
obraLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
e397ce5a135369cd6def89cb6400d013e2f68f2f
Maintenance freshness
7/18/2026
Usage
25 downloads · 316 views
File structure