process-inbox

Guide users through clarifying inbox items into actions, projects, or references.

2|Updated Oct 30, 2025
One-click install
npx skills add https://github.com/elinsky/execution-system-skills --skill process-inbox-elinsky
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: process-inbox
Source: https://github.com/elinsky/execution-system-skills/tree/main/process-inbox
Command: npx skills add https://github.com/elinsky/execution-system-skills --skill process-inbox-elinsky

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Processing an inbox is often overwhelming: items are vague, multi-part, or get repeatedly deferred. This Skill turns inbox clutter into a clear, organized system by coaching users through clarifying each item, deciding the next physical action, routing it to the correct horizon (00k–50k), and removing it from the inbox so nothing returns.

Core Features & Use Cases

  • Guided, one-item-at-a-time coaching that enforces "top item first" and "never back to inbox" rules to prevent cherry-picking.
  • Adaptive clarification questions and routing logic to decide between next actions (00k), projects (10k), areas/goals/vision (20k–50k), reference, trash, or someday/maybe.
  • Integrated MCP tool usage patterns: add_action, create_project, add_to_waiting, add_to_deferred, add_to_incubating, search_projects, and list_areas to perform deterministic edits to the user's execution-system repository.
  • Session management and error handling guidance so the skill can pause, resume, and recover from tool failures while keeping the user informed.

Quick Start

Say "Process inbox" and the assistant will read your inbox file, guide you through clarifying the top item, take the appropriate MCP actions, and delete the processed line until the inbox is empty.

Frequently Asked Questions about process-inbox

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

FAQPage Schema
How do I process my GTD inbox to reach inbox zero?

GTD inbox processing works by reading a central inbox file, coaching you one item at a time to clarify each entry, routing it to the correct 00k–50k horizon via MCP tools, and deleting the processed line to reach inbox zero.

How does clarify-and-organize workflow handle vague inbox items?

The clarify-and-organize workflow enforces a top-item-first rule and asks adaptive clarification questions to transform vague inbox items into routed next actions, projects, or reference entries, preventing items from being repeatedly deferred.

What MCP tools do I need to organize tasks into GTD horizons?

Organizing tasks into GTD horizons requires MCP tools such as add_action, create_project, add_to_waiting, add_to_deferred, add_to_incubating, search_projects, and list_areas to route items across 00k–50k levels.

Can I pause and resume inbox processing if an MCP tool fails?

Yes, you can pause and resume inbox processing because the skill includes session management and error handling guidance to recover from MCP tool failures while keeping the user informed of the current progress.

What is the best way to stop cherry-picking easy tasks during inbox processing?

The best way to stop cherry-picking during inbox processing is using a guided workflow that enforces a top-item-first rule and a never-back-to-inbox policy, forcing you to clarify and route the current top item before moving down the list.

Do I need a specific file format to use GTD inbox processing with MCP?

You need a central inbox file that the skill can read and edit, allowing it to process lines sequentially, invoke MCP tools to route the contents, and delete processed lines to achieve an empty state.