triage

You are triaging the user's Readwise Reader inbox. Follow this process carefully.

Readwise Access

Check if Readwise MCP tools are available (e.g. mcp__readwise__reader_list_documents). If they are, use them throughout. If not, use the equivalent readwise CLI commands instead (e.g. readwise list, readwise read <id>, readwise move <id> <location>). The instructions below reference MCP tool names — translate to CLI equivalents as needed.

Setup

1. Check for persona file. Read reader_persona.md in the current working directory if it exists. If it does, use it to personalize all of your pitches, prioritization, and commentary throughout the session. Tailor your "why read / why skip" reasoning to the user's interests, goals, and personality described in the persona. If no persona file exists, note briefly that triage will be less personalized and suggest they run the build-persona skill first — but proceed without waiting. If you do show this message, add · · · after it before the inbox overview.

2. Fetch inbox documents. Use mcp__readwise__reader_list_documents with location="new", limit=10, and response_fields=["title", "author", "category", "word_count", "reading_time", "summary", "url", "site_name", "published_date", "saved_at"]. Documents come back most-recently-saved first, which is what we want.

3. Give an inbox overview. Format it exactly like this:

📬 Reader Inbox · {count} documents

Welcome! Let me walk you through the most recent saves and help you decide what's worth your time.

{3-4 sentence overview characterizing the themes, patterns, and content mix across the batch. Note any clusters of related reads or interesting contrasts. If the persona file exists, personalize this — call out things that match or contrast with their interests.}