AI新闻简报策划工具 - 使用inference.sh CLI自动化创建高质量行业简报

newsletter-curation by inferen-sh/skills

7,000 周安装量

182 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/inferen-sh/skills --skill newsletter-curation

AI/机器学习营销生产力

🇨🇳中文介绍

新闻简报策划

通过 inference.sh CLI 创建和策划高质量的新闻简报。

快速开始

需要 inference.sh CLI (infsh)。安装说明

infsh login

# 查找要策划的内容
infsh app run tavily/search-assistant --input '{
  "query": "most important AI developments this week 2024"
}'

# 生成简报标题
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>"
}'

简报格式

1. 链接汇总

5-15 个精选链接，每个链接附有 1-3 句评论。

## 本周精选

### [文章标题](url)
用一到三句话解释为什么这很重要，以及读者能从中获得什么。加入你的观点——不要只是描述。

### [文章标题](url)
你的评论放在这里。价值在于你的策划和视角，而不仅仅是链接。

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

2. 深度分析 + 链接

一篇深度分析（300-500 词）+ 5-8 个精选链接。

## 重大故事

[对本周最重要主题的 300-500 词分析]

## 同样值得一读

- **[标题](url)** — 一句话评论
- **[标题](url)** — 一句话评论
...

一篇重点突出的文章（500-1,000 词），论点清晰。

## [文章标题]

[你的原创分析、观点或见解]

## 我正在阅读的内容

- [标题](url) — 简短说明
- [标题](url) — 简短说明

与专家或从业者进行专题对话。

你所在领域的数字、图表和趋势分析。

# [简报名称] — 第 #[N] 期

## 👋 你好

[2-3 句个人介绍——你在想什么，本期涵盖的内容，为什么现在很重要]

## 🔥 重大故事

[特色内容——你最深入的分析或最重要的精选文章及评论]

## 📚 值得一读

### [标题 1](url)
[2-3 句评论，包含你的观点]

### [标题 2](url)
[2-3 句评论]

### [标题 3](url)
[2-3 句评论]

## 💡 快讯

- [一句话 + 链接](url)
- [一句话 + 链接](url)
- [一句话 + 链接](url)

## 📊 本周数据

[一个引人注目的数据点及其背景]

## 💬 来自社区

[读者回复、问题或讨论点]

---

这就是本周的全部内容。如果你觉得有用，请转发给可能感兴趣的同事。

[你的名字]

在哪里寻找内容

# 行业新闻
infsh app run tavily/search-assistant --input '{
  "query": "[你的领域] news this week latest developments"
}'

# 研究和数据
infsh app run exa/search --input '{
  "query": "[你的领域] research report statistics 2024"
}'

# 热门讨论
infsh app run tavily/search-assistant --input '{
  "query": "site:reddit.com [你的领域] discussion this week"
}'

# 学术/深度内容
infsh app run exa/search --input '{
  "query": "[你的领域] analysis deep dive opinion"
}'

来源类型	示例	最适合
新闻	TechCrunch, The Verge, 行业媒体	突发进展
研究	论文、报告、调查	数据支持的见解
博客	工程博客、个人博客	从业者视角
社交媒体	Twitter 主题、LinkedIn 帖子	热门观点、讨论
工具	产品发布、更新	实用推荐
社区	Reddit, HN, 论坛	基层情绪

对于每一篇内容，请自问：

问题	如果否 →
我会一对一地把它发送给同事吗？	不要包含
它是否教授了可操作的内容？	考虑跳过
来源可信吗？	寻找更好的来源
它是否及时/与本周相关？	留待以后或跳过
我能添加增加价值的评论吗？	仅仅链接是不够的

什么是好的评论

❌ 仅仅描述："这篇文章谈论了 React Server Components。"
❌ 重复标题："React Server Components 已经来了。"

✅ 添加上下文："React Server Components 上周发布了，这是我看到的第一个生产环境拆解。关键见解：它们将初始 JS 包大小减少了 60%，但增加了构建管道的复杂性。"

✅ 给出你的观点："我对这里的迁移路径持怀疑态度。我交谈过的大多数团队都在等待更好的工具。"

✅ 建立联系："这与 Vercel 上个月的公告很契合——生态系统显然正在向这种模式靠拢。"

[发生了什么] + [为什么这对读者很重要] + [你的观点或预测]

频率	最适合	打开率影响
每周	大多数简报	最高——可预测，不会让人应接不暇
每两周	深度分析、文章	如果内容充实则效果不错
每日	新闻导向、短格式	需要养成习惯，有风险
每月	研究汇总	适合深度内容，但容易被遗忘

每周是最佳选择。 同一天，同一时间，每周如此。一致性有助于养成习惯。

星期	表现
星期二	打开率最高
星期四	第二高
星期三	第三
星期一	较低（收件箱过载）
星期五	较低（周末模式）
周末	最低（但某些细分领域可能表现良好）

公式	示例
期号 + 预告	"#47: 没人谈论的框架"
数字 + 主题	"本月改变我工作流程的 5 个工具"
问题	"TypeScript 正在消亡吗？"
本周 + 类别	"本周 AI 动态：GPT-5 传闻，开源获胜"
直接价值	"我希望早点拥有的 SQL 优化指南"

保持在 50 个字符以内。 移动端大约在 35 个字符处截断。

