EXAMPLE - Workflow for processing large Things3 inboxes using LLM-driven confidence matching and intelligent automation...
NOTE: This is an example skill showing how to build an inbox processing workflow. The actual inbox-processing skill is gitignored as it contains personal workflow patterns. Copy this to .claude/skills/inbox-processing/ and customize for your needs.
Process large Things3 inboxes (100+ items) efficiently through batch analysis, confidence-based automation, and intelligent user interaction.
Prerequisites:
things3-productivity skill for MCP tool patternsprivate-prefs/personal-taxonomy.json with your work areas and tagstemp/inbox-processing/ folder for session stateWhen to use: Inbox has 100+ items requiring organization.
The skill uses LLM-driven analysis with context from personal-taxonomy.json:
Step 1: Setup Session
Create temp/inbox-processing/ with tracking files:
session.md # Batch progress, statistics
match_results.json # Decisions with confidence scores
pending_decisions.json # Items awaiting approval
high_confidence_actions.json # Auto-apply candidates (≥90%)
execution_log.md # Complete action history
Step 2: Load Inbox Batch
# First batch: 50 items, subsequent: 50-100 items
read_tasks(when="inbox", limit=50, include_notes=True)
Step 3: Load System Inventory Cache once per session:
list_areas() # All areas with IDs and tags
list_projects() # All projects with metadata
list_tags() # All tags including hierarchy
Step 4: Analyze Each Item For each inbox item, determine:
Confidence Levels:
Step 5: Present High-Confidence Batch Group by action type:
### Area: Work (25 items, 90-100% confidence)
Auto-assign these 25 items to area="Work"?
- "Work: Fix login bug" (100%)
- "Dashboard review" (95%)
...
[Approve] [Review individually] [Skip]
Step 6: Handle Medium-Confidence Items Present individually for 80-89% confidence:
1. "Design review notes" (85%) → area="Work"?
Notes: Contains work-related keywords
[Yes] [No] [Different area]
Step 7: Execute Approved Actions Batch operations by type:
# Set areas
edit_task(task_uuid="...", area="Work")
# Add tags
add_tags(task_uuids=[...], tags=["urgent"])
# Create projects
create_project(name="Q4 Roadmap", area="Work")
Step 8: Handle Reference Items Items with notes but no actionable task:
# Suggest migration to Notion
migrate_inbox_to_notion(block_id="your-block-id")
Step 9: Update Statistics
Track in session.md:
Batch 1: 50 items processed
- 25 auto-assigned to areas
- 10 tagged
- 5 moved to projects
- 10 pending review
Remaining: 96 items
Step 10: Next Batch If inbox > 0, repeat from Step 2 with larger batch size (up to 100).
The skill improves through use:
### High Confidence (90-100%)
"Work: Fix dashboard bug" → area="Work"
- Explicit area mention (100%)
- Work tag keyword present
- Matches existing area pattern
### Medium Confidence (80-89%)
"Review team notes" → area="Work"?
- Work context implied (85%)
- No explicit area mention
- Could be personal or work
### Low Confidence (<80%)
"Call mom" → ???
- No clear work/personal indicators
- No matching patterns
- Requires manual classification
To create your own inbox processing skill:
Copy this example:
cp -r .claude/skills/inbox-processing.example .claude/skills/inbox-processing
Update references:
Configure personal-taxonomy.json:
{
"things3": {
"work_classification": {
"work_tag": "YOUR_WORK_TAG",
"work_areas": ["Your Work Area"]
}
}
}
Test with small batches:
list_projects=True to avoid creating duplicates