Token导航 LogoToken导航

Agent Skill · 研究检索

newsletter-curation(时事通讯策展)

newsletter-curation 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

newsletter-curation 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为调用外部服务;许可证为 MIT,暂无第三方扫描结果,按安装量在研究检索类的 73,675 个 Skill 里排第 13,504。

总安装 9,327周安装 380GitHub Stars 公开资料未说明下载 3,637核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:newsletter-curation(时事通讯策展)
来源仓库:https://github.com/inf-sh/skills
仓库路径:skills/newsletter-curation
安装命令:
npx skills add inf-sh/skills --skill "newsletter-curation"
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

AgentSkills.tonpx skills
npx skills add inf-sh/skills --skill "newsletter-curation"

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

时事通讯策划,包括内容来源、编辑结构和订阅者增长策略。涵盖问题格式、链接综述、评论风格和发送节奏。用于:电子邮件通讯、链接综述、每周摘要、策划内容、创作者通讯。触发器:时事通讯、电子邮件时事通讯、时事通讯精选、每周摘要、链接综述、精选时事通讯、时事通讯写作、时事通讯格式、订阅者增长、时事通讯策略、内容管理、时事通讯模板

来源仓库内路径:skills/newsletter-curation

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add inf-sh/skills --skill "newsletter-curation";命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要调用外部服务,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

newsletter-curation 怎么安装?

在终端执行 npx skills add inf-sh/skills --skill "newsletter-curation"。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

newsletter-curation 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

newsletter-curation 需要什么权限?

权限级别是调用外部服务。该 Skill 可能调用第三方服务、云服务或外部模型 API,使用前需要确认账号、额度、数据发送范围和服务条款。

newsletter-curation 是免费的吗?

来源标注的许可证是 MIT。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

newsletter-curation 用的人多吗?

公开数据是累计安装 9,327 次,近一周安装 380 次,下载 3,637 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

newsletter-curation 安全吗?

没有查到第三方扫描结果,安全性无法从公开资料判断,安装前请自行审查源码、依赖和命令行为。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 许可证明确为 MIT,商用和分发边界好判断。

先想清楚的地方

  • 没有第三方扫描结果,安全性只能靠自己读源码判断。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 要求有安全扫描结论才肯安装的团队。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
newsletter-curation

时事通讯策展 · 本页

9,327—调用外部服务MIT未收录

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

name
newsletter-curation
description
Newsletter curation with content sourcing, editorial structure, and subscriber growth strategies. Covers issue formatting, link roundups, commentary style, and sending cadence. Use for: email newsletters, link roundups, weekly digests, curated content, creator newsletters. Triggers: newsletter, email newsletter, newsletter curation, weekly digest, link roundup, curated newsletter, newsletter writing, newsletter format, subscriber growth, newsletter strategy, content curation, newsletter template
allowed-tools
Bash(infsh *)

Newsletter Curation

Create and curate high-quality newsletters via inference.sh CLI.

Quick Start

curl -fsSL https://cli.inference.sh | sh && infsh login

# Find content to curate
infsh app run tavily/search-assistant --input '{
  "query": "most important AI developments this week 2024"
}'

# Generate newsletter header
infsh app run infsh/html-to-image --input '{
  "html": "<div style=\"width:600px;height:200px;background:linear-gradient(135deg,#1e293b,#334155);display:flex;align-items:center;padding:40px;font-family:system-ui;color:white\"><div><h1 style=\"font-size:32px;margin:0;font-weight:800\">The Weekly Signal</h1><p style=\"font-size:16px;opacity:0.7;margin-top:8px\">Issue #47 — January 15, 2025</p></div></div>"
}'

Newsletter Formats

1. Link Roundup

5-15 curated links with 1-3 sentence commentary per link.

## This Week's Top Picks

### [Article Title](url)
One to three sentences explaining why this matters and what the
reader will get from it. Add your take — don't just describe.

### [Article Title](url)
Your commentary here. The value is your curation and perspective,
not just the link.

2. Deep Dive + Links

One in-depth analysis (300-500 words) + 5-8 curated links.

## The Big Story

[300-500 word analysis of the week's most important topic]

## Also Worth Reading

- **[Title](url)** — One sentence commentary
- **[Title](url)** — One sentence commentary
...

3. Original Essay

One focused piece (500-1,000 words) with a clear thesis.

## [Essay Title]

[Your original analysis, opinion, or insight]

## What I'm Reading

- [Title](url) — brief note
- [Title](url) — brief note

4. Q&A / Interview

Feature conversation with an expert or practitioner.

5. Data/Trends

Numbers, charts, and analysis of trends in your space.

Issue Structure

The Template

# [Newsletter Name] — Issue #[N]

## 👋 Hello

[2-3 sentences of personal intro — what's on your mind,
what this issue covers, why it matters right now]

## 🔥 The Big Story

[Featured content — your deepest analysis or most
important curated piece with commentary]

## 📚 Worth Reading

### [Title 1](url)
[2-3 sentence commentary with your take]

### [Title 2](url)
[2-3 sentence commentary]

### [Title 3](url)
[2-3 sentence commentary]

## 💡 Quick Hits

- [One-liner + link](url)
- [One-liner + link](url)
- [One-liner + link](url)

## 📊 Stat of the Week

[One compelling data point with context]

## 💬 From the Community

[Reader reply, question, or discussion point]

---

That's it for this week. If you found this useful, forward
it to a colleague who'd enjoy it.

[Your name]

Content Sourcing

Where to Find Content

# Industry news
infsh app run tavily/search-assistant --input '{
  "query": "[your niche] news this week latest developments"
}'

