2k Downloads
Overview
Query headlines, feeds, and categories from a self-hosted FreshRSS instance via its Google Reader–compatible API, with filters for time range, category, unread status, and count.
Key Advantages
1.Direct integration with a self-hosted FreshRSS instance, keeping news aggregation fully under user control.
2.Simple, focused command interface (`headlines`, `categories`, `feeds`) suitable for automation and scripted workflows.
3.Useful filtering options (by category, unread status, and recent hours) to narrow results to relevant items.
4.Environment-variable-based configuration (URL, username, API password) that fits typical server/CLI deployment patterns.
5.Output format includes date, source, title, URL, and categories, which is easy to parse or present back to the user.
Use Cases
- Answering user requests like “show my latest RSS headlines” or “what’s new in my Technology feeds from the last 2 hours?” using the user’s FreshRSS instance.
- Building a personal news assistant that can surface unread items from specified categories on demand.
- Listing available categories or feeds to help users discover or refine what they want to read through conversational queries.
- Automating periodic checks for new headlines in certain categories (e.g., Security, DevOps) and summarizing them in a chat session.
- Providing a unified “inbox” view of fresh items from multiple RSS sources configured in FreshRSS without logging into the web UI.
Evaluation Scores
7.6
/ 10
Reliability
7.0
Functionality
7.0
Usability
7.4
Safety
8.8
Performance
8.5
Compatibility
7.5
Based on 1 evaluation · Latest: 3/19/2026
Download Trend
Loading...
Evaluation History (1)
7.6/103/19/2026▼
OS: win32-x64LLM: arcee-ai/trinity-large-preview
**Judgement:** A focused, solid skill for users who already run a self-hosted FreshRSS instance and want to query their feeds (headlines, categories, feeds) from OpenClaw. It’s read-only, relatively simple, and likely to perform well, but depends entirely on the external FreshRSS service and correct environment configuration.
**What it does well**
- Pulls latest headlines with useful filters: by category, unread status, and recent time window (`--hours`).
- Lists categories and feeds, enabling richer “browse my RSS” style interactions.
- Uses a straightforward CLI script (`freshrss.sh`) that should be easy to wrap with tool calls.
- Output format (date, source, title, URL, categories) is practical for both display and downstream processing.
**Limitations / Risks**
- Requires a properly configured, reachable FreshRSS instance with the Google Reader–compatible API and API password set; any misconfiguration or downtime will break the skill.
- Only supports a limited set of operations (no marking items as read, no full-text search, no complex filtering beyond category/unread/time).
- Category names are case-sensitive and must match FreshRSS exactly, which can lead to user-facing errors if not handled carefully.
- Credentials (URL, username, API password) live in environment variables; this is standard but still requires secure deployment to avoid accidental exposure.
- All content is as private as the FreshRSS instance itself; if the OpenClaw environment exposes logs or transcripts broadly, sensitive RSS items could be indirectly exposed.
**Best-fit scenarios**
- Users who already self-host FreshRSS and explicitly want their personal RSS headlines available via an assistant.
- Chat-based “personal news reader” flows: “Show me unread headlines from my ‘Technology’ category in the last 4 hours, up to 10 items.”
- Lightweight dashboards or daily briefings built from a user’s existing RSS configuration.
**Less suitable for**
- Users without a FreshRSS instance or without access to its API settings.
- Workflows that need to modify feed state (e.g., marking as read, starring items) or perform complex search/filtering beyond what the script exposes.
Comments (0)
No comments yet. Be the first!