Token导航 LogoToken导航

Agent Skill · 待分类

newsletter-creator(时事通讯创建者)

newsletter-creator 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

newsletter-creator 是待分类类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为权限未标注;许可证信息还不明确,第三方扫描有提醒项,按安装量在待分类类的 11,209 个 Skill 里排第 2,851。

总安装 1,341周安装 57GitHub Stars 48下载 470核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/travisjneuman/.claude --skill newsletter-creator

这个 Skill 是做什么的

这个 Skill 的分类还没最终确定,用法以来源仓库的说明为准。

newsletter-creator 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。

适用于 GitHub 仓库管理、代码协作、Issue 跟踪等开发相关任务场景。通过 npx skills add 命令从指定 GitHub 仓库安装,需确认权限范围和联网需求。安装前建议核实维护状态、是否会触发命令执行或文件读写操作。可结合原始 README 文档进一步核验具体功能和使用方法。

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

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/travisjneuman/.claude --skill newsletter-creat…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    权限没有明确标注,第一次使用时只给一个无关紧要的任务,观察它到底读了哪些文件和网络。

常见问题

6 条

newsletter-creator 怎么安装?

在终端执行 npx skills add https://github.com/travisjneuman/.claude --skill newsletter-creator。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

newsletter-creator 支持哪些 AI 工具?

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

newsletter-creator 需要什么权限?

权限级别没有明确标注。第一次使用时建议只给无关紧要的任务,观察它实际读写了哪些内容。

newsletter-creator 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

newsletter-creator 用的人多吗?

公开数据是累计安装 1,341 次,近一周安装 57 次,下载 470 次,GitHub 48 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

newsletter-creator 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

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

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

待分类类 Skill 对比

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

infsh CLI · Codex、Claude

4,374,576382权限未标注未明确未收录
ai-video-generation

AI 视频生成 · Codex、Claude

4,313,376382调用外部服务未明确有提醒
lark-openapi-explorer

云雀 OpenAPI 浏览器 · Codex、Claude

2,064,1209,011需要联网未明确有提醒
lark-workflow-standup-report

Lark 工作流程站立报告 · Codex、Claude

2,041,6328,978需要联网未明确通过
use-my-browser

使用我的浏览器 · Codex、Claude

1,848,49140操作浏览器未明确未通过
newsletter-creator

时事通讯创建者 · 本页

1,34148权限未标注未明确有提醒

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

SKILL.md 原文

name
newsletter-creator
description
Company newsletter and content roundup creation with consistent formatting, content curation, and audience segmentation. Use when creating internal newsletters, external digests, or content summaries.

Newsletter Creator

Structured frameworks for creating compelling internal and external newsletters with consistent quality, effective curation, and audience-appropriate tone.

Newsletter Structure

Standard Newsletter Sections

NEWSLETTER LAYOUT:

1. HEADER
   - Newsletter name / brand
   - Edition number and date
   - Tagline or theme for this edition

2. TL;DR / HIGHLIGHTS (above the fold)
   - 3-5 bullet summary of key items
   - Designed for scanners who won't read the full email
   - Each bullet links to the corresponding section

3. FEATURED STORY (1 item)
   - Primary content piece
   - 150-250 words with a clear takeaway
   - Supporting image or graphic
   - CTA: read more, watch, try

4. NEWS & UPDATES (3-5 items)
   - Brief summaries (50-100 words each)
   - Consistent format: headline, summary, link
   - Categorized if applicable

5. CURATED CONTENT (3-5 items)
   - Third-party articles, tools, or resources
   - Brief annotation explaining relevance
   - Source attribution

6. SPOTLIGHT SECTION (1 item, rotating)
   - Team member spotlight, customer story, tool tip
   - Rotates theme each edition
   - Personal and engaging

7. UPCOMING EVENTS / DATES
   - Relevant events, webinars, deadlines
   - Calendar format or simple list

8. FOOTER
   - Unsubscribe / manage preferences
   - Social media links
   - Feedback prompt ("Reply with your thoughts")
   - Archives link

Internal vs External Newsletter Differences

ElementInternal NewsletterExternal Newsletter
ToneCasual, transparent, team-orientedProfessional, value-driven
ContentCompany updates, wins, cultureIndustry insights, product updates
FrequencyWeekly or biweeklyWeekly, biweekly, or monthly
Length500-800 words300-600 words
CTAParticipate, recognize, feedbackRead more, try feature, register
MetricsOpen rate, survey feedbackOpen rate, CTR, conversions
PersonalizationBy team or departmentBy segment or interest

