Communitygithub.com

amplitude/builder-skills

规划并制作产品发布所需的视频和视觉资产——演示视频、GIF、截图以及基于 Remotion 的程序化视频。任何需要创建演示视频、录制产品操作演示、制作发布 GIF、规划发布视觉资产或决定为公告制作何种媒体时,均可使用此技能。

builder-skills 是什么?

这是一个专注于产品发布视觉和视频资产创建的 AI 技能。它通过一个“媒体层级”来指导决策:优先考虑演示视频,其次是 GIF/循环录屏、带标注的截图,最后是图表或插图。该技能覆盖了从脚本撰写、平台特定的视频长度规范(如 Product Hunt 限 60-90 秒、Twitter 限 30-45 秒)、录制技巧到后期制作工具的全部流程。更重要的是,它深入介绍了如何利用 Remotion 进行程序化视频制作,这是一种将视频视为代码(基于 React 组件)的现代工作流,支持版本控制、参数化和快速迭代。技能还提供了详细的 GIF 优化、截图构图、Open Graph 图片制作以及按发布等级(Tier 1/2/3)的资产清单,确保开发者能系统性地为产品发布生成高质量、高影响力的媒体内容。

兼容平台~Claude Code~Codex CLI✓Cursor
npx skills add https://github.com/amplitude/builder-skills/tree/HEAD/launch-skills/skills/launch-video

在你喜欢的 AI 中提问

打开一个已预加载此 Agent Skill 的新对话。

文档

发布视频与视觉资产

此技能涵盖了产品发布所需的视觉和视频资产创建。这些是你将创建的最具影响力的资产——一个出色的演示视频或 GIF 能吸引注意力,比文字更快地传达价值,并易于传播。而一个糟糕的资产则可能让产品显得混乱或粗糙,从而削弱发布效果。

媒体层级

对于大多数发布活动,创建内容的决策通常遵循以下顺序:

  1. 演示视频 — 在上下文中展示产品功能。最适合解释工作原理。
  2. 动画 GIF 或屏幕录制循环 — 更短,可在社交媒体上自动内联播放。最适合展示特定交互。
  3. 带标注的截图 — 静态,制作迅速,适合展示特定状态或功能。
  4. 图表或插画 — 用于架构、概念或无法截图的场景。

一般来说:当流程重要时使用视频,当单个交互能传达价值时使用 GIF,当某个特定状态是关键时使用截图。

演示视频

各平台时长

平台目标时长硬限制
Product Hunt60-90 秒3 分钟
着陆页 Hero 区60-90 秒2 分钟
X/Twitter 嵌入式30-45 秒2 分 20 秒
LinkedIn45-90 秒10 分钟
YouTube(完整演示)3-5 分钟—

平台的硬限制不仅仅是技术上的——超过限制后用户参与度会急剧下降。一个 4 分钟的 Product Hunt 视频实际上等于没有视频。

脚本结构(适用于短格式演示)

保持 5-7 个节拍:

  1. 问题(5-10 秒)— 陈述要解决的问题。一句话,不要冗长的铺垫。
  2. 引入解决方案(5-10 秒)— 说出产品名称和核心价值主张。
  3. 演示:核心路径(30-60 秒)— 展示主要用例的端到端操作。这是视频的核心。
  4. 关键能力(10-20 秒)— 2-3 个快速切换,展示次要功能。保持节奏。
  5. 证明点(5-10 秒)— 一个指标、客户评价或基准。一页幻灯片或一句旁白。
  6. 行动号召(5 秒)— 一个行动。“在 [URL] 免费试用”或“在 [URL] 注册。”

避免:冗长的介绍、动画 Logo(用户会点击离开)、缓慢的产品启动画面以及任何不展示产品实际功能的内容。

录制技巧

  • 使用演示环境,而非生产环境。 使用干净的数据,避免尴尬的客户信息,状态可靠。
  • 放慢有目的性的交互。 比正常工作速度更刻意地移动鼠标,用户会更容易跟随光标轨迹。
  • 以 2 倍于目标分辨率录制。 以 2880×1800 或 1440×900(Retina)录制,然后向下缩放以供交付。这为你提供了缩放空间并使画面更清晰。
  • 隐藏所有无关内容。 关闭 Slack 通知,隐藏浏览器书签栏,使用干净的浏览器配置文件。录制中的干扰会损害信任感。
  • 录制内容多于实际使用量。 录制完整的工作流程并在后期剪辑。这比漏拍了一个节拍而重新录制要快得多。

