Verify Completion Claims With Recorded Evidence
Completion claims can hide failed, skipped, or untested requirements. This skill guides requirement-level verification with observed output, commit-bound evidence, and explicit human acceptance.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "executor-verification" from https://skillstore.io/skills/atri10-executor-verification.md and its manifest at https://skillstore.io/api/skills/atri10-executor-verification/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.
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Using "executor-verification". Verify an integration criterion that requires HTTP 409 with no partial write.
Expected outcome:
Using "executor-verification". Summarize a verification round where one manual criterion was never checked.
Expected outcome:
Using "executor-verification". Run a criterion when the evidence runner lacks a required credential.
Expected outcome:
All 155 static findings are false positives involving Markdown formatting, intended local verification, companion paths, or protective secret-handling guidance. Two semantic workflow risks concern unisolated regression reverts and retained evidence after secret-scan failures. No evidence found of malicious prompt injection or exfiltration; companion helper implementations are outside the two reviewed files.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
https://skillstore.io/skills/atri10-executor-verification/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/atri10-executor-verification?utm_source=security_passport_badge)<a href="https://skillstore.io/skills/atri10-executor-verification?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/atri10-executor-verification/security.svg" alt="Skillstore security assessment" loading="lazy"></a><iframe src="https://skillstore.io/embed/skills/atri10-executor-verification.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>atri10. (2026). executor-verification security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/atri10-executor-verification/audits/1@techreport{atri10-atri10-executor-verification-2026,
author = {atri10},
title = {executor-verification security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/atri10-executor-verification/audits/1},
note = {Author version unspecified}
}cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "executor-verification security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "atri10"
date-released: "2026-10-05"
url: "https://skillstore.io/skills/atri10-executor-verification/audits/1"
identifiers:
- type: other
value: "skillstore:atri10-executor-verification:audit:1"
description: "Skillstore immutable audit report identifier"
Walk existing acceptance criteria, gather suitable evidence, and present unresolved requirements before a feature handoff.
Compare observed test and smoke outcomes with requirements, without treating a passing unit suite as full feature proof.
Dispatch one evidence runner per criterion, inspect the returned artifact, and route failures back to the owning implementation plan.
Verify criterion [reference] in [verification document] at the current state. Report its requirement, named method, observed output, and status without changing code.
Walk every criterion in [verification document]. Record state, commands, outcomes, and evidence citations. Summarize all four statuses and stop for human acceptance.
Prepare one runner for [criterion] using the provided template. Fill every placeholder, select a model explicitly, and verify prerequisites before dispatch.
Review fix [commit] against the existing ledger. Identify affected criteria and append a new round. Use isolated regression checks and scan retained evidence before committing.
Author
atri10License
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
6d0b11444384184b7ae743742a7e233a9a705cd9
Maintenance freshness
10/6/2026
Usage
0 downloads · 0 views
File structure
Audit and Repair Plans Before Execution
Separate plans can hide missing requirements, incompatible interfaces, and broken dependencies. This skill reviews the complete plan set and coordinates repairs with independent verification.
Execute Approved Plans with Subagents and Reviews
Long implementation plans can lose task state and accumulate unreviewed changes. This skill coordinates scoped subagents, review gates, and durable records across execution and recovery.
Clarify Initiatives and Compare Approaches
Unclear requirements and unsupported assumptions make technical decisions difficult. This skill guides structured discovery, evidence gathering, and approach comparisons before human approval.
Write Testable Specifications Before Planning
Ambiguous requirements create conflicting implementations and unverifiable reviews. This skill guides linked specifications, risk assessments, and verification strategies through explicit human approval.
Prepare Executor Integration and Session Handoffs
Session changes can lose decisions, verification evidence, and unfinished implementation work. This skill guides human-controlled integration, durable pause records, and resumption checked against the current repository.
Audit and Repair Initiative Artifacts
Conflicting documents can carry incorrect decisions into later development phases. This skill coordinates independent audits, scoped repairs, and fresh re-audits before phase clearance.
Verify Completion Claims Before Reporting
by CodingCossack
Completion claims can be wrong when agents rely on memory or confidence. This skill requires fresh evidence before reporting success.
Improve QA Coverage for Web Apps
by alirezarezvani
Modern teams need clear test strategy and practical automation without slowing delivery. This skill helps Claude, Codex, and Claude Code plan tests, review coverage, and scaffold QA workflows.
Manage Requirement Changes Safely
by yunshu0909
Requirement changes often expand across files without clear approval points. This skill gives Claude, Codex, and Claude Code a gated workflow for scope, impact, validation, and documentation.
Create Verifiable Agent Loop Specs
by zhangzeyu99-web
Vague coding-agent tasks drift, repeat work, and report success without evidence. Ariadne Loop turns them into bounded loop specs with verifiers, stop rules, and human gates.
Fix Bugs With Structured Triage
by Crearize
Debugging across backend and frontend can lose context and miss regression tests. This skill guides root cause analysis, minimal fixes, validation, and pull request handoff.
Review Code Before Commit
by 2389-research
Teams ship bugs when final changes are trusted too quickly. This skill adds a focused pre-commit review for security, logic, business rules, and performance.