triage

Generate personalized pitches for batches of up to 10 Readwise Reader inbox items.

Updated Jun 17, 2025
One-click install
npx skills add https://github.com/nikbrunner/dots --skill triage-nikbrunner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/nikbrunner/dots/tree/main/common/.agents/skills/triage
Command: npx skills add https://github.com/nikbrunner/dots --skill triage-nikbrunner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage and pitch Readwise Reader inbox items one by one with personalized messaging to help you decide what to read and engage with.

Core Features & Use Cases

  • Automated inbox scanning: fetch the most recent documents from the Readwise Reader inbox with metadata such as title, author, category, reading_time, summary, url, site_name, published_date, and saved_at.
  • Per-document pitching: generate concise pitches tailored to your interests to support quick prioritization and decisions.
  • Structured interaction loop: present an ASCII card, a tailored pitch, and a fixed set of actions (Read, Later, Archive, Something else) with clear transitions.

Quick Start

Start triaging your Readwise inbox to generate personalized pitches for each document.

Frequently Asked Questions about triage

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

FAQPage Schema
How do I triage my Readwise Reader inbox automatically?

To triage your Readwise Reader inbox automatically, this Skill fetches recent documents in batches of up to 10 items, retrieves metadata like title and author, and generates personalized pitches to help you decide quickly. It presents an ASCII card for each document.

What is the best way to get personalized reading pitches for saved articles?

Generating personalized reading pitches for saved articles involves fetching document metadata such as summary, reading_time, and category from your inbox. This Skill then creates concise, tailored messaging for each item to support quick prioritization and engagement decisions.

How do I use MCP tools to scan and categorize my Readwise inbox?

You can use MCP tools or CLI equivalents to scan and categorize your Readwise inbox by fetching document metadata including url, site_name, and published_date. This Skill operates on batches of up to 10 items to enforce a structured interaction loop.

Can I automate Readwise inbox decisions with a fixed set of actions?

Yes, you can automate Readwise inbox decisions using a fixed set of actions: Read, Later, Archive, and Something else. After presenting an ASCII document card and a tailored pitch, this Skill handles user responses according to defined rules with clear transitions.

What metadata is needed to generate pitches for Readwise documents?

Generating pitches for Readwise documents requires metadata such as title, author, category, reading_time, summary, url, site_name, published_date, and saved_at. The Skill fetches this data automatically for batches of up to 10 inbox items to tailor the messaging.

Are there limitations on how many Readwise items I can process at once?

Processing Readwise items with this Skill is limited to batches of up to 10 items at a time. This constraint ensures a strict interaction loop where each document gets an ASCII card, a personalized pitch, and defined action transitions.