Token导航 LogoToken导航

Agent Skill · 研究检索

newsletter-to-video(新闻通讯到视频)

用于辅助视频生成、动画合成、脚本化剪辑或 Remotion 等视频项目开发。它适合让 Agent 组织镜头、生成素材说明、维护合成代码或排查渲染问题。使用时需要确认分辨率、时长、素材路径和导出格式;涉及外部素材、人物肖像或商业发布时,应先核对版权授权和内容审核要求。

newsletter-to-video 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 49,058。

总安装 665周安装 28GitHub Stars 124下载 233核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:newsletter-to-video(新闻通讯到视频)
来源仓库:https://github.com/kenneth-liao/ai-launchpad-marketplace
仓库路径:skills/newsletter-to-video
安装命令:
npx skills add https://github.com/kenneth-liao/ai-launchpad-marketplace --skill newsletter-to-video
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/kenneth-liao/ai-launchpad-marketplace --skill newsletter-to-video

这个 Skill 是做什么的

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

newsletter-to-video 用于辅助视频生成、动画合成、脚本化剪辑或 Remotion 等视频项目开发,适合让 Agent 组织镜头、生成素材说明、维护合成代码或排查渲染问题。适用于视频制作、动画开发、多媒体内容创作等研究检索类任务场景。

通过 npx skills add 命令从指定 GitHub 仓库安装,需确认权限范围和联网需求。安装前建议核实维护状态、是否会触发命令执行或文件读写操作。可结合原始 README 文档进一步核验具体功能和使用方法。

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

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

newsletter-to-video 怎么安装?

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

newsletter-to-video 支持哪些 AI 工具?

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

newsletter-to-video 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

newsletter-to-video 是免费的吗?

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

newsletter-to-video 用的人多吗?

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

newsletter-to-video 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 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-to-video

新闻通讯到视频 · 本页

665124只读未明确通过

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

SKILL.md 原文

Newsletter to YouTube Video Outline

Repurpose a newsletter issue into a high-level YouTube video outline. The output is topic-level only — no scripts, no talking points, no actual content. Just the topics you'll cover, structured for video.

Why This Exists

Newsletter and YouTube are different mediums. Newsletters reward scanners — readers jump to what interests them. YouTube rewards retention — viewers watch linearly, and every moment competes with the back button. A straight 1:1 port of newsletter structure usually makes for a boring video. This skill restructures the content to match how people actually watch.

When to Use

Use this skill when:

  • Converting a newsletter issue into a YouTube video plan
  • The user asks to repurpose newsletter content for YouTube
  • Planning a video based on an existing newsletter issue
  • The user mentions "video outline from newsletter" or similar

Process

digraph newsletter_to_youtube {
    "Read newsletter issue" [shape=doublecircle];
    "Extract core topics" [shape=box];
    "Identify the tension" [shape=box];
    "Drop non-video sections" [shape=box];
    "Reorder for retention" [shape=box];
    "Generate hook via skill" [shape=box, style=bold];
    "Structure the outline" [shape=box];
    "Present to user" [shape=doublecircle];

    "Read newsletter issue" -> "Extract core topics";
    "Extract core topics" -> "Identify the tension";
    "Identify the tension" -> "Drop non-video sections";
    "Drop non-video sections" -> "Reorder for retention";
    "Reorder for retention" -> "Generate hook via skill";
    "Generate hook via skill" -> "Structure the outline";
    "Structure the outline" -> "Present to user";
}

Step 1: Read the Newsletter Issue