# Research and data
infsh app run exa/search --input '{
  "query": "[your niche] research report statistics 2024"
}'

# Trending discussions
infsh app run tavily/search-assistant --input '{
  "query": "site:reddit.com [your niche] discussion this week"
}'

# Academic/deep content
infsh app run exa/search --input '{
  "query": "[your niche] analysis deep dive opinion"
}'

Source Categories

Source TypeExamplesBest For
NewsTechCrunch, The Verge, industry pressBreaking developments
ResearchPapers, reports, surveysData-backed insights
BlogsEngineering blogs, personal blogsPractitioner perspectives
SocialTwitter threads, LinkedIn postsHot takes, discussions
ToolsProduct launches, updatesPractical recommendations
CommunityReddit, HN, forumsGround-level sentiment

Curation Quality Filter

For each piece of content, ask:

QuestionIf No →
Would I send this to a colleague 1-on-1?Don't include
Does it teach something actionable?Consider skipping
Is the source credible?Find better source
Is it timely/relevant this week?Save for later or skip
Can I add commentary that adds value?Just linking isn't enough

Writing Commentary

What Makes Good Commentary

❌ Just describing: "This article talks about React Server Components."
❌ Restating the headline: "React Server Components are here."

✅ Adding context: "React Server Components shipped last week, and this
   is the first production teardown I've seen. Key insight: they reduced
   initial JS bundle by 60%, but added complexity to the build pipeline."

✅ Giving your take: "I'm skeptical about the migration path here.
   Most teams I've talked to are waiting for better tooling."

✅ Connecting dots: "This pairs well with Vercel's announcement last
   month — the ecosystem is clearly converging on this pattern."

Commentary Formula

[What happened] + [Why it matters to the reader] + [Your take or prediction]

Sending Cadence

FrequencyBest ForOpen Rate Impact
WeeklyMost newslettersHighest — predictable, not overwhelming
Bi-weeklyDeep analysis, essaysGood if content is substantial
DailyNews-focused, short formatRequires dedicated habit, risky
MonthlyResearch roundupsOK for depth, risks being forgotten

Weekly is the sweet spot. Same day, same time, every week. Consistency builds habit.

DayPerformance
TuesdayHighest open rates
ThursdaySecond highest
WednesdayThird
MondayLower (inbox overload)
FridayLower (weekend mode)
WeekendLowest (but some niches thrive)

Subject Lines

FormulaExample
Issue number + teaser"#47: The framework nobody's talking about"
Number + topic"5 tools that changed my workflow this month"
Question"Is TypeScript dying?"
This week + category"This week in AI: GPT-5 rumors, open source wins"
Direct value"The SQL optimization guide I wish I had earlier"

Keep under 50 characters. Mobile truncates at ~35.

Growth Strategies

StrategyImplementation
Cross-promotionPartner with complementary newsletters
Social distributionPost key insights on Twitter/LinkedIn with subscribe CTA
Referral program"Forward to 3 friends" or formal referral rewards
SEO archivePublish newsletter archive as blog posts
Lead magnet"Subscribe and get [free resource]"
Consistent qualityThe best growth strategy: be worth reading
# Create social teaser for newsletter
infsh app run x/post-create --input '{
  "text": "This week in The Weekly Signal:\
\
→ Why edge computing is eating the backend\
→ The database migration nobody talks about\
→ 5 tools I discovered this month\
\
Join 2,000+ engineers: [link]\
\
Issue #47 drops tomorrow morning."
}'

Metrics That Matter

MetricGoodGreatAction If Low
Open rate30-40%40%+Improve subject lines
Click rate3-5%5%+Better content curation, stronger CTAs
Unsubscribe rate< 0.5% per issue< 0.2%Check content quality, frequency
Reply rateAny repliesRegular repliesAsk questions, invite conversation
Forward rateAny forwards—Make content share-worthy
Growth rate5-10% monthly10%+Increase distribution, referral program

Common Mistakes

MistakeProblemFix
No consistent scheduleReaders forget about youSame day, same time, every week
Links without commentaryYou're a bookmark, not a newsletterAdd your take on every piece
Too many links (15+)Overwhelming, nothing stands out5-10 curated picks max
Generic subject linesLow open ratesTease the best content, keep under 50 chars
No personal voiceReads like an RSS feedIntro paragraph, opinions, personality
Only promotional contentReaders unsubscribe90% value, 10% promotion max
Inconsistent qualityTrust erodesSkip an issue rather than send a weak one
No CTA for engagementOne-way broadcastAsk questions, invite replies, encourage forwards
No archive/SEOMissing growth channelPublish issues as web pages

Related Skills

npx skills add inference-sh/skills@email-design
npx skills add inference-sh/skills@content-repurposing
npx skills add inference-sh/skills@seo-content-brief

Browse all apps: infsh app list

平台分布

Claude Code

63.17%
按下载量换算2,297

Cursor

28.74%
按下载量换算1,045

安全审计

暂无安全审计结果可展示。

权限和风险

调用外部服务

该 Skill 可能调用第三方服务、云服务或外部模型 API,使用前需要确认账号、额度、数据发送范围和服务条款。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills