Token导航 LogoToken导航TokenDH.com
研究检索external-servicegithub未标认证来源可访问许可证需确认审计提醒

newsletter-curation时事通讯策展

Agent Skill

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

总安装

517

周安装

22

GitHub Stars

363

下载量

181
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/inference-sh/agent-skills --skill newsletter-curation

简介

用于查找、检索和筛选相关信息。newsletter-curation 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

  • 适合根据关键词或来源线索快速定位候选结果。
  • 可结合仓库和 README 核验具体用法。
  • 安装前建议确认权限和维护状态。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。
  • 注意是否会触发联网、命令执行或文件读写。

SKILL.md

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 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:\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

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 forwardsMake 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

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

34.97%
按下载量换算63

Claude

29.31%
按下载量换算53

Cursor

18.98%
按下载量换算34

Gemini CLI

9.56%
按下载量换算17

安全审计

Gen Agent Trust Hub

通过

Socket

可疑

Snyk

可疑

权限和风险

external-service

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

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills