inbox

Verify fingerprints and present incoming handoffs for acceptance.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/jdidion/claude-plugins --skill inbox-jdidion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: inbox
Source: https://github.com/jdidion/claude-plugins/tree/main/plugins/handoff/skills/inbox
Command: npx skills add https://github.com/jdidion/claude-plugins --skill inbox-jdidion

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Check incoming handoffs for the active session, verify their fingerprints, and present them for acceptance.

Core Features & Use Cases

  • Verify handoff fingerprints before presenting content to avoid tampered handoffs
  • List, view, and read handoffs, including status (pod vs legacy) and whether already seen
  • Archive accepted or cleared handoffs to maintain an audit trail and idempotency

Quick Start

Run /handoff:inbox to view pending handoffs and begin processing.

Frequently Asked Questions about inbox

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

FAQPage Schema
How do I securely process incoming handoffs and verify their fingerprints?

Secure handoff processing verifies fingerprints before presenting content to prevent accepting tampered handoffs. It identifies valid pod envelopes or legacy files for the active session, tracks seen status idempotently, and archives accepted items.

What is the best way to manage workflow handoffs and maintain an audit trail?

Managing workflow handoffs securely involves archiving accepted or cleared items to maintain an audit trail and ensure idempotent seen-tracking. It processes valid pod envelopes or legacy files for the active session and archives completed items.

How do I check if a pod envelope handoff has already been seen?

Checking if a pod envelope handoff has been seen relies on idempotent seen-tracking. The system lists handoffs with their status, indicating whether a valid incoming pod envelope or legacy file has already been viewed in the active session.

Does fingerprint verification work with legacy files or only pod envelopes?

Fingerprint verification works with both pod envelopes and legacy files. The system applies fingerprint verification when handoffs arrive in either format, ensuring secure validation before presenting content for acceptance in the active session.

Why does my handoff inbox show tampered content before acceptance?

Your handoff inbox may show tampered content if fingerprint verification fails or is bypassed. Secure processing enforces fingerprint verification before presenting valid handoffs, preventing tampered items from reaching the acceptance stage.