旁白与静默

两种方式都可行。选择取决于上下文:

  • 旁白:更温暖,更具解释性,在 YouTube 和着陆页上效果更好。需要干净的录音环境和良好的音频质量。糟糕的音频比没有音频更糟糕。
  • 静默加文字覆盖:在自动播放且静音的上下文中(如社交信息流)效果更好。制作更快。需要清晰的屏幕标签。

如果不确定:先静默录制演示,为关键时刻添加文字覆盖,然后根据平台决定是否添加旁白。

工具

  • 屏幕录制:Loom(快速)、Screen Studio(输出精致,适合营销)、QuickTime(原始)、OBS(完全控制)
  • 视频编辑:CapCut(快速、简单)、DaVinci Resolve(专业、免费)、Final Cut Pro、Adobe Premiere
  • 动效设计/Logo 动画:After Effects、Motion(Mac)、Jitter(基于网页)
  • 字幕:Descript(也适合通过转录稿进行编辑)、Captions app、Rev
  • 程序化视频:Remotion(基于 React——参见下文章节)

使用 Remotion 的程序化视频

对于快速交付且不想每次都等待动效设计师的团队,程序化视频让你可以编写 React 组件并将其渲染为 MP4 文件。视频即代码:版本可控、可参数化且无需时间线编辑器即可迭代。

何时使用程序化视频

适合:

  • 用于社交媒体的发布公告短片(15-45 秒)
  • 展示 UI 交互的产品操作演示视频
  • 带有文字覆盖和截图的特色亮点集锦
  • 数据驱动型视频(基准对比、增长指标)
  • 可在多次发布中重复使用的模板化视频(只需替换内容)

不太适合:

  • 需要复杂动效设计的电影级品牌宣传视频
  • 包含真人实拍镜头的创始人叙事视频
  • 需要大量自定义插图或 3D 的视频

对于重要的 Tier 1 发布,你可以结合使用两种方法:用程序化视频制作社交短片,并聘请专业动效设计师制作主 Hero 视频。

Remotion 设置

npx create-video@latest my-launch-video
cd my-launch-video
npm start  # 打开 Remotion Studio 进行预览

关键概念:

  • Composition:一个具有定义时长(以帧为单位)和帧率的 React 组件
  • useCurrentFrame():返回当前帧编号的 Hook——用于驱动动画
  • Sequence:使其子元素在时间上偏移的组件——用于编排场景顺序
  • spring():用于产生自然运动感的动画实用工具(缓入/缓出)
  • 资产:图片、截图和音频文件放在 public/ 文件夹中

场景规划模板

在编写代码之前,逐场景规划视频:

字段描述
场景 #序号
时长秒数(例如 "3s")
目的此场景传达的信息(一句话)
文字内容屏幕上显示的确切文字
视觉元素截图、图标、代码片段、图表
动画风格淡入、从左滑入、打字机效果、放大等
转出效果场景如何退出(淡出、直接切换、滑动)

代码模式

编排场景序列:

<Sequence from={0} durationInFrames={90}>
  <HookScene />
</Sequence>
<Sequence from={90} durationInFrames={120}>
  <DemoScene />
</Sequence>
<Sequence from={210} durationInFrames={90}>
  <CTAScene />
</Sequence>

文字渐显:

const frame = useCurrentFrame();
const opacity = interpolate(frame, [0, 20], [0, 1], {
  extrapolateRight: 'clamp',
});

return <h1 style={{ opacity }}>你的主要价值主张</h1>;

迭代工作流

  1. 规划场景 — 使用上面的模板
  2. 收集素材 — 截图、Logo、产品图片 → public/ 文件夹
  3. 编写或提示初稿 — 确保结构和内容正确
  4. 在 Studio 中预览 — 完整观看,注意时机和视觉问题
  5. 迭代 — 调整时机、动画和内容。通常需要 2-4 轮
  6. 渲染 — npx remotion render src/index.ts MyComposition out/video.mp4
  7. 检查平台规格 — 验证分辨率和文件大小是否满足目标平台要求

GIF 和短视频循环

GIF 在大多数平台上自动播放,非常适合展示单个交互——UI 状态变化、CLI 命令输出、API 响应。它们比视频制作更快,在社交媒体帖子上通常更有效。

