Skills verification-before-completion
📦

verification-before-completion

Content revision r1 Safe ⚙️ External commands

Verify Completion Claims Before Reporting

Completion claims can be wrong when agents rely on memory or confidence. This skill requires fresh evidence before reporting success.

Supports: Claude Codex Code(CC)
🥉 79 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "verification-before-completion" from https://skillstore.io/skills/codingcossack-verification-before-completion.md and its manifest at https://skillstore.io/api/skills/codingcossack-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.

Markdown detail GET /skills/codingcossack-verification-before-completion.md Signed manifest GET /api/skills/codingcossack-verification-before-completion/manifest Signed lockfile GET /api/skills/codingcossack-verification-before-completion/lockfile

Test it

Using "verification-before-completion". The agent says the bug is fixed and all tests pass.

Expected outcome:

Recommended response: verify independently. Inspect the changed files, run the relevant regression test, and report the observed result.

Using "verification-before-completion". A developer wants to say the build is clean after running only lint.

Expected outcome:

Recommended response: lint does not prove the build. Run the build command or state that build verification is still missing.

Using "verification-before-completion". A pull request is ready except the requirements were not re-read.

Expected outcome:

Recommended response: re-read the checklist, compare each requirement to the implementation, and report any uncovered items.

Security Audit

Safe
v8 • 7/6/2026 Open versioned report

All static external-command detections are false positives caused by Markdown code fences and examples, not executable code. The system-reconnaissance detection is also a false positive because the line warns users to verify delegated agent work. No prompt injection, exfiltration intent, or malicious automation was found.

1
Files scanned
100
Lines analyzed
0
Review items
0
False positives ignored

Risk Factors

⚙️ External commands (11)
SKILL.md:14-23 SKILL.md:23-34 SKILL.md:34-41 SKILL.md:41-78 SKILL.md:78-81 SKILL.md:81-84 SKILL.md:84-87 SKILL.md:87-90 SKILL.md:90-93 SKILL.md:93-96 SKILL.md:96-99
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
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.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/codingcossack-verification-before-completion/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/codingcossack-verification-before-completion/security.svg)](https://skillstore.io/skills/codingcossack-verification-before-completion?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/codingcossack-verification-before-completion?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/codingcossack-verification-before-completion/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/codingcossack-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

CodingCossack. (2026). verification-before-completion security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/codingcossack-verification-before-completion/audits/8

BibTeX citation

@techreport{codingcossack-codingcossack-verification-before-completion-2026, author = {CodingCossack}, title = {verification-before-completion security audit report (audit version 8)}, institution = {Skillstore}, year = {2026}, number = {8}, url = {https://skillstore.io/skills/codingcossack-verification-before-completion/audits/8}, 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 8)" version: "unspecified" type: report authors: - name: "CodingCossack" date-released: "2026-07-06" url: "https://skillstore.io/skills/codingcossack-verification-before-completion/audits/8" identifiers: - type: other value: "skillstore:codingcossack-verification-before-completion:audit:8" description: "Skillstore immutable audit report identifier"

Compare variants

10 installable variants

Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.

Why this variant is first

Highest Skillstore Score
CodingCossack Recommended Current

codingcossack-verification-before-completion

Skillstore Score 79
Evidence Confidence High
Skillstore usage 13
Updated

2026-08-21

ZhanlinCui

zhanlincui-verification-before-completion

Skillstore Score 78
Evidence Confidence High
Skillstore usage 41
Updated

2026-08-21

davila7

davila7-verification-before-completion

Skillstore Score 78
Evidence Confidence High
Skillstore usage 12
Updated

2026-08-21

ANcpLua

ancplua-verification-before-completion

Skillstore Score 78
Evidence Confidence High
Skillstore usage 10
Updated

2026-08-21

sickn33

sickn33-verification-before-completion

Skillstore Score 78
Evidence Confidence High
Skillstore usage 8
Updated

2026-08-21

Cygnusfear

cygnusfear-verification-before-completion

Skillstore Score 78
Evidence Confidence High
Skillstore usage 7
Updated

2026-08-21

Cycleaddict

cycleaddict-verification-before-completion

Skillstore Score 78
Evidence Confidence High
Skillstore usage 6
Updated

2026-08-21

DYAI2025

dyai2025-verification-before-completion

Skillstore Score 75
Evidence Confidence Medium
Skillstore usage 9
Updated

2026-08-21

obra

obra-verification-before-completion

Skillstore Score 38
Evidence Confidence High
Skillstore usage 30
Updated

2026-08-21

Dimon94

dimon94-verification-before-completion

Skillstore Score 38
Evidence Confidence Medium
Skillstore usage 11
Updated

2026-08-21

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
70
Community
91
Spec Compliance

What You Can Build

Validate Coding Agent Results

Require command output or a checked diff before accepting an agent completion report.

Prepare Pull Request Updates

Confirm tests, lint, builds, and requirements before writing a final status update.

Enforce Regression Evidence

Use a red-green verification cycle before claiming that a bug fix is complete.

Try These Prompts

Basic Verification Check 
Before you say this task is done, identify the verification command, run it, read the output, and report the exact result.
Focused Test Confirmation 
Use the verification-before-completion skill for this change. Choose the most specific test or lint command that covers the edited code, run it fresh, and summarize the evidence.
Release Readiness Review 
Verify this branch before release. Check tests, lint, build status, and requirement coverage, then list any gaps instead of assuming completion.
Delegated Agent Audit 
Audit the agent completion report. Inspect the diff, verify the changed behavior independently, and only confirm completion when the evidence supports it.

Best Practices

  • Run fresh verification in the current work session before making success claims.
  • Match the verification command to the exact claim being made.
  • Report incomplete or failing verification clearly, with the observed evidence.

Avoid

  • Claiming tests pass based on a previous run or expected behavior.
  • Treating lint success as proof that build and runtime behavior are correct.
  • Accepting another agent completion report without checking the diff or outputs.

Frequently Asked Questions

What does this skill help verify?
It helps verify completion claims for tests, lint, builds, bug fixes, regression tests, delegated work, and requirements.
Does it run tests automatically?
No. It guides the agent to choose and run the right verification command when the environment allows it.
Can it guarantee that a fix is correct?
No. It improves evidence quality, but correctness still depends on the available tests and review process.
Is it useful with Claude, Codex, and Claude Code?
Yes. The workflow is tool-agnostic and applies to any coding assistant that can inspect changes and run checks.
How should failures be reported?
Report the command, exit status, key failure details, and the remaining work instead of claiming success.
When should this skill be used?
Use it before final responses, commits, pull requests, release notes, or any message that claims work is complete.

Developer Details

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Repository

https://github.com/CodingCossack/agent-skills-library/tree/main/skills/verification-before-completion

Ref

d11af420e07cd866fe39cfa937efef3223896c06

Maintenance freshness

7/18/2026

Usage

8 downloads · 233 views

File structure

📄 SKILL.md

More from CodingCossack

View all

Related Skills

View all