/cu:read

Drain Inbox queues, load article content, and generate structured summaries.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/jdidion/claude-plugins --skill cu-read
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: /cu:read
Source: https://github.com/jdidion/claude-plugins/tree/main/plugins/curaitor/skills/cu%3Aread
Command: npx skills add https://github.com/jdidion/claude-plugins --skill cu-read

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automates deep reading sessions for Inbox articles by draining pending items, loading article content, and producing structured, study-ready summaries that support interactive discussion and decision making.

Core Features & Use Cases

  • Coordinates a multi-step reading workflow: drain the level-2 queue, load article context, fetch full content, and cache summaries for fast reuse.
  • Presents a thorough, structured summary with key findings, methods, and relevance to your work, enabling rapid decision making.
  • Supports interactive RAG-style discussion and verdict workflows (topic attachment, clipping to catalogs, or posting to teammates) without leaving the session.
  • Integrates with the Curaitor Inbox and Obsidian catalogs to keep notes, topics, and bookmarks in sync for long-term curation.

Quick Start

Start a cu:read session to process your Inbox articles and generate a structured summary for each item.

Frequently Asked Questions about /cu:read

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

FAQPage Schema
How do I automate reading and summarizing Inbox articles for my Obsidian vault?

Automate reading Inbox articles by loading full content and generating structured summaries with key findings. This Skill drains pending queues and caches study-ready notes to sync directly with your Obsidian catalogs.

What is the best way to triage saved articles and attach decisions to specific research topics?

Triage saved articles using interactive verdict workflows that allow topic attachment and clipping to catalogs. You can discuss content via RAG-style queries and post decisions to teammates without leaving the session.

Can I discuss an article's content interactively before deciding whether to keep it in my curation queue?

Discuss article content interactively using RAG-style queries during your reading session. This workflow lets you evaluate key findings and methods before assigning a final verdict to clip or discard the item.

How do I backfill structured summaries for articles already sitting in my reading queue?

Backfill summaries for queued articles by running a session that processes pending level-2 items. The workflow fetches full article content and caches structured summaries for rapid reuse and long-term curation.

Does this article triage workflow require syncing with external note-taking platforms to function?

The triage workflow integrates with Curaitor Inbox and Obsidian catalogs to keep notes and bookmarks in sync. Operating within the Curaitor cu:read context, it requires no external dependencies to process summaries.

When should I avoid using an automated curation workflow for processing research articles?

Avoid automated curation workflows when articles reside behind strict paywalls or require complex logins, as fetching full content may fail. This Skill is optimized for accessible Inbox items needing structured deep reading.