Skills executor-handoff
๐Ÿ“ฆ

executor-handoff

Content revision r1 Medium Risk โš™๏ธ External commands๐Ÿ“ Filesystem access

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.

Supports: Claude Codex Code(CC)
๐Ÿ“Š 69 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
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.

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-handoff". Prepare a handoff for completed work and keep the branch.

Expected outcome:

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

Using "executor-handoff". Pause an initiative with one unfinished task.

Expected outcome:

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

Using "executor-handoff". Resume when the ledger disagrees with the checkout.

Expected outcome:

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

Security Audit

Medium Risk
v1 โ€ข 10/5/2026 Open versioned report

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
Files scanned
642
Lines analyzed
0
Review items
0
False positives ignored

Confirmed security concerns (1)

Medium
Directory Names Substitute for Worktree Ownership
The rule says: "If `WORKTREE_PATH` is under `.worktrees/` or `worktrees/`: we own it." It then authorizes removal without checking a creation record or requesting separate cleanup approval. Host-managed worktrees can use these directory names, so choosing local integration can remove a workspace that the agent does not own. Git refusal handling limits deletion of modified files but does not establish ownership.
The ownership rule directly precedes worktree removal and is repeated in the cleanup checklist. Confidence is high, although unauthorized removal depends on host directory conventions.
Audited by: codex
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.

Open versioned report
Security Assessment

Copy report link

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

Markdown badge

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

HTML badge

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

Embed card

<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>
Academic citations (APA ยท BibTeX ยท CFF)

APA citation

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

BibTeX citation

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

Why this score Evidence Confidence: Medium
55
Architecture
85
Maintainability
87
Content
65
Community
78
Spec Compliance

What You Can Build

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.

Try These Prompts

Check Handoff Readiness
Assess whether initiative [ID] is ready for handoff. Report missing prerequisites and observed evidence. Do not merge, push, or delete anything.
Prepare Integration Choices
Prepare handoff for initiative [ID]. Report rulings, scan both stores, and rerun applicable checks. Confirm the base branch and await my integration choice.
Pause a Partial Initiative
Pause initiative [ID]. Record unfinished tasks, rulings, dispatch outcomes, phase, and uncommitted files. Scan stores and create the session record. Preserve the workspace.
Reconcile and Resume
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.

Best Practices

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

Avoid

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

Frequently Asked Questions

Does this package include the Executor helper scripts?
No. The reviewed package contains SKILL.md only and references helpers from a sibling Executor installation.
Does the skill merge or push automatically?
The workflow requires the human to choose an integration option before its merge or push steps begin.
Can unfinished work be handed to another session?
Yes. The pause protocol records progress, rulings, dispatch outcomes, Git state, and continuation details without marking unfinished work complete.
Does a clean secret scan guarantee that no credentials exist?
No. The documented scan detects credential-shaped content. Its implementation was not included in the reviewed package.
Are execution records deleted after completion?
The workflow preserves initiative folders, execution workspaces, and registry rows. Store pruning remains a separate human decision.
How are host-managed worktrees protected?
The workflow preserves worktrees outside designated directories but assumes ownership inside them. Verify creation records before cleanup, including worktrees inside those directories.

Developer Details

Author

atri10

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Ref

6d0b11444384184b7ae743742a7e233a9a705cd9

Maintenance freshness

10/6/2026

Usage

0 downloads ยท 0 views

File structure

๐Ÿ“„ SKILL.md

More from atri10

View all
View all