papr-rss
Read, search and triage the user's Papr RSS subscriptions from the shell via the `papr` CLI. Use when the user wants to catch up on their feeds, find or summarize articles they've subscribed to, check what's unread, star/save articles, subscribe to a new feed, or pull new posts. Triggers on: "what's in my feeds", "any unread RSS", "summarize this feed", "search my subscriptions for X", "mark these read", "subscribe to <url>", "refresh my feeds".
Profile →npx skills add l0ng-ai/papr --skill papr-rss --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Papr RSS CLI `papr` is a token-efficient, agent-facing CLI over the user's local Papr RSS database. It emits [TOON](https://toonformat.dev) on stdout (≈40% cheaper than JSON, via the official `toon-format` encoder), keeps diagnostics on stderr, and returns structured errors with exit codes (0 success/no-op, 1 runtime, 2 usage). Reads are token-minimal by default; long article bodies are truncated with a `--full` escape hatch. Run `papr` with no arguments first — it prints the unread dashboard plus the most useful next commands, so you can orient without reading a manual. ## Core flow ```sh papr # home: unread/starred counts + recent unread + next steps papr feeds # subscriptions grouped by folder, with unread counts papr list --feed <id> # articles in a feed (defaults to unread; --all for read too) papr list --starred # smart views: --starred / --later / --tag <id> / --folder <id> papr list --fields author,url # add columns: author,url,snippet,type,feed_id,published papr read <id> [<id>...] # plain-text body, truncated; pass several ids to batch papr read --feed <id> --unread --limit 5 # read a feed's latest unread in one call papr read <id> --full # the complete body when trunca
- Core flow
- Triage & subscriptions
- Management (mirrors the desktop app)
- Sync
- Notes
papr # home: unread/starred counts + recent unread + next steps papr feeds # subscriptions grouped by folder, with unread counts papr list --feed <id> # articles in a feed (defaults to unread; --all for read too) papr list --starred # smart views: --starred / --later / --tag <id> / --folder <id> papr list --fields author,url # add columns: author,url,snippet,type,feed_id,published papr read <id> [<id>...] # plain-text body, truncated; pass several ids to batch papr read --feed <id> --unread --limit 5 # read a feed's latest unread in one call papr read <id> --full # the complete body when truncation hid something papr search "<query>" # FTS5 full-text search across every article papr mark read <id> [<id>...] # state: read|unread|star|unstar|later|unlater (idempotent)
What does the papr-rss skill do?
Read, search and triage the user's Papr RSS subscriptions from the shell via the `papr` CLI. Use when the user wants to catch up on their feeds, find or summarize articles they've subscribed to, check what's unread, star/save articles, subscribe to a new feed, or pull new posts. Triggers on: "what's in my feeds", "any unread RSS", "summarize this feed", "search my subscriptions for X", "mark these read", "subscribe to <url>", "refresh my feeds".
How do I install it?
Run `npx skills add l0ng-ai/papr --skill papr-rss --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From l0ng-ai/papr, a repository with 494 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.