何时使用 GIF 与视频

使用 GIF 当:

  • 全部价值可以在 3-8 秒内传达完成
  • 你展示的是一个单一的 UI 交互,而非一个工作流程
  • 该资产将嵌入推文或 README 中,而视频播放可靠性较低

使用视频当:

  • 价值需要上下文(问题 → 解决方案)
  • 交互演示需要超过 8 秒
  • 你需要音频

录制 GIF

  • 以 2x 分辨率录制,向下缩放到目标分辨率
  • 保持在 5MB 以下以保证网页性能(使用调色板缩减或更少的帧数)
  • 无缝循环 — 起始和结束状态应匹配,避免循环时有跳跃感
  • 工具选项:CleanShot X(Mac 推荐)、Kap、Giphy Capture、Gifski(用于转换视频片段)

优化 GIF 文件大小

  • 减少调色板(对于许多 UI 录制,256 色 → 128 或 64 色)
  • 降低帧率(UI 录制中 30fps → 15fps 通常不明显)
  • 积极裁剪——只显示变化的部分,而非整个屏幕
  • 当平台支持时,转换为带有自动播放/循环的 MP4 来代替 GIF(MP4 比同等 GIF 小约 10 倍)

截图

截图在发布中未被充分利用。一张构图良好且标注清晰的截图传达功能的速度比一段文字快。

构图

  • 展示产品处于有意义的状态 — 不要是空屏、加载状态或充满难以看清功能的虚拟数据的屏幕
  • 使用干净的环境 — 无标签的浏览器、一致应用暗色或亮色模式、无可见的个人数据
  • 高亮相关区域 — 使用标注框、箭头或高亮来引导注意力到关键内容

标注工具

  • CleanShot X (Mac) — 在一个工作流程中完成捕获、标注和导出
  • Skitch — 简单标注
  • Figma / Sketch — 用于更精致的产品展示图,支持自定义样式

浏览器框架

对于 Web 产品,使用浏览器框架使截图看起来是经过精心设计的,而非原始截图。像 Screely、Browserframe 或自定义 Figma 模板等工具可以添加浏览器外壳叠加层。

功能网格的多个截图

着陆页和 Product Hunt 画廊通常需要 3-5 张展示产品不同方面的截图。将它们作为一组来规划:

  • 每张截图展示一个独特的能力
  • 一致的视觉处理(相同的缩放级别、相同的浏览器主题、相同的标注样式)
  • 讲述一个递进过程:入口 → 关键操作 → 结果

按发布等级划分的资产清单

Tier 1

  • 演示视频(60-90 秒,适用于 Product Hunt 和着陆页)
  • 社交短片(从同一录制中剪辑的 30-45 秒版本)
  • 3-5 张带标注的截图(用于着陆页和 Product Hunt 画廊)
  • 1-2 个 GIF(用于社交媒体帖子,展示关键交互)
  • Open Graph 图片(用于博客文章和社交链接预览)

Tier 2

  • 1-2 个 GIF 或短屏录制
  • 2-3 张截图(用于着陆页区块)
  • Open Graph 图片

Tier 3

  • 1 张截图
  • 可选:如果是视觉变化,添加短 GIF

Open Graph 图片

每篇以链接形式分享的内容(博客文章、着陆页、更新日志条目)都应有一张自定义的 Open Graph (OG) 图片。当链接被粘贴到 Twitter、Slack、iMessage 或 LinkedIn 时,显示的就是 OG 图片。

  • 尺寸:1200×630px
  • 内容:产品名称 + 主要价值主张。像对待广告牌一样对待它——在较小的尺寸下也应可读
  • 一致性:使用模板,使你所有的发布内容具有统一的视觉效果
  • 工具:Figma 模板、Vercel OG(代码生成)、Bannerbear(自动化)

各平台视频规格

平台分辨率最大时长格式备注
X/Twitter1280×720 或 1920×10802:20MP4 (H.264)自动静音播放——需添加字幕
LinkedIn1920×108010 分钟MP4 (H.264)信息流中方形 (1080×1080) 效果很好
Product Hunt1920×108090 秒MP4保持在 50MB 以下
网站 Hero 区1920×1080无限制MP4/WebM考虑自动播放循环(无音频)

配套技能

  • launch-strategy — 确定发布等级所需的资产
  • launch-tweet — GIF 和视频作为附件(而非链接)放入推文中
  • launch-landing-page — 演示视频和截图放置在页面上
  • launch-distribution — 各平台的格式要求

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

