Readwise skills
Readwise skills help agents triage a reading inbox, discuss books and connect highlights across saved sources
- 328 ★ on the repository
- Last commit
Extended access
Why this level
- The agent reads personal Readwise material and some workflows change article state.
- A reading-interest profile is saved to a local file.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/readwise-skillsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The agent reads personal Readwise material and some workflows change article state.
- A reading-interest profile is saved to a local file.
This is third-party code. Review the repository files before installing.
What it does
Readwise skills teaches an agent to work with a personal Readwise and Reader library. It supports one-at-a-time article triage, feed catch-up in batches and discussion of recent reading. A book review workflow builds on highlights and connects the book to other sources. The collection also includes quizzes and an interactive graph of ideas. Personalized suggestions use a reading profile saved in a separate file and shared across skills.
Who it is for. For readers who keep articles and highlights in Readwise and want to discuss them with their agent.
Good fit when
- Triage saved articles against personal interests
- Recall ideas from recent reading
- Draft a book review from your highlights
- Explore connections across sources
Not a fit when
- You have no Readwise library or access
- You need a standalone reading application
- You cannot share personal notes with the agent
Example request
Triage my new Reader articles one at a time and explain their relevance to my current research.Limitations
Before use, connect either Readwise MCP or the CLI; the skills supply instructions and do not replace service access. Tool calls use your personal library, exposing the selected articles and highlights to the agent. Personalization depends on a separate reader-profile file that needs creation and maintenance. Some workflows change Reader item state, such as marking feed items seen, so request read-only behavior when first trying the collection.
How to disable. Remove Readwise skills from the agent directory. Revoke the MCP or CLI connection separately if it is no longer needed.
FAQ
Do I need both MCP and CLI?
No. Either Readwise connection method is sufficient.
How do I start personalization?
Run `build-persona` to create `reader_persona.md`.
Does triage stop without a profile?
No. It proceeds with less personalized recommendations.
Can it draft a current-reading page?
Yes. The collection includes `now-reading-page`.
Is Claude Cowork supported?
Yes. Add the repository through Cowork’s plugin marketplace settings.
Discussion
No questions or reviews yet.
Related
SkillsA reading advisor for agents on top of WeRead: picks from shelf and notes, learning paths, note digests and year reviews.
A collection of skills for decisions and projects: strategy, market research, thinking, data analysis, docs and slides.
A skill that cross-examines a plan before work starts: numbered questions in rounds with a recommended answer and no changes until you confirm
cafe3310's personal skill collection: spec-driven project work, reviews, reports, browser, 3D and video in one repository
A personal set of six skills: goal briefs for an agent, disk cleanup, AI news digests, project tidy-up, deep research and long-form writing
A skill that guides a researcher into a new field by rungs: motivation, vocabulary, methods, frontier, no unverified references
README in short
Skill installation is separate from service connection. The Claude Code plugin can install both MCP and skills together.
README badge
Original SKILL.md
---
name: triage
description: Triage Reader inbox one doc at a time with personalized pitches
---
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.}
Let's start with the most recent thing in your inbox:
· · ·
## Triage Loop
Present documents **one at a time**, starting from the most recently saved. For each document, use this exact format:
### Document Card
Render an ASCII box in a code block. Pad all lines to the same width so the right `│` border aligns. Use this structure:
```
┌──────────────────────────────────────────────────┐
│ {Title — wrap to multiple lines if needed} │