executor-handoff
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.
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
Review the Skillstore skill "executor-handoff" from https://skillstore.io/skills/atri10-executor-handoff.md and its manifest at https://skillstore.io/api/skills/atri10-executor-handoff/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「executor-handoff」を使用しています。 Prepare a handoff for completed work and keep the branch.
期待される結果:
- Rulings: retained the existing retry limit to satisfy the acceptance test. Cost if wrong: update the limit and test.
- Evidence: applicable checks passed on the current tree; both stores passed the credential-pattern scan.
- Git: branch preserved without merge or push. The initiative and execution records remain available.
- Lifecycle: completed-work records updated after the preservation choice.
「executor-handoff」を使用しています。 Pause an initiative with one unfinished task.
期待される結果:
- Progress: the unfinished task remains in progress, with remaining work recorded.
- Continuity: decisions, dispatch outcomes, branch state, and uncommitted files are documented in the session record.
- Lifecycle: initiative and resumable plan rows marked paused; the current phase remains entered, not passed.
- Workspace: branch and worktree preserved for the next session.
「executor-handoff」を使用しています。 Resume when the ledger disagrees with the checkout.
期待される結果:
- Discrepancy: the ledger marks a task complete, but the checkout does not contain its implementation.
- Correction: current repository evidence takes precedence over the stored completion claim.
- Next step: record the discrepancy and review binding documents before continuing implementation.
セキュリティ監査
中リスクAll 182 static findings are false positives involving Markdown syntax, fixed dependency references, ordinary Git queries, or deletion safeguards. One semantic risk remains: directory names authorize worktree removal without independent ownership evidence. No evidence found of credential exfiltration or prompt injection; referenced helper implementations are outside this audit.
確認済みのセキュリティ上の懸念 (1)
リスク要因
⚙️ 外部コマンド (50)
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/atri10-executor-handoff/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/atri10-executor-handoff?utm_source=security_passport_badge)HTMLバッジ
<a href="https://skillstore.io/skills/atri10-executor-handoff?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/atri10-executor-handoff/security.svg" alt="Skillstore security assessment" loading="lazy"></a>埋め込みカード
<iframe src="https://skillstore.io/embed/skills/atri10-executor-handoff.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-handoff security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/atri10-executor-handoff/audits/1BibTeX形式の引用
@techreport{atri10-atri10-executor-handoff-2026,
author = {atri10},
title = {executor-handoff security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/atri10-executor-handoff/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-handoff 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-handoff/audits/1"
identifiers:
- type: other
value: "skillstore:atri10-executor-handoff:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore スコア
このスコアの理由 証拠の信頼度: 中作成できるもの
Close a Verified Initiative
Review decisions and current verification evidence before choosing local integration, a pull request, or branch preservation.
Pause Unfinished Implementation
Record unfinished tasks, dispatch outcomes, rulings, and uncommitted changes so another session can continue without reconstructing decisions.
Resume an Existing Initiative
Compare initiative records with the current checkout, identify discrepancies, and establish the next valid phase before editing.
これらのプロンプトを試す
Assess whether initiative [ID] is ready for handoff. Report missing prerequisites and observed evidence. Do not merge, push, or delete anything.
Prepare handoff for initiative [ID]. Report rulings, scan both stores, and rerun applicable checks. Confirm the base branch and await my integration choice.
Pause initiative [ID]. Record unfinished tasks, rulings, dispatch outcomes, phase, and uncommitted files. Scan stores and create the session record. Preserve the workspace.
Resume initiative [ID] from ordered records. Compare Git state with recorded progress and report discrepancies. Verify worktree ownership independently. Await approval before integration or deletion.
ベストプラクティス
- Preserve observed commands and outcomes; report unavailable or unrun checks explicitly.
- Confirm integration choices and base branches with the human; verify worktree creation records and canonical paths before cleanup.
- Report credential findings by file, line, and kind without copying secret values into transcripts.
回避
- Treating earlier test results or stored completion claims as proof of the current checkout.
- Merging, pushing, force-pushing, or discarding work without the required explicit human decision.
- Deleting execution records or assuming a directory name proves permission to remove a worktree.