スキル executor-critique

📦

executor-critique

Name: executor-critique
Author: atri10

コンテンツリビジョン r1 中リスク ⚙️ 外部コマンド📁 ファイルシステムへのアクセス

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.

対応: Claude Codex Code(CC)

📊 69 十分

Maintain this Skill? Claim it 📊 69 十分

自分のエージェントでインストール

このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。

エージェントリクエスト

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.

エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。

エージェントが読めるリソース

AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。

Markdown詳細 GET /skills/atri10-executor-critique.md 署名済み manifest GET /api/skills/atri10-executor-critique/manifest 署名済み lockfile GET /api/skills/atri10-executor-critique/lockfile

テストする

「executor-critique」を使用しています。 Audit a specification whose interface name differs from the architecture contract.

期待される結果:

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.

「executor-critique」を使用しています。 Re-audit a repair that removed a requirement instead of satisfying it.

期待される結果:

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.

「executor-critique」を使用しています。 Start an audit when a required upstream document cannot be opened.

期待される結果:

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.

セキュリティ監査

中リスク

v1 • 2026/10/5 バージョン別レポートを開く

All 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.

スキャンされたファイル

1,221

解析済み行数

レビュー項目

誤検知を無視

確認済みのセキュリティ上の懸念 (1)

中

component-repairer-prompt.md:3-4 component-repairer-prompt.md:13-18 component-repairer-prompt.md:65-72 component-repairer-prompt.md:316-320

Conflicting Ownership of a Shared Repair Log

The template dispatches one repairer per artifact but derives the repair log only from component and round. Each repairer receives exclusive ownership and whole-file rewrite instructions, risking lost evidence or blocked repairs when several artifacts need fixes.

The same component-round log is described as exclusively owned by each artifact repairer, with no locking or aggregation protocol. Helper behavior is unverified, so actual concurrent overwrites are not demonstrated.

リスク要因

⚙️ 外部コマンド (50)

📁 ファイルシステムへのアクセス (9)

SKILL.md:78 SKILL.md:79 SKILL.md:80 SKILL.md:81 SKILL.md:82 SKILL.md:83 SKILL.md:84 SKILL.md:126 SKILL.md:255

監査者: codex

このレポートを共有・引用

バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。

バージョン別レポートを開く

レポートリンクをコピー

https://skillstore.io/skills/atri10-executor-critique/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdownバッジ

[![Skillstore security assessment](https://skillstore.io/badges/skills/atri10-executor-critique/security.svg)](https://skillstore.io/skills/atri10-executor-critique?utm_source=security_passport_badge)

HTMLバッジ

<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>

埋め込みカード

<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>

学術引用 (APA · BibTeX · CFF)

APA形式の引用

atri10. (2026). executor-critique security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/atri10-executor-critique/audits/1

BibTeX形式の引用

@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 スコア

このスコアの理由証拠の信頼度: 中

アーキテクチャ

保守性

コンテンツ

コミュニティ

仕様準拠

作成できるもの

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.

これらのプロンプトを試す

Audit a Charter

Audit the charter for [INITIATIVE_ID] using the charter catalog. Dispatch an independent auditor and require evidence for every finding.

Compare Specifications with Upstream Decisions

Audit the specification component for [INITIATIVE_ID]. Supply its complete artifact set, charter, active architecture decisions, and verification criteria.

Repair Assigned Findings

Repair [FINDING_IDS] in [ARTIFACT_FILE] from [AUDIT_FILE]. Preserve requirements, log evidence, and do not commit. Give each repairer a unique log.

Re-Audit the Final Round

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.

ベストプラクティス

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.

回避

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.

よくある質問

Which AI tools does this skill target?

The package targets Claude, Codex, and Claude Code. Execution requires an environment with agent dispatch support and the related Executor helpers.

Does the package include its helper scripts?

No. It contains the skill document and three prompt templates. Helper implementations are referenced but are not included here.

What makes an audit pass?

The documented contract requires zero HIGH and zero MEDIUM findings. The referenced helper checks reported verdicts against counts and supporting records.

Can a repairer change upstream contracts?

No. Upstream contract findings belong to the controller, which must amend the source through an initiative ruling.

How many audit rounds are allowed?

The workflow allows R01 through R03. Unresolved findings after R03 go to a human rather than another repair round.

Can multiple artifacts be repaired independently?

The template assigns one repairer per artifact. Define separate repair logs or a designated log writer to prevent conflicting ownership.