amplitude/builder-skills

Performs deep analysis of a specific Amplitude chart to explain trends, anomalies, and likely drivers. Use when a metric looks unusual, investigating a spike or drop, or understanding the "why" behind numbers.

amplitude/builder-skills

Deeply analyze Amplitude dashboards by analyzing key charts, surfacing top areas for concern and takeaways, identify anomalies, then explain changes using customer feedback trends.

amplitude/builder-skills

Designs A/B tests with proper metrics and variants, analyzes running or completed experiments, and interprets results with statistical rigor. Use when setting up experiments, checking experiment status, analyzing results, or making ship decisions.

amplitude/builder-skills

Synthesizes customer feedback into actionable themes including feature requests, bugs, pain points, and praise. Use when planning product roadmap, understanding user sentiment, investigating specific issues, or preparing voice-of-customer reports.

amplitude/builder-skills

Analyze MCP server usage instrumented with Amplitude's MCP Analytics SDK: break usage and errors down by tool, read the rationales within each tool to see what callers are trying to do, and produce a prioritized write-up of actionable fixes. Use this skill whenever the user asks to understand how their MCP server is being used, what agents/users are trying to do with it, why tool calls are failing, what to fix or improve in their MCP server, or asks for an "MCP usage report", "tool error analysis", "intent analysis", "rationale clustering", or "MCP insights". Also trigger when the user mentions [MCP]-prefixed events, tool rationale, tool call errors, or just finished instrumenting their MCP server and wants to see what the data says. Requires the Amplitude MCP connector.

amplitude/builder-skills

Read lost deals and churned accounts from your CRM, extract reasons clustered by theme (missing features, pricing, competitors, UX), and write a prioritized weekly analysis with product improvement recommendations. Use before roadmap planning or to build the case for prioritizing retention work.

amplitude/builder-skills

Creates Amplitude charts from natural language descriptions, handling event selection, filters, groupings, and visualization choices. Use when you know what you want to measure but prefer not to build the chart manually.

amplitude/builder-skills

Guide an Amplitude user through building a custom agent by suggesting use cases grounded in their role and data, shaping the idea into a well-formed spec, and generating a ready-to-run Global Agent deeplink that creates it. Use to create, build, or set up a custom agent, automate a recurring analysis, or put a repeated report on a schedule.

amplitude/builder-skills

Builds comprehensive Amplitude dashboards from requirements or goals, organizing charts into logical sections with appropriate layouts. Use when creating a complete dashboard from scratch or assembling existing charts into a cohesive view.

amplitude/builder-skills

Monitors all active and recently completed experiments across Amplitude projects, triages them by importance, then runs deep analysis and reporting on the most impactful ones. Use when the user asks to "check on experiments", "experiment status", "experiment review", "what experiments are running", or wants a periodic experiment health report.

amplitude/builder-skills

Pull Intercom tickets and Slack support messages from the past 7 days, classify each signal, enrich with CRM data (ARR, plan, renewal), score by customer value and churn risk, and output a tiered priority report saved to Drive. Use when you need a fast, data-driven view of what support signals matter most.

amplitude/builder-skills

Use this skill whenever a user wants to improve existing pages on their website to get cited more by AI models — whether they say "our pages aren't getting cited", "improve this page for AI visibility", "which of our pages should we update", "make this article more cite-worthy", "our competitors are getting cited instead of us", "update our content for AI search", or any variation where the goal is improving an existing asset rather than creating something new. This skill pulls owned pages from AI Visibility, identifies which ones have citation potential but are underperforming, compares them against the external pages that are winning citations on the same topics, and produces section-level rewrites or a full-page update — then pushes the revision to the CMS as a draft. Trigger even if the user just says "help me get cited more" or "why is [competitor] getting cited instead of us".

amplitude/builder-skills

Use this skill whenever a user wants to win AI citations on prompts that competitors currently dominate — whether they say "competitors are getting cited instead of us", "we're losing on these prompts", "how do I outrank [competitor] in AI answers", "find prompts where we should be winning", "create content to beat [competitor]", or any variation where the goal is capturing AI share on prompts a competitor currently owns. This skill pulls competitor visibility data from AI Visibility, identifies the specific prompts where competitors win and Amplitude is absent, clusters them by intent, and produces targeted comparison pages, alternatives content, or rebuttal assets — then pushes drafts to CMS. Trigger on any mention of competitor, prompt hijack, outrank, or "why is [competitor] getting cited instead of us".

