ak-rss-digest
Use this skill to build a current reading list from the feed bundle in references/feeds.opml.
Works with
0
total installs
0
this week
667
GitHub stars
0
upvotes
Install Skill
Run in your terminal
0
installs
0
this week
667
stars
What it does
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.
Installation Guide
How to use ak-rss-digest on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your machine
- ›Node.js 16+ with npm — verify with
node --version - ›Active project directory where you want to add
ak-rss-digest
Run the install command
Execute the skills CLI command in your project's root directory to begin installation:
Fetches ak-rss-digest from rookie-ricardo/erduo-skills and configures it for Cursor.
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate ak-rss-digest. Access via /ak-rss-digest in your agent's command palette.
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Documentation
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
- Run
python3 scripts/fetch_today_feed_items.py --format jsonto collect entries from the configured feeds. This defaults to the most recent 7 days. - Treat feed-level network failures as non-fatal. Continue with the feeds that succeeded and mention major failures only when they materially reduce coverage.
- 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.
- 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.
- Score every serious candidate on the rubric below. Output only items with a score strictly greater than
7.0. - 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, orRecommendation.
Use this structure for the final answer:
本期从最近一周的 RSS 里筛出几篇值得看的文章,重点偏 AI agent、前沿判断和不太枯燥的深度内容。
- 标题:文章标题
评分:8.7/10
推荐语:1-2 句话,先说为什么值得看。
摘要:严格两句话,讲清核心观点和价值。
链接:文章链接
If nothing qualifies, say so directly in Chinese, for example:
这周没有筛到真正值得推荐的文章。现有更新要么偏技术细节,要么信息密度不够,没有过 7 分线。
Resources
-
scripts/fetch_today_feed_items.pyUse this script to fetch the configured feeds and return recent entries as structured JSON or Markdown. -
references/feeds.opmlUse 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:
python3 scripts/fetch_today_feed_items.py --format json
Fetch a single day explicitly:
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:
python3 scripts/fetch_today_feed_items.py --days 7 --limit 30 --format json
Inspect a quick Markdown view instead of JSON:
python3 scripts/fetch_today_feed_items.py --format markdown
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Steps
- 1Install product management skill
- 2Start with user story generation for known feature
- 3Progress to competitive analysis: research 2-3 competitors
- 4Use for roadmap prioritization: apply RICE/ICE scoring
- 5Draft stakeholder communications and refine based on feedback
- 6Build template library for recurring PM tasks
- 7Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Related Skills
grill-me
388mattpocock/skills
premortem
197parcadei/continuous-claude-v3
deslop
118cursor/plugins
framer-motion
99pproenca/dot-skills
write-a-prd
91mattpocock/skills
travel-planner
90ailabs-393/ai-labs-claude-skills
Reviews
- LLiam Mensah★★★★★Dec 24, 2024
Solid pick for teams standardizing on skills: ak-rss-digest is focused, and the summary matches what you get after install.
- AAmina Thompson★★★★★Dec 24, 2024
We added ak-rss-digest from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- GGanesh Mohane★★★★★Dec 12, 2024
ak-rss-digest has been reliable in day-to-day use. Documentation quality is above average for community skills.
- AAmina Sanchez★★★★★Dec 8, 2024
ak-rss-digest reduced setup friction for our internal harness; good balance of opinion and flexibility.
- YYuki Desai★★★★★Nov 27, 2024
ak-rss-digest is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- SSofia Anderson★★★★★Nov 23, 2024
Registry listing for ak-rss-digest matched our evaluation — installs cleanly and behaves as described in the markdown.
- YYuki Martin★★★★★Nov 15, 2024
ak-rss-digest has been reliable in day-to-day use. Documentation quality is above average for community skills.
- BBenjamin Thompson★★★★★Nov 15, 2024
Keeps context tight: ak-rss-digest is the kind of skill you can hand to a new teammate without a long onboarding doc.
- SSakshi Patil★★★★★Nov 3, 2024
Solid pick for teams standardizing on skills: ak-rss-digest is focused, and the summary matches what you get after install.
- CChaitanya Patil★★★★★Oct 22, 2024
We added ak-rss-digest from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 51
Discussion
Comments — not star reviews- No comments yet — start the thread.