スキル executor-initiative
📦
executor-initiative
コンテンツリビジョン r1 高リスク ⚙️ 外部コマンド📁 ファイルシステムへのアクセス
Manage Initiative Intake and Lifecycle
Unclear scope and missing approval records make project decisions difficult to track. This skill guides request classification, charter writing, and lifecycle documentation through Executor.
対応: Claude Codex Code(CC)
インストール前に停止して確認を求めてください。
計画を確認し、ファイルを変更する前にユーザーの明示的な同意を得てください。
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
エージェントリクエスト
Review the Skillstore skill "executor-initiative" from https://skillstore.io/skills/atri10-executor-initiative.md and its manifest at https://skillstore.io/api/skills/atri10-executor-initiative/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「executor-initiative」を使用しています。 Can the admin dashboard share the existing server process?
期待される結果:
- Classification: Spike.
- Deliverable: A feasibility recommendation, not retained implementation code.
- Next step: Present the proposed investigation and wait for approval.
- Initiative allocation: Not required.
「executor-initiative」を使用しています。 Tenant bulk imports repeatedly degrade other tenants. Prepare a charter for an isolation initiative.
期待される結果:
- Classification: Architectural initiative.
- Problem: One tenant can degrade service for other tenants.
- Proposed criterion: Tenant API p99 remains below an agreed threshold during the bulk import fixture.
- Non-goal: Cross-region failover.
- Approval status: Pending confirmation of the problem statement and measurable criteria.
「executor-initiative」を使用しています。 Add multi-region failover to an initiative approved only for tenant isolation.
期待される結果:
- Recommendation: Create a separate initiative.
- Reason: Recovery-time requirements add success criteria beyond the approved isolation scope.
- Relationship: Document a dependency only if the new work genuinely depends on the existing initiative.
- Existing charter: Preserve its approved scope.
セキュリティ監査
高リスクv1 • 2026/10/5 バージョン別レポートを開く
All 168 static alerts are false positives for their reported patterns: Markdown delimiters, sibling references, a registry lock, and routine workflow operations. Two semantic risks remain: documented unlocked transitions can lose updates, and the verification checklist can record intake approval before charter presentation. No evidence found of malware, exfiltration, or audit-directed prompt injection; referenced dependency scripts were unavailable for review.
2
スキャンされたファイル
706
解析済み行数
0
レビュー項目
0
誤検知を無視
確認済みのセキュリティ上の懸念 (2)
高
Verification Checklist Can Record Unapproved Intake
The checklist says to run checks when presenting the charter, including a state-changing intake-pass command. This can record approval before the required human decision.
The checklist directly requests a pass during presentation, while the intake gate requires prior approval. Documented artifact checks do not establish human authorization.
中
Concurrent Transitions Can Lose Lifecycle Records
The skill states that phase and status updates lack locking and can lose updates in shared indexes. Prose serialization rules do not coordinate independent agents.
The source explicitly documents unlocked writes and lost updates. The dependency implementation was unavailable, so this finding concerns the documented workflow risk.
リスク要因
⚙️ 外部コマンド (50)
references/intake-examples.md:82-112 references/intake-examples.md:112-123 references/intake-examples.md:123 references/intake-examples.md:124 references/intake-examples.md:126-127 references/intake-examples.md:127-135 references/intake-examples.md:135-136 references/intake-examples.md:136-150 references/intake-examples.md:150-152 SKILL.md:13 SKILL.md:14 SKILL.md:32 SKILL.md:60-69 SKILL.md:69-90 SKILL.md:90-93 SKILL.md:93-95 SKILL.md:95-99 SKILL.md:99 SKILL.md:100-101 SKILL.md:101 SKILL.md:102 SKILL.md:103 SKILL.md:105-107 SKILL.md:107-111 SKILL.md:111-113 SKILL.md:113 SKILL.md:115 SKILL.md:116-119 SKILL.md:119 SKILL.md:120-121 SKILL.md:121-123 SKILL.md:123 SKILL.md:129-130 SKILL.md:130 SKILL.md:132-134 SKILL.md:134-137 SKILL.md:137-147 SKILL.md:147-151 SKILL.md:151-152 SKILL.md:152 SKILL.md:153-154 SKILL.md:154 SKILL.md:155-161 SKILL.md:161-164 SKILL.md:165-167 SKILL.md:167 SKILL.md:168 SKILL.md:169-170 SKILL.md:170 SKILL.md:171-173
📁 ファイルシステムへのアクセス (11)
監査者: codex
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/atri10-executor-initiative/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/atri10-executor-initiative?utm_source=security_passport_badge)HTMLバッジ
<a href="https://skillstore.io/skills/atri10-executor-initiative?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/atri10-executor-initiative/security.svg" alt="Skillstore security assessment" loading="lazy"></a>埋め込みカード
<iframe src="https://skillstore.io/embed/skills/atri10-executor-initiative.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-initiative security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/atri10-executor-initiative/audits/1BibTeX形式の引用
@techreport{atri10-atri10-executor-initiative-2026,
author = {atri10},
title = {executor-initiative security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/atri10-executor-initiative/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-initiative 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-initiative/audits/1"
identifiers:
- type: other
value: "skillstore:atri10-executor-initiative:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore スコア
このスコアの理由 証拠の信頼度: 中 41
アーキテクチャ
85
保守性
87
コンテンツ
65
コミュニティ
78
仕様準拠
作成できるもの
Classify an Incoming Engineering Request
Determine whether a request needs a feasibility answer, a bounded change, or a documented architectural initiative.
Prepare a Charter for Approval
Translate an architectural request into measurable outcomes, explicit scope boundaries, and named approval responsibilities.
Maintain Initiative Lifecycle Records
Document approved transitions, pauses, replacements, and closure while keeping the registry and initiative index consistent.
これらのプロンプトを試す
Classify a Request
Classify this request: [request]. Explain whether it is a spike, bounded change, or architectural initiative. Do not change files.
Draft an Initiative Charter
Draft a charter for [initiative] with measurable criteria, non-goals, allowed paths, and [approver]. Present it for approval without recording a gate pass.
Evaluate Existing Initiative Scope
Compare [request] with the approved charter for [initiative ID]. Recommend attachment or separate allocation without widening approved scope or changing records.
Apply an Approved Lifecycle Transition
After confirming [approval evidence], record [transition] for [initiative ID]. Serialize updates, document skipped phases, verify both indexes, and preserve prior records.
ベストプラクティス
- Confirm dependency availability and inspect referenced scripts before authorizing execution.
- Obtain explicit approval before recording any gate pass; treat pre-presentation verification as read-only.
- Serialize lifecycle updates, verify both indexes, and redact secret values from tracked documents.
回避
- Create initiatives for questions or bounded changes without a lasting architectural deliverable.
- Widen an approved charter or mark a gate passed without a new human decision.
- Run concurrent phase updates, delete historical records, or copy example identifiers and timestamps.
よくある質問
Which AI tools can use this skill?
The report lists Claude, Codex, and Claude Code. Full operation also requires repository access and the referenced Executor dependencies.
Does every request need an initiative?
No. Feasibility spikes and most bounded changes do not. Architectural work receives an initiative or attaches to an existing approved scope.
Can this skill implement the project?
No. It coordinates intake and lifecycle records. Other Executor skills handle specifications, planning, execution, verification, and handoff.
Are the required scripts included?
No. The reviewed package contains instructions and examples. It references scripts and contract documents in a sibling Executor skill.
Does a successful command prove human approval?
No. Explicit human approval is required. The pre-presentation verification checklist should not run a state-changing intake-pass command.
Can multiple agents update phases simultaneously?
Not safely under the documented workflow. Phase and status changes lack locking, so serialize transitions and verify the resulting indexes.
開発者情報
作成者
atri10ライセンス
MIT
Skillstore リビジョン
r1
バージョンに関する注意
作者はバージョンを宣言していません。
参照
6d0b11444384184b7ae743742a7e233a9a705cd9
メンテナンスの新しさ
2026/10/6
利用状況
0 ダウンロード · 0 閲覧
ファイル構成