Read the full newsletter issue. Identify:

  • The core thesis (what's the one main idea?)
  • All distinct topics/subtopics covered
  • The most surprising or counterintuitive finding
  • Any limitations, trade-offs, or honest takes (these create tension)
  • Personal experience and real results (these build credibility on camera)

Step 2: Adapt for Video

Drop these — they don't translate to video:

  • P.S. lines and email-specific CTAs (forward, reply)
  • Preview text / subtitle
  • Subject line options
  • "Getting started" setup sections (install steps, config JSON) — unless the video is a tutorial
  • Sections that only work as scannable text (comparison tables can become talking points, but raw tables don't work on screen)

Promote these — they work better on video than in text:

  • Personal stories and anecdotes (these are gold on camera)
  • Surprising findings or limitations (great for hooks and retention)
  • Before/after comparisons (visual, easy to demonstrate)
  • Live demos or walkthroughs (newsletter screenshots become video demos)

Reorder for retention:

YouTube viewers decide to stay or leave in the first 30 seconds. The newsletter hook might work as-is, but often the most interesting finding is buried in the middle or end of the newsletter. Pull it forward.

Newsletter patternVideo adaptation
Hook → Context → Content → Limitation → CloseHook with the limitation → Why it matters → How it works → Limitation deep-dive → What's next
Hook → Problem → Solution → How-to → CloseHook with the result → The problem → The solution → Quick demo → What's next
Hook → Feature overview → Cost → Limitations → CloseHook with the tension (cost/limitation) → What it does → How it actually works → The honest trade-offs → Verdict

The general principle: lead with tension or surprise, deliver value in the middle, end forward-looking. Tension is what keeps viewers watching. The newsletter can afford a slow build because readers scan ahead. Video can't.

Step 3: Generate the Hook

Invoke creator-stack:hook to craft the video's opening hook.

Feed the skill this context from Steps 1–2:

  • The working title (or a placeholder title describing the video topic)
  • The most surprising or counterintuitive finding from the newsletter — this is almost always the best hook material
  • The core tension (limitation, trade-off, honest take) identified in Step 1
  • The content type (YouTube video) so the skill loads references/youtube-hooks.md

The skill will produce a hook that:

  • Extends curiosity beyond the title (doesn't just repeat it)
  • Lands within 5–15 seconds
  • Avoids forbidden patterns (title repetition, welcome-first, unrelated tangent)
  • Passes its own 7-point verification checklist

Include the skill's hook output in the outline's Hook section. The hook should be 2–3 sentences: what the viewer sees/hears and why it creates urgency to keep watching.

Step 4: Build the Outline

Structure every outline with these sections. The Hook section comes from Step 3. The rest is topic-level only — 1-2 lines per section, not actual content.

## Hook (0:00–0:15)
[Generated by creator-stack:hook skill — 2-3 sentences
describing the opening: what the viewer sees/hears, the hook pattern used,
and the curiosity it creates]

## Setup
[What context the viewer needs to understand the rest — 1 sentence]

## Main Topics
[Each topic as a bullet — just the topic name and what aspect of it you'll cover]
- Topic 1: ...
- Topic 2: ...
- Topic 3: ...
[Usually 3-5 topics. More than 5 means the video is trying to cover too much.]

## Close
[How the video wraps — what the viewer should take away or do next]

Keep it tight. The outline for a 10-minute video should fit in under 15 lines (excluding the hook). If you're writing more than that, you're going past topic-level into content territory.

Output Format

Present the outline as a single markdown block. Use the template structure above. No commentary outside the outline unless the user asks for it.

If a newsletter issue covers too many topics for one video, say so and suggest splitting into 2 videos with a recommended split point — but still produce the outline for the primary video.

Brand Compliance

When creating video outlines for The AI Launchpad, invoke creator-stack:brand-guidelines to verify the hook and outline align with brand standards.

Quality Checklist

Verify completion before finalizing:

  • Newsletter issue fully read and core thesis identified
  • Non-video sections dropped (P.S., subject lines, setup steps)
  • Video-friendly elements promoted (stories, demos, surprises)
  • Content reordered for retention (tension/surprise leads)
  • creator-stack:hook invoked for hook generation
  • Hook passes the skill's 7-point verification checklist
  • Outline uses the template structure (Hook → Setup → Main Topics → Close)
  • 3-5 main topics (not more)
  • Each topic is a label + angle, not talking points
  • Outline fits under 15 lines (excluding hook)

Common Mistakes

MistakeFix
Writing talking points instead of topicsEach bullet should be a topic label + angle, not what you'd say about it
Mirroring the newsletter order exactlyReorder — lead with whatever creates the most tension or curiosity
Including 7+ main topicsPick 3-5. A focused video outperforms a comprehensive one.
Keeping email-specific sectionsDrop P.S., subject lines, reply CTAs — they don't exist in video
Writing the hook inline instead of using the skillInvoke creator-stack:hook — it catches forbidden patterns you'll miss
Generic hook ("Today we're going to talk about...")The hook skill will prevent this — feed it the tension/surprise and let it pick the right pattern
Forgetting the closeEvery video needs a clear ending — verdict, next steps, or a forward look

平台分布

Codex

34.52%
按下载量换算80

Claude

27.82%
按下载量换算65

Cursor

18.8%
按下载量换算44

Gemini CLI

9.22%
按下载量换算21

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

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

继续浏览同类 Skills