Rss Aggregator
v1.0.2自动读取配置的 RSS 链接，抓取并合并多源报道，去重历史推送，生成无 Emoji、高信息密度的 Markdown 简报。
⭐ 2· 1.3k·13 current·13 all-time
byYoogenYun@hooila
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The skill's stated purpose (fetch RSS, dedupe, produce Markdown briefs) aligns with the instructions to read rss_sources.txt and fetch articles. However the registry metadata declared no required config paths or files, while SKILL.md expects a local rss_sources.txt and a pushed_history.log for deduplication—this mismatch between declared requirements and actual runtime file access is an inconsistency.
Instruction Scope
Runtime instructions explicitly tell the agent to read rss_sources.txt, fetch and parse full web articles, and read/append pushed_history.log. They also mandate 'hide data source' (never display RSS feeds or original outlet names). Reading/writing a local history file and suppressing provenance are legitimate for brief generation but are sensitive: the skill can erase or omit source attribution and persist a local log without declaring those files. The instructions give the agent broad discretion to judge 'is_abuse=true' and to merge cross-source content—this is content-sensitive and may cause omitted provenance or untrusted merging decisions.
Install Mechanism
No install spec or code files are present; it's instruction-only so nothing is written to disk by an installer. This is lower risk from an installation standpoint.
Credentials
The skill requests no environment variables or external credentials, which is proportionate. However, it accesses local files (rss_sources.txt is present; pushed_history.log is referenced but not present in manifest) despite metadata claiming no required config paths—this undeclared file access should be made explicit.
Persistence & Privilege
always is false and the skill does not request elevated platform privileges. It does instruct writing to its own pushed_history.log (persistence limited to its own file), which is normal for incremental push functionality. There is no indication it modifies other skills or global agent configuration.
What to consider before installing
What to consider before installing:
- The skill will read rss_sources.txt and expects a pushed_history.log (for dedupe) even though the registry metadata didn't declare config files—confirm where these files will live and that you trust that location.
- The skill requires network access to fetch article pages and will parse full article content; run it in a sandbox or with limited network rights if you need containment.
- It explicitly instructs the agent to hide source attribution (never show RSS feeds or outlet names). If provenance is important for your use case (audit, credibility), this behavior is undesirable.
- The instructions give the agent discretion to judge and drop 'abusive' content and to merge multi-source reports—review sample outputs to ensure merging/omission logic meets your standards.
- Because this is instruction-only with no code, review the rss_sources.txt contents and consider creating/inspecting the pushed_history.log beforehand; add monitoring of that file so you know what has been recorded.
- If you want stronger assurance, request the skill author to: (1) declare config paths in metadata, (2) document exact file locations and formats for pushed_history.log, and (3) remove or explain the requirement to hide original sources.Like a lobster shell, security has layers — review code before you run it.
latestvk97dma5qjfcx1ad9p7ajj06czh81w52d
License
MIT-0
Free to use, modify, and redistribute. No attribution required.