策略	实施方式
交叉推广	与互补的简报合作
社交分发	在 Twitter/LinkedIn 上发布关键见解并附带订阅号召性用语
推荐计划	"转发给 3 个朋友" 或正式的推荐奖励
SEO 存档	将简报期号作为博客文章发布
潜在客户吸引	"订阅并获取 [免费资源]"
保持质量稳定	最佳增长策略：值得一读

# 为简报创建社交预告
infsh app run x/post-create --input '{
  "text": "本周 The Weekly Signal 内容：\n\n→ 为什么边缘计算正在吞噬后端\n→ 没人谈论的数据库迁移\n→ 本月发现的 5 个工具\n\n加入 2,000+ 工程师：[链接]\n\n第 47 期明天早上发布。"
}'

指标	良好	优秀	如果偏低应采取的行动
打开率	30-40%	40%+	改进主题行
点击率	3-5%	5%+	更好的内容策划，更强的号召性用语
退订率	每期 < 0.5%	< 0.2%	检查内容质量、频率
回复率	任何回复	定期回复	提问，邀请对话
转发率	任何转发	—	让内容值得分享
增长率	每月 5-10%	10%+	增加分发渠道，推荐计划

错误	问题	解决方法
没有固定的时间表	读者会忘记你	每周同一天同一时间
只有链接没有评论	你只是个书签，不是简报	对每一篇内容都添加你的观点
链接过多（15+）	令人应接不暇，没有重点突出	最多 5-10 个精选内容
通用主题行	打开率低	预告最佳内容，保持在 50 个字符以内
没有个人风格	读起来像 RSS 订阅源	介绍段落、观点、个性
只有推广内容	读者会退订	90% 价值内容，最多 10% 推广内容
质量不稳定	信任度下降	宁愿跳过一期，也不要发送薄弱的内容
没有互动号召性用语	单向广播	提问，邀请回复，鼓励转发
没有存档/SEO	错失增长渠道	将期号作为网页发布

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

浏览所有应用：infsh app list

🇺🇸English

Newsletter Curation

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

Quick Start

Requires inference.sh CLI (infsh). Install instructions

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 Type	Examples	Best For
News	TechCrunch, The Verge, industry press	Breaking developments
Research	Papers, reports, surveys	Data-backed insights
Blogs	Engineering blogs, personal blogs	Practitioner perspectives
Social	Twitter threads, LinkedIn posts	Hot takes, discussions
Tools	Product launches, updates	Practical recommendations
Community	Reddit, HN, forums	Ground-level sentiment

Curation Quality Filter

For each piece of content, ask:

Question	If 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

Frequency	Best For	Open Rate Impact
Weekly	Most newsletters	Highest — predictable, not overwhelming
Bi-weekly	Deep analysis, essays	Good if content is substantial
Daily	News-focused, short format	Requires dedicated habit, risky
Monthly	Research roundups	OK for depth, risks being forgotten

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

Day	Performance
Tuesday	Highest open rates
Thursday	Second highest
Wednesday	Third
Monday	Lower (inbox overload)
Friday	Lower (weekend mode)
Weekend	Lowest (but some niches thrive)

Subject Lines

Formula	Example
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

Strategy	Implementation
Cross-promotion	Partner with complementary newsletters
Social distribution	Post key insights on Twitter/LinkedIn with subscribe CTA
Referral program	"Forward to 3 friends" or formal referral rewards
SEO archive	Publish newsletter archive as blog posts
Lead magnet	"Subscribe and get [free resource]"
Consistent quality	The 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:\n\n→ Why edge computing is eating the backend\n→ The database migration nobody talks about\n→ 5 tools I discovered this month\n\nJoin 2,000+ engineers: [link]\n\nIssue #47 drops tomorrow morning."
}'

Metrics That Matter

Metric	Good	Great	Action If Low
Open rate	30-40%	40%+	Improve subject lines
Click rate	3-5%	5%+	Better content curation, stronger CTAs
Unsubscribe rate	< 0.5% per issue	< 0.2%	Check content quality, frequency
Reply rate	Any replies	Regular replies	Ask questions, invite conversation
Forward rate	Any forwards	—	Make content share-worthy
Growth rate	5-10% monthly	10%+	Increase distribution, referral program

Common Mistakes

Mistake	Problem	Fix
No consistent schedule	Readers forget about you	Same day, same time, every week
Links without commentary	You're a bookmark, not a newsletter	Add your take on every piece
Too many links (15+)	Overwhelming, nothing stands out	5-10 curated picks max
Generic subject lines	Low open rates	Tease the best content, keep under 50 chars
No personal voice	Reads like an RSS feed	Intro paragraph, opinions, personality
Only promotional content	Readers unsubscribe	90% value, 10% promotion max
Inconsistent quality	Trust erodes	Skip an issue rather than send a weak one
No CTA for engagement	One-way broadcast	Ask questions, invite replies, encourage forwards
No archive/SEO

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

Weekly Installs

7.0K

Repository

inferen-sh/skills

GitHub Stars

182

First Seen

12 days ago

Security Audits

Gen Agent Trust HubPass SocketWarn SnykWarn

Installed on

claude-code5.5K

gemini-cli5.0K

codex5.0K

amp5.0K

opencode5.0K

kimi-cli5.0K

AI新闻简报策划工具 - 使用inference.sh CLI自动化创建高质量行业简报

🇨🇳中文介绍

新闻简报策划

快速开始

简报格式

1. 链接汇总

相关 Skills

2. 深度分析 + 链接

3. 原创文章

4. 问答 / 访谈

5. 数据/趋势

期号结构

模板

内容来源