RSSaurus - Agent-Friendly RSS Feed Reader

**Quick judgment** A solid, narrowly focused CLI skill for interacting with RSSaurus. It’s well-aligned with agent use (simple commands, JSON and URL output) and is appropriate whenever the user explicitly wants RSSaurus-controlled RSS automation from the terminal. Its usefulness is constrained to RSSaurus users, but within that niche it appears well-designed. **Strengths & benefits** - Provides a complete loop for RSSaurus workflows: authenticate, list feeds/items, get URLs, open items, and perform read/save triage. - Machine-friendly options (`--json`, `--urls`, cursor pagination) make it easy for agents to script and chain commands. - Explicit privacy guidance (don’t print config, prefer re-auth) helps avoid leaking API tokens. - Simple, consistent subcommands (`feeds`, `items`, `read`, `unread`, `mark-read`, `save`, `unsave`, `open`, `auth`) are easy for agents to reason about. **Main risks & limitations** - **Destructive actions**: Commands like `rssaurus mark-read --all` or `--all --feed-id` can irreversibly change read state for many items; agents must avoid running them without very explicit user intent. - **Token/config exposure risk**: The CLI config can contain API tokens; any agent using this skill must strictly avoid printing or dumping config files and should request only non-sensitive error details from the user. - **Service dependency**: All operations rely on the external RSSaurus service and valid auth tokens; failures may appear as network/auth errors that agents need to handle gracefully. - **Scope limited to RSSaurus**: It’s not a general-purpose RSS reader; it’s only valuable when the user already uses RSSaurus or explicitly asks to automate it. **Recommended scenarios** - The user says they use RSSaurus and wants to **automate or script their RSS workflows** (listing unread, marking read/unread, bulk cleanup, saving items) from the CLI. - The user wants **machine-readable lists of article URLs** from their RSSaurus account, for further processing by other CLI tools or scripts. - The user reports issues with the `rssaurus` CLI (auth not working, commands failing), and needs **diagnosis or recovery** steps from an agent. - The user requests **examples or demos** of how to use RSSaurus from the command line (e.g., how to mark items read based on filters or quickly open the latest items).