verification-before-completion
Verify Work Before Claiming Completion
Agents can claim success before checking real evidence. This skill requires fresh verification commands and evidence before completion claims.
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/sickn33-verification-before-completion.md and its manifest at https://skillstore.io/api/skills/sickn33-verification-before-completion/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.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 agent finished a bug fix and wants to say all tests pass.
Expected outcome:
The response names the test command, reports fresh output, and only claims success when the output supports it.
Using "verification-before-completion". A build looks likely to pass because linting passed.
Expected outcome:
The response rejects the assumption, runs the build command, and reports the actual build result.
Using "verification-before-completion". Another agent says it completed a delegated task.
Expected outcome:
The response checks the changed files, verifies expected behavior, and reports confirmed work plus unresolved gaps.
Security Audit
SafeAll static findings are false positives from Markdown code fences or verification-related prose. No evidence found of executable commands, reconnaissance behavior, prompt injection, data exfiltration, or malicious intent.
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/sickn33-verification-before-completion/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-verification-before-completion?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-verification-before-completion?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-verification-before-completion/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-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
sickn33. (2026). verification-before-completion security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-verification-before-completion/audits/4BibTeX citation
@techreport{sickn33-sickn33-verification-before-completion-2026,
author = {sickn33},
title = {verification-before-completion security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/sickn33-verification-before-completion/audits/4},
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 4)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/sickn33-verification-before-completion/audits/4"
identifiers:
- type: other
value: "skillstore:sickn33-verification-before-completion:audit:4"
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: HighWhat You Can Build
Pre-Commit Verification
Confirm tests, lint checks, and build output before committing code or opening a pull request.
Agent Handoff Review
Check another agent report against file changes and verification evidence before accepting completion.
Bug Fix Confirmation
Verify the original failure mode and related regression tests before saying a bug is fixed.
Try These Prompts
Before you claim this task is complete, identify the command that proves it. Run it, read the full output, and report the result.
Verify the original bug is fixed. Run the relevant test or reproduction, include the observed result, and state any remaining risk.
Run the full verification set for this change. Check tests, build, and changed requirements before stating whether the PR is ready.
Review the agent report against the diff and fresh verification output. Accept only claims supported by evidence from this session.
Best Practices
- Run the exact command that proves the claim you plan to make.
- Read the full output and check failures before summarizing status.
- Report uncertainty plainly when verification is incomplete or blocked.
Avoid
- Do not claim success from confidence, memory, or partial checks.
- Do not treat a linter result as proof that a build passes.
- Do not accept another agent report without independent verification.