skills.rest
hve4638
hve4638COMMUNITY
Explore all skills by this author →
GitHub

pickup

Load prior handoff context from .agent-memory/handoff and archive it after successful load.

Updated Mar 1, 2026
Search Tags:#automation#workflow#context#handoff#archive#session#load
One-click install
npx skills add https://github.com/hve4638/hve-cc-marketplace --skill pickup-hve4638
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pickup
Source: https://github.com/hve4638/hve-cc-marketplace/tree/main/common/skills/pickup
Command: npx skills add https://github.com/hve4638/hve-cc-marketplace --skill pickup-hve4638

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Read context from a previous handoff and resume it in the current session. After picking up, briefly summarize the loaded content and avoid starting new work immediately.

Core Features & Use Cases

  • Scans the direct subfolders of .agent-memory/handoff/, excluding the _archive/ directory, and sorts by folder name to determine recency.
  • Handles 0, 1, or multiple candidates: for 0, reports nothing to pick up; for 1, loads immediately; for 2+, presents newest-first and prompts the user.
  • Loads by first reading the selected folder's INDEX.md, then traversing the documented NN-*.md flow to establish the working base for the session.
  • Archives the loaded folder to .agent-memory/handoff/_archive/ after a successful load, creating the archive directory if missing and ensuring atomicity.
  • Keeps archived handoffs separate from active candidates unless explicitly referenced.

Quick Start

Load the most recent handoff context from .agent-memory/handoff and archive it after a successful load.

Frequently Asked Questions about pickup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resume a previous agent session from a handoff context?▼

To resume a previous agent session, this Skill scans the .agent-memory/handoff/ directory, identifies the most recent handoff folder, and loads its context by reading INDEX.md and traversing documented NN-*.md dependencies to establish the working base.

What happens when multiple handoff context folders exist for session resumption?▼

When multiple handoff folders exist, the Skill sorts them newest-first, presents the candidates, and prompts the user to choose which context to load, ensuring you resume the correct workflow session.

How do I archive a loaded handoff context to keep active candidates separate?▼

After a successful handoff context load, the Skill automatically archives the folder to .agent-memory/handoff/_archive/, creating the directory if missing, and ensures the operation is atomic and isolated from failures.

Can I load handoff context automatically when only one session candidate exists?▼

Yes, when only one handoff folder candidate is found in the .agent-memory/handoff/ directory, the Skill loads it immediately without prompting the user, streamlining the session resumption process.

What does the agent report when there are zero handoff folders to pick up?▼

When there are zero handoff folder candidates in the .agent-memory/handoff/ directory, the Skill reports that there is nothing to pick up, preventing unnecessary workflow interruption.

Do I need to manually follow NN-*.md dependencies when loading session context?▼

No, the Skill automatically traverses the documented NN-*.md dependencies after reading INDEX.md, forming the complete working base for the session without manual dependency resolution.

Related Skills

Explore More Software Engineering Skills→
hve4638hve4638

handoff

Enumerate session tasks and save timestamped handoff documents to .agent-memory/handoff/.

Community
Advanced
AO-Cyber-SystemsAO-Cyber-Systems

df:resume-work

Restore project context from STATE.md and resume previous work.

Official
Advanced
bradygasterbradygaster
3.1k

nap

Compress agent histories and archive stale decisions in session state files.

Community
Basic
MihaiOnSoftwareMihaiOnSoftware
1

load-rules

Load user rules from ~/.ai/rules/ in defined order.

Community
Basic