amplitude/builder-skills

Use this skill whenever a user wants to turn AI Visibility data into published content — whether they say "find content gaps", "what should we write about", "which topics have low visibility", "help me get cited by AI models", "create a blog post from our AI Visibility gaps", "we're losing to competitors on these prompts", or any variation where they want to go from AI visibility weakness to a draft article, landing page, or FAQ. This skill connects directly to Amplitude AI Visibility data (topics, prompts, visibility scores, citations, competitor data, full LLM responses and sources) and produces a publish-ready content brief plus full article draft. If the user mentions CMS (WordPress, Webflow, Contentful, Sanity, HubSpot, Ghost, Shopify), also trigger this skill to push the draft directly. Trigger even if they just say something vague like "what content should we create?" in an AI Visibility context.

amplitude/builder-skills

Use this skill whenever a user wants to test content variants before publishing to find which one will get cited most by AI models — whether they say "which version of this content will perform better", "test this article before we publish", "simulate how AI will respond to this content", "which angle should we use", "generate content variants and pick the winner", "run a simulation before publishing", or any variation where the goal is data-driven content selection rather than gut-feel publishing. This skill takes an identified content opportunity, generates 2–3 distinct variants with different angles or structures, scores them against actual AI model responses from AI Visibility, references the Simulate Changes feature for pre-publish validation, and produces a clear recommendation on which variant to publish — then pushes the winner to CMS. Trigger on any mention of "simulate", "test variants", "which performs better", "A/B content", or "before we publish".

amplitude/builder-skills

Use this skill whenever a user wants to understand which external sources are being cited by AI models on topics relevant to their brand, and wants to create content that will outrank those sources — whether they say "what sources are AI models citing", "why is [third-party site] being cited instead of us", "we want to be the definitive source on X", "build something that gets cited more than G2 or TechRadar", "create an authoritative asset", or any variation where the goal is producing a new reference asset (definition page, benchmark, methodology, glossary, comparison hub) designed to beat existing top-cited sources. This skill analyzes AI Visibility source data, reverse-engineers what makes top-cited pages authoritative, and produces a superior source asset — then pushes it to CMS as a draft. Trigger on any mention of "sources", "third-party citations", "authoritative content", "definitional pages", or "outrank".

amplitude/builder-skills

Instrument a Node/TypeScript MCP server with Amplitude's @amplitude/mcp-analytics SDK so tool calls, sessions, and rationale are tracked as Amplitude events. Use this skill whenever the user wants to add Amplitude analytics to their MCP server, mentions "MCP Analytics", "@amplitude/mcp-analytics", "instrument my MCP server", "track MCP tool calls", "add rationale to my MCP tools", or wants agent traffic (Claude, Cursor, ChatGPT) attributed back to Amplitude. Also use for adding UTM tagging to MCP-returned links, or for troubleshooting identity/user_id mismatches between MCP events and web/mobile Amplitude data.

amplitude/builder-skills

Instruments a pull request with Amplitude analytics that conform to the project's existing taxonomy. Reads the tracking plan via the Amplitude MCP server (events, properties, naming conventions), analyzes the PR diff to find the few user actions genuinely worth tracking, detects the codebase's SDK and tracking patterns, and adds instrumentation that matches both. Optionally (opt-in) stages new events and properties on an Amplitude tracking-plan branch for data-governance review. Use when asked to "instrument this PR", "add analytics to this change", "add tracking", "add Amplitude events", "instrument this feature", or "what should I track here".

amplitude/builder-skills

Diagnoses product health by cross-referencing Amplitude analytics (dashboards, charts, funnels, feedback, AI agent analytics), optionally Datadog (errors, latency, stack traces), and optionally Slack (qualitative feedback, bug reports, feature requests). Identifies what's broken, what's working, and what to do about it — with root causes, not just symptoms. Use when asked to "diagnose my product", "what's going on", "product health check", "what's broken", "where are users struggling", "give me a product diagnosis", or "what should I focus on".

amplitude/builder-skills

Summarizes B2B account health by analyzing usage patterns, engagement trends, risk signals, and expansion opportunities. Use for customer success reviews, renewal preparation, QBRs, or account prioritization.

相关技能