executor-critique
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.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "executor-critique" from https://skillstore.io/skills/atri10-executor-critique.md and its manifest at https://skillstore.io/api/skills/atri10-executor-critique/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 "executor-critique". Audit a specification whose interface name differs from the architecture contract.
Expected outcome:
- Verdict: FAIL.
- High finding H1: The specification and architecture use different names for the same interface.
- Evidence: The audit quotes both conflicting passages and records their actual file locations.
- Proposed repair: The controller identifies the authoritative contract and routes a fix to the incorrect document.
Using "executor-critique". Re-audit a repair that removed a requirement instead of satisfying it.
Expected outcome:
- Original finding: NOT ADDRESSED.
- New high finding: The repair deleted the requirement and weakened the artifact.
- Verdict: FAIL.
- Next step: Restore the requirement and repair its cause, or escalate for an explicit human decision.
Using "executor-critique". Start an audit when a required upstream document cannot be opened.
Expected outcome:
- Verdict: BLOCKED.
- Audit file: None.
- Reason: A required upstream document is missing or unreadable.
- Next step: Supply the exact required document before dispatching the auditor again.
Security Audit
Medium RiskAll 162 static alerts are false positives: Markdown formatting, ordinary review questions, and fixed helper references. One semantic finding identifies conflicting repair-log ownership that can lose audit evidence when multiple artifact repairers are dispatched. No evidence found of malicious prompt injection or exfiltration; helper implementations are outside this package and remain unverified.
Confirmed security concerns (1)
Risk Factors
โ๏ธ External commands (50)
๐ Filesystem access (9)
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/atri10-executor-critique/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/atri10-executor-critique?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/atri10-executor-critique?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/atri10-executor-critique/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/atri10-executor-critique.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
atri10. (2026). executor-critique security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/atri10-executor-critique/audits/1BibTeX citation
@techreport{atri10-atri10-executor-critique-2026,
author = {atri10},
title = {executor-critique security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/atri10-executor-critique/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-critique 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-critique/audits/1"
identifiers:
- type: other
value: "skillstore:atri10-executor-critique:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Review Requirements Before Planning
Compare specifications with charter goals, architecture decisions, and verification criteria before authorizing implementation planning.
Detect Architecture Drift in Code
Review implementation boundaries and interface signatures against architecture and design artifacts before execution clearance.
Verify Repairs Before Release Handoff
Use a fresh reviewer to inspect repair diffs, verify finding closure, and check current-tree handoff evidence.
Try These Prompts
Audit the charter for [INITIATIVE_ID] using the charter catalog. Dispatch an independent auditor and require evidence for every finding.
Audit the specification component for [INITIATIVE_ID]. Supply its complete artifact set, charter, active architecture decisions, and verification criteria.
Repair [FINDING_IDS] in [ARTIFACT_FILE] from [AUDIT_FILE]. Preserve requirements, log evidence, and do not commit. Give each repairer a unique log.
Dispatch a fresh R03 re-auditor for [INITIATIVE_ID] and [COMPONENT]. Supply prior findings, repair logs, and the repair diff. Escalate unresolved findings to a human.
Best Practices
- Supply the complete artifact set and required upstream evidence before dispatching an auditor.
- Use separate audit, repair, and re-audit agents, with explicit ownership for every artifact and repair log.
- Verify quoted evidence, preserve unresolved findings, and run the documented helper check before reporting phase clearance.
Avoid
- Letting the controller approve its own work or accepting a repair log as proof of closure.
- Deleting requirements, weakening exact values, or granting an agent-created waiver to obtain a passing verdict.
- Dispatching several artifact repairers with exclusive ownership of the same repair log.
Frequently Asked Questions
Which AI tools does this skill target?
Does the package include its helper scripts?
What makes an audit pass?
Can a repairer change upstream contracts?
How many audit rounds are allowed?
Can multiple artifacts be repaired independently?
Developer Details
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 ยท 1 views
File structure
๐ component-auditor-prompt.md
๐ component-reauditor-prompt.md
๐ component-repairer-prompt.md
๐ SKILL.md