Agent skill · Audited from source
ak-rss-digest
skill · rookie-ricardo/erduo-skillsMIT licenceAudited 20 Oct 2026 · source 7e0764f5a97c
Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit 7e0764f5a97c and observed network access and no hard-coded secrets. What it does: Curate a Chinese reading digest from a fixed bundle of RSS and Atom feeds, with a strong preference for AI agent thinking, frontier AI commentary, deep interviews, and non-boring high-signal essays. Use when Codex needs…
Cite
Cite this page
ModelsAtlas. “ak-rss-digest (rookie-ricardo/erduo-skills)”. Retrieved 20 Oct 2026. https://modelsatlas.com/skills/rookie-ricardo/ak-rss-digest
Trust audit
Audit 0.4.1 · source read 20 Oct 2026
SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 13,985 of 14,816 audited skills.
What the source does
- FilesystemNone observedNo reads or writes in the source
- NetworkDeclared3 observations
- ShellNone observedNo commands run in the source
- DependenciesPinnedNothing floats
- SecretsNone foundNo keys in source
Five audit layers
| Layer | What we check | Result | Findings |
|---|---|---|---|
L0 Provenance | Repo owner, licence, archive status, activity | PASS | 0 |
L1 Static source | Secrets, path traversal, supply chain, hidden code | PASS | 0 |
L2 Instructions | Prompt injection, authority framing, hidden directives | PASS | 0 |
L3 Inventory | The files and declarations match the source | PASS | 0 |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED why | 0 |
Gates applied: no behavioural pass.
Findings (0)
No findings at any severity. We re-audit when the source changes.
Audit 0.4.1 · source sha 7e0764f5a97c · 20 Oct 2026Report an issue or request a re-scan
Provenance
Who published it, and what the verdict is pinned to
- Publisherrookie-ricardo GitHub userOwner of the repository this skill is read from
- Source folderrookie-ricardo/erduo-skills/skills/ak-rss-digestThe exact folder we audited
- LicenceMITAs the repository states it
- Commit pinned for this verdict7e0764f5a97cA new audit runs when the source changes
- Repository statusNot archivedLast push 87 days ago
- Sandboxed runNot runSkills are read, not executed; layer L4 is skipped
What it tells the agent
Full source on GitHub ↗Its description: Curate a Chinese reading digest from a fixed bundle of RSS and Atom feeds, with a strong preference for AI agent thinking, frontier AI commentary, deep interviews, and non-boring high-signal essays. Use when Codex needs…
--- name: ak-rss-digest description: Curate a Chinese reading digest from a fixed bundle of RSS and Atom feeds, with a strong preference for AI agent thinking, frontier AI commentary, deep interviews, and non-boring high-signal essays. Use when Codex needs to pull the latest week's posts by default, or a specific day's posts when explicitly requested, summarize them, score each article on a 10-point scale, and output only the posts scoring above 7 in a concise Chinese daily-brief style. --- # AK RSS Digest ## Overview Use this skill to build a current reading list from the feed bundle in `references/feeds.opml`. Default to the most recent 7 days ending on the current date in `Asia/Shanghai`, and narrow to a single day only when the user explicitly asks for it. ## Workflow 1. Run `python3 scripts/fetch_today_feed_items.py --format json` to collect entries from the configured feeds. This defaults to the most recent 7 days. 2. Treat feed-level network failures as non-fatal. Continue with the feeds that succeeded and mention major failures only when they materially reduce coverage. 3. Read the structured output and discard obvious mismatches before opening article pages. Reject items that are clearly raw research papers, release notes, changelogs, benchmark dumps, or narrowly technical implementation logs without broader implications. 4. Open the remaining candidate links when the feed summary is too thin to judge the article well. Skim for thesis, novelty, readability, and whether the piece offers strong perspective rather than just information. 5. Score every serious candidate on the rubric below. Output only items with a score strictly greater than `7.0`. 6. If nothing clears the threshold, say so directly instead of padding the output with mediocre picks. ## Selection Heuristics Prefer articles with at least one of these traits: - Fresh thinking about AI agents, agent tooling, agent UX, multi-agent workflows, evaluation, deployment, or failure modes. - Strong interviews or conversations with operators, founders, researchers, or engineers who reveal how frontier work is actually being done. - Essays that synthesize a new direction, new constraint, or strategic implication in AI, software, or adjacent technology. - Pieces that are readable and idea-dense for a general technical audience, not just specialists in one subfield. Penalize heavily or reject: - Pure technical papers and paper summaries with little interpretive value. - Vendor marketing, launch fluff, SEO writing, or obvious news rewrites. - Narrow implementation diaries that do not connect to broader product, research, or ecosystem questions. - Dry reference material that is correct but not worth a strong recommendation. ## Scoring Rubric - `9-10`: Exceptional fit. Strong signal, strong writing, original insight, and clearly valuable for someone tracking AI agents or adjacent frontier shifts. - `8-8.9`: Good recommendation. Worth reading, clear point of view, and relevant enough to the target taste profile. - `7-7.9`: Borderline. Useful but not compelling enough for the final digest. Do not output it. - `5-6.9`: Competent but dry, derivative, too narrow, or not aligned with the target taste profile. - `<5`: Irrelevant, low-signal, or actively unsuitable. When scoring, weigh these dimensions: - Relevance to AI agents, frontier AI, deep operator insight, or adjacent strategic technology discussion. - Originality of the article's argument or reporting. - Readability and ability to hold attention. - Practical usefulness for someone trying to keep up with meaningful new directions. ## Output Format Write the final answer in Simplified Chinese. For each article that scores above `7`, include exactly these elements with Chinese labels: - `标题`: original article title. - `评分`: `x/10`, use one decimal place when helpful. - `推荐语`: one or two sentences explaining why this is worth reading. - `摘要`: exactly two sentences summarizing the article. - `链接`: canonical article URL. Use a concise tone that reads like a curated daily brief, not a formal report: - Prefer short, direct sentences over explanatory padding. - Lead with why the article is worth the user's time. - Keep each item compact and scannable. - Avoid English field names such as `Title`, `Score`, or `Recommendation`. Use this structure for the final answer: ```markdown 本期从最近一周的 RSS 里筛出几篇值得看的文章,重点偏 AI agent、前沿判断和不太枯燥的深度内容。 - 标题:文章标题 评分:8.7/10 推荐语:1-2 句话,先说为什么值得看。 摘要:严格两句话,讲清核心观点和价值。 链接:文章链接 ``` If nothing qualifies, say so directly in Chinese, for example: ```markdown 这周没有筛到真正值得推荐的文章。现有更新要么偏技术细节,要么信息密度不够,没有过 7 分线。 ``` ## Resources - `scripts/fetch_today_feed_items.py` Use this script to fetch the configured feeds and return recent entries as structured JSON or Markdown. - `references/feeds.opml` Use this as the source of truth for the feed bundle. Keep the workflow anchored to this file unless the user explicitly asks to change the feed list. ## Command Examples Fetch the latest week of entries in Shanghai time: ```bash python3 scripts/fetch_today_feed_items.py --format json ``` Fetch a single day explicitly: ```bash python3 scripts/fetch_today_feed_items.py --date 2026-03-17 --days 1 --timezone Asia/Shanghai --format json ``` Fetch the latest posts from the past week: ```bash python3 scripts/fetch_today_feed_items.py --days 7 --limit 30 --format json ``` Inspect a quick Markdown view instead of JSON: ```bash python3 scripts/fetch_today_feed_items.py --format markdown ```
Excerpt, first 5,525 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.
Install
Pinned to the audited commit 7e0764f
git clone https://github.com/rookie-ricardo/erduo-skills git -C erduo-skills checkout 7e0764f5a97c
The author documents no install command, so this uses the repository directly. Our verdict covers commit 7e0764f5a97c only.
Works in which agents?
What its own text says, not a test
| Agent | Status | More |
|---|---|---|
| Codex | Mentioned in its text, not tested | Skills for Codex · About Codex |
Audit history
Every audit, every source change
- ✓SAFE B 89 / 100
first audit · source
7e0764f5a97c
Similar skills
obra/superpowers
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions…
obra/superpowers
Use when you have a spec or requirements for a multi-step task, before touching code
obra/superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
Questions about ak-rss-digest
Is ak-rss-digest safe to install?
What can ak-rss-digest access on my machine?
Which assistants does ak-rss-digest work with?
How current is this page?
Sources
- github.com/rookie-ricardo/erduo-skills/tree/main/skills/ak-rss-d — the audited source at commit 7e0764f5a97c and every finding aboveObserved · 20 Oct 2026
Spotted something wrong? Report a correction · Methodology
Keep going in your AI
Opens with this page as the source. We add nothing else to the prompt.
- Is ak-rss-digest safe to install?
- What can ak-rss-digest access on my machine?
- Which assistants does ak-rss-digest work with?