Content Curation Methodology

Curation Workflow

WEEKLY CURATION PROCESS:

COLLECT (ongoing throughout week):
- Save articles to curation tool (Pocket, Raindrop, Notion)
- Tag with categories and relevance score
- Note key quotes or takeaways
- Track sources for diversity

EVALUATE (1 day before send):
- Review all saved items
- Score each on: relevance, timeliness, quality, uniqueness
- Select top items per section
- Verify links still work
- Check for duplicates from prior editions

CURATE (writing day):
- Write brief annotations for each item (why it matters)
- Arrange in priority order
- Write featured story and transitions
- Add editorial perspective where appropriate

REVIEW (before send):
- Proofread all copy
- Test all links
- Preview in email client (desktop + mobile)
- Check accessibility (alt text, contrast)
- Send test to 2-3 reviewers

Content Scoring Matrix

CriterionWeight5 (Include)3 (Maybe)1 (Skip)
Relevance30%Directly applicableTangentially relatedOff-topic
Timeliness25%This week / breakingThis monthOld news
Quality20%Expert source, data-backedGood but genericListicle / fluff
Uniqueness15%Unlikely readers saw itModerately circulatedViral / everywhere
Actionability10%Clear takeaway or actionInformationalAbstract / theoretical
THRESHOLD:
  3.5+: Definite include
  2.5-3.4: Include if space permits
  < 2.5: Skip unless slow news week

Tone and Voice Guidelines

Voice Framework by Audience

INTERNAL NEWSLETTER VOICE:

Personality: Friendly colleague who's well-informed
Tone: Warm, transparent, sometimes playful
Language: First-person plural ("we"), casual contractions
Avoid: Corporate jargon, overly formal language, spin

EXAMPLE:
"Big week for the product team — they shipped the new
dashboard that's been in the works since Q3. If you haven't
tried it yet, you're missing out. Here's a quick walkthrough."

──────────────────────────────────────────────────────

EXTERNAL NEWSLETTER VOICE:

Personality: Trusted industry insider
Tone: Authoritative but approachable, value-focused
Language: Second-person ("you"), professional but not stiff
Avoid: Self-promotion overload, clickbait, assumptions

EXAMPLE:
"This week, three major shifts in the data infrastructure
space caught our attention. Here's what they mean for your
stack — and what to do about it."

Annotation Style Guide

CONTENT ANNOTATION FORMULA:

[HEADLINE] (linked)
[1-2 sentence summary of what it covers]
[1 sentence on why it matters to your audience]

EXAMPLE:
"The State of Developer Experience 2025" (link)
GitHub's annual report surveying 12,000 developers on tooling,
AI adoption, and workflow satisfaction. Worth reading for the
data on how teams are actually using AI coding assistants —
the gap between hype and reality is illuminating.

BAD ANNOTATION:
"The State of Developer Experience 2025" (link)
Check out this report from GitHub.

(No context, no why-it-matters, no reason to click)

Layout and Formatting Best Practices

Email Design Principles

FORMATTING RULES:

WIDTH:
- Max content width: 600px
- Single column preferred (reliable rendering)
- 2-column only for desktop-specific sections

TYPOGRAPHY:
- Body: 16px minimum (mobile readability)
- Headlines: 20-24px
- Line height: 1.5-1.6
- Font: System fonts or web-safe (Arial, Georgia, Helvetica)

IMAGES:
- Width: 100% of container (responsive)
- Alt text on every image
- File size: < 200KB per image
- Use sparingly — many clients block images by default

SPACING:
- Section dividers between major sections
- Generous padding (20px+) between items
- White space > cramped content

MOBILE:
- Test on iOS Mail, Gmail app, Outlook app
- Buttons: minimum 44x44px touch target
- Text should be readable without zooming
- Stack columns vertically on mobile

Template Structure (HTML)

EMAIL TEMPLATE SKELETON:

<!-- Preheader text (shows in inbox preview) -->
<!-- Max 150 chars, summarize key content -->

[HEADER: Logo + Edition Info]

[TL;DR BOX: 3-5 bullet highlights]

[DIVIDER]

[FEATURED STORY: Image + Text + CTA Button]

[DIVIDER]

[NEWS SECTION: 3-5 items, consistent format]

[DIVIDER]

[CURATED LINKS: 3-5 external items with annotations]

[DIVIDER]

[SPOTLIGHT: Rotating section]

