菜单
Fetch developer newsletter RSS feeds and Hacker News top stories, then pick the 10 best items as YouTube video topic ideas. Use when the user asks for newsletter picks, video topic ideas from newsletters, a weekly dev digest, or to "run the newsletter digest".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Ship a completed feature - lint, test, commit, push, PR, subagent review loop, risk-rated PR description. Use when the user says "finish this feature", "ship it", "wrap this up", or "create the PR".
Ask the user a few casual clarifying questions before acting. Reliable trigger is the explicit /questions command. Soft trigger is the message's last character being a question mark, but that's a phrase-match heuristic the model may miss - use /questions when you want it guaranteed. Lighter, more conversational sibling of "grill me" style interviews - not relentless, just a couple of genuine questions to sharpen the request before doing work.
Update a project's documentation to reflect code changes on the current branch before opening a PR. Use when the user finishes a feature/fix and is about to create a PR, or asks to "sync docs", "update the docs for these changes", or check whether documentation needs updating.
Give an honest opinion without implementing anything, when a user message ends with "wdyt", "wdyt?", or "what do you think" (also "what do you think?"). Use this instead of jumping to a plan or code. Surfaces concerns, tradeoffs, and clarifying questions, then waits for the user's response before doing any work.
Route subtasks to other models - glm-5.2 (opencode), gpt (codex exec), grok-4.5 (grok build), Claude subagents - with cost/quality routing and verification. Use when the user says "delegate", "farm this out", "have glm/codex/grok do it", or asks to split a task across models. Not for ordinary tasks the main agent should do itself.
Multi-model code review - the /review methodology with finder agents routed to cheap models on other harnesses (gpt via codex, glm via opencode) through the delegate skill, verified and synthesized by the main agent. Use when the user says "delegate-review", "multi-model review", or "review this PR with cheap workers".
| name | newsletter-digest |
| description | Fetch developer newsletter RSS feeds and Hacker News top stories, then pick the 10 best items as YouTube video topic ideas. Use when the user asks for newsletter picks, video topic ideas from newsletters, a weekly dev digest, or to "run the newsletter digest". |
Fetch dev newsletter RSS feeds and Hacker News top stories, then curate 10 YouTube-video-worthy items, then print the result directly in chat.
https://javascriptweekly.com/rsshttps://react.statuscode.com/rsshttps://nodeweekly.com/rsshttps://daily.dev/rss.xmlhttps://news.ycombinator.com/best (top stories from the last 48 hours)If the user names different feeds or a different count, use those instead.
Use curl -sL <url> for each feed in parallel Bash calls. Newsletter RSS items typically bundle many links per issue — fetch the latest issue's RSS, then for each <item> parse the <description> HTML to extract the individual article links (each issue is itself a roundup of dozens of links).
For Hacker News, fetch https://news.ycombinator.com/best with curl -sL and parse the HTML to extract story titles, URLs, points, and comment counts. Each <tr class="athing"> contains a story row — pull the title link and URL from the <span class="titleline"> element, and the points/comments from the next <tr> subtext row.
If a feed fails or returns empty, note it and continue with the others.
Apply criteria in order:
Avoid: long research papers, sprawling multi-topic roundups, deeply niche internals (compiler arcana, single-vendor minutiae), job posts, sponsor slots, pure opinion blogs without a hook.
Aim for variety across all sources rather than 10 items from one feed.
Output directly in the assistant message as markdown. Include today's date at the top. Format:
# Newsletter Digest — <today's date>
1. **<Title>** — _<Source>_
<URL>
<one-sentence video angle>
2. **<Title>** — _<Source>_
...
Do NOT post to Slack or any external destination. The output is just the chat message.
The "best 10" step is judgment. Apply the criteria above explicitly rather than defaulting to whatever's at the top of the feed.