lets-go

Resumes work from the active Proton Drive handoff and marks it consumed.

1|Updated Oct 29, 2025
One-click install
npx skills add https://github.com/jwh3times/holland-vip --skill lets-go-jwh3times
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lets-go
Source: https://github.com/jwh3times/holland-vip/tree/main/.agents/skills/lets-go
Command: npx skills add https://github.com/jwh3times/holland-vip --skill lets-go-jwh3times

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Picking up work on a different machine requires manually finding the handoff document, syncing the right branch, and reconstructing session context. This Skill automates that resume process by locating the active handoff in Proton Drive, reading it, marking it consumed, and aligning the local git workspace. ## Core Features & Use Cases - Handoff Discovery: Locates the single active handoff per repository via handoff_map.json in Proton Drive, using the scripts/handoff-map.mjs helper for all map reads and writes. - Dual Transport Support: Works with either the Proton Drive desktop sync client or a CLI mirror using the proton-drive command-line tool, with explicit pull and push steps for the mirror path. - Workspace Alignment: Fetches and prunes both the main and private repositories, switches to the handoff's feature branch or fast-forwards main, and warns about uncommitted, stashed, or unpushed work left on the other machine. - Use Case: You wrote a handoff on your desktop with /handoff and are now on your laptop. Run this Skill to download the handoff, clear the map so it cannot be resumed twice, check out the right branch, and get a brief on the objective and next step. ## Quick Start Resume my work by picking up the active Proton Drive handoff for this repository and continuing from its next step.

Frequently Asked Questions about lets-go

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

FAQPage Schema
How do I resume work from a handoff on another machine?▼

Run the lets-go skill, which reads handoff_map.json in Proton Drive via scripts/handoff-map.mjs, loads the active handoff document, clears the map entry, and syncs your git workspace to the branch and SHA the handoff names.

How does the skill sync handoffs without the Proton Drive desktop client?▼

It uses the proton-drive CLI in mirror mode. Set HANDOFFS_DIR to a local mirror folder, and the skill downloads the map and document before reading them, then uploads the cleared map afterward so the handoff cannot be resumed twice.

What happens if there is no active handoff for my repository?▼

The handoff-map.mjs get command reports active as null, and the skill tells you there is no active handoff for the repository key and stops without modifying the map or your workspace.

Why does the proton-drive command hang or ask me to log in?▼

Every proton-drive command needs an explicit conflict strategy flag, otherwise it prompts and hangs an agent. Output containing 'You need to login first' means the CLI session lapsed; run proton-drive auth login yourself, then retry.

Does the skill trust the handoff's description of GitHub Issues and PRs?▼

No. GitHub owns live work state, so the skill re-reads the Issues and PRs the handoff references rather than trusting their written status, then gives you a brief on the objective, current state, and next step.