executor-verification
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.
Installer avec mon Agent
Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.
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.Votre Agent doit toujours présenter son plan et demander toute confirmation exigée par la politique de sécurité.
Ressources lisibles par les agents
Utilisez ces liens lorsquâun Agent IA, un crawler ou un script a besoin dâun contexte propre au lieu de lire toute la page.
Tester
Utilisation de « executor-verification ». Verify an integration criterion that requires HTTP 409 with no partial write.
Résultat attendu:
- Illustrative outcome: FAILED.
- Observed: the integration test received HTTP 500 instead of HTTP 409.
- Required: HTTP 409 with no partial write.
- Next step: return the mismatch to execution and reverify after the fix.
Utilisation de « executor-verification ». Summarize a verification round where one manual criterion was never checked.
Résultat attendu:
- Illustrative summary: 11 PROVEN, 0 FAILED, 1 NOT-RUN, 0 UNAVAILABLE.
- Exception: the manual criterion has no recorded observation.
- Completion remains unproven. Present the exception for human acceptance or further verification.
Utilisation de « executor-verification ». Run a criterion when the evidence runner lacks a required credential.
Résultat attendu:
- Illustrative runner outcome: NOT-RUN.
- Evidence: none; no run and no evidence file.
- Reason: the criterion requires a credential that was not provided.
- Do not inspect the environment for secrets or assume the criterion passes.
Audit de sécurité
Risque moyenAll 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.
Préoccupations de sécurité confirmées (2)
Facteurs de risque
âïž Commandes externes (50)
đ AccĂšs au systĂšme de fichiers (8)
Partager et citer ce rapport
Partagez le rapport dâĂ©valuation versionnĂ©, le badge neutre, la carte intĂ©grable et les citations. Skillstore prĂ©sente les preuves sans dĂ©cider si ce Skill est sĂ»r.
Copier le lien du rapport
https://skillstore.io/skills/atri10-executor-verification/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportBadge Markdown
[](https://skillstore.io/skills/atri10-executor-verification?utm_source=security_passport_badge)Badge HTML
<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>Carte intégrable
<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>Citations académiques (APA · BibTeX · CFF)
Citation APA
atri10. (2026). executor-verification security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/atri10-executor-verification/audits/1Citation BibTeX
@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}
}CITATION.cff
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"
Score Skillstore
Pourquoi ce score Niveau de confiance des preuves: MoyenCe que vous pouvez créer
Verify a Feature Before Handoff
Walk existing acceptance criteria, gather suitable evidence, and present unresolved requirements before a feature handoff.
Review Requirement Coverage
Compare observed test and smoke outcomes with requirements, without treating a passing unit suite as full feature proof.
Coordinate Agent Verification
Dispatch one evidence runner per criterion, inspect the returned artifact, and route failures back to the owning implementation plan.
Essayez ces prompts
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.
Bonnes pratiques
- Record the exact tested state and match each requirement to the evidence type its strategy names.
- Use an isolated worktree for regression reverts and preserve all existing user changes.
- Redact before capture, scan every retained evidence attempt, and resolve sensitive originals before tracking or committing.
Ăviter
- Treating passing unit tests, clean review reports, or expected output as proof of every requirement.
- Changing code during verification to obtain a passing result without a separate fix and new evidence round.
- Hiding FAILED, NOT-RUN, or UNAVAILABLE outcomes when presenting the completion summary.
Foire aux questions
What does this skill verify?
Can I use it with Claude, Codex, or Claude Code?
Are the helper scripts included?
What happens when a check cannot run?
Does verification fix failing code?
What precautions apply to stored evidence?
Détails du développeur
Auteur
atri10Licence
MIT
Révision Skillstore
r1
Avis de version
Lâauteur nâa dĂ©clarĂ© aucune version.
Réf
6d0b11444384184b7ae743742a7e233a9a705cd9
Récence de maintenance
06/10/2026
Utilisation
0 téléchargements · 1 vues
Structure de fichiers
đ evidence-runner-prompt.md
đ SKILL.md