[DIVIDER]

[EVENTS: Simple list or calendar]

[FOOTER: Unsubscribe, social, feedback]

Subject Line Optimization

Subject Line Formulas

PROVEN FORMATS:

CURIOSITY: "The one metric most teams get wrong"
NUMBER:    "5 things we learned shipping v3.0"
QUESTION:  "Is your CI pipeline costing you hours?"
NEWS:      "Big changes coming to [product] this quarter"
PERSONAL:  "[Name], your weekly engineering digest"
EMOJI:     "This week in product" (use sparingly, max 1)

CHARACTER LIMITS:
- Ideal: 30-50 characters
- Max: 60 characters (mobile truncation)
- Preheader: extend subject with 40-90 chars of context

A/B TEST PAIRS:
- Short vs. long
- Question vs. statement
- With emoji vs. without
- Specific vs. vague
- Personalized vs. generic

Subject Line Anti-Patterns

AVOID:
- ALL CAPS (looks like spam)
- Excessive punctuation (!!!)
- Misleading or clickbait subjects
- "Newsletter #47" (boring, no reason to open)
- Repeating the same format every week
- Overly long subjects that get truncated

Metrics and Performance Tracking

Key Metrics

MetricGoodAverageNeeds WorkAction
Open Rate> 40%25-40%< 25%Improve subject lines, send time
Click Rate> 5%2-5%< 2%Better CTAs, more relevant content
Click-to-Open> 15%8-15%< 8%Content quality, layout
Unsubscribe< 0.1%0.1-0.3%> 0.3%Frequency, relevance review
Reply Rate> 1%0.5-1%< 0.5%Add reply prompts, questions

Performance Review Template

MONTHLY NEWSLETTER REVIEW:

Edition Stats:
| Edition | Date | Open % | Click % | Unsub % | Top Link |
|---------|------|--------|---------|---------|----------|
| #47     |      |        |         |         |          |
| #48     |      |        |         |         |          |
| #49     |      |        |         |         |          |
| #50     |      |        |         |         |          |

Trends:
- Open rate trend: [up/down/flat]
- Best-performing content type: [___]
- Worst-performing content type: [___]
- Optimal send time (from data): [___]

Actions for Next Month:
- [ ] [specific improvement based on data]
- [ ] [content type to add or remove]
- [ ] [send time or frequency adjustment]

Content Calendar Integration

Editorial Calendar Template

MONTHLY CONTENT CALENDAR:

Week 1: [Theme / Focus]
- Featured: [topic]
- Curated: [2-3 planned sources]
- Spotlight: [team member / customer / tool]

Week 2: [Theme / Focus]
- Featured: [topic]
- Curated: [2-3 planned sources]
- Spotlight: [rotating section type]

Week 3: [Theme / Focus]
- Featured: [topic]
- Curated: [2-3 planned sources]
- Spotlight: [rotating section type]

Week 4: [Theme / Focus]
- Featured: [topic]
- Curated: [2-3 planned sources]
- Spotlight: [rotating section type]

RECURRING SECTIONS:
- Monthly: Industry roundup, metrics review
- Quarterly: Retrospective, reader survey
- Annual: Year in review, predictions

Frequency and Timing Recommendations

AudienceRecommended FrequencyBest Send DayBest Send Time
Internal (all-company)WeeklyMonday or Friday9-10 AM local
Internal (team)WeeklyMonday9 AM local
External (B2B)Weekly or biweeklyTuesday-Thursday10 AM ET
External (B2C)WeeklyTuesday or Saturday10 AM or 8 PM
Executive summaryMonthlyFirst Monday8 AM local

Newsletter Quality Checklist

CheckStatus
Subject line is compelling and under 60 chars[ ]
Preheader text adds context (not duplicate of subject)[ ]
TL;DR section captures key highlights[ ]
All links tested and working[ ]
Images have alt text[ ]
Mobile rendering tested[ ]
Tone matches target audience[ ]
Content is curated (not just aggregated)[ ]
Each item has a clear "why it matters"[ ]
Unsubscribe link present and functional[ ]
Send time optimized for audience[ ]
Proofread by at least one other person[ ]

See Also

平台分布

Codex

31.89%
按下载量换算150

Claude

31.12%
按下载量换算146

Cursor

17.92%
按下载量换算84

Gemini CLI

9.36%
按下载量换算44

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

权限未标注

当前来源未能明确判断权限范围,默认进入异常复核队列。

安装前确认

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

继续浏览同类 Skills