Communitygithub.com

amplitude/builder-skills

为产品发布活动撰写发布推文、公告帖以及跨平台社交媒体内容(支持 X/Twitter、LinkedIn、BlueSky 和 Threads)。每当有人要求编写发布推文、起草公告帖、为产品发布撰写社交媒体文案,或为不同平台改编发布消息时,均可使用此技能。

builder-skills 是什么?

该技能专注于为产品发布生成高效的社交媒体公告文案。它提供了一套完整的撰写流程与方法论,指导用户如何写出在 X/Twitter、LinkedIn、BlueSky 和 Threads 等平台上能够“抓住眼球、传递价值、推动行动”的发布内容。技能不仅涵盖了单条推文的结构与规则(例如:首行必须直击价值、必须附带媒体、禁止在首条内放链接),还深入讲解了多推文线程的编排原则(5-8条推文为最佳长度、每条推文需独立提供价值)。更重要的是,它强调了跨平台适配的关键差异:X 平台要求简洁有力、视觉优先;LinkedIn 适合篇幅更长、叙事性更强的 B2B 内容;BlueSky 风格接近 X 但受众更技术化;Threads 则需要更轻松、对话式的语态。此外,技能还包含了完整的文案撰写工作流(从信息简报开始,到写推特版本再扩展到线程,最后适配其他平台),以及常见错误清单(如首条链接、无媒体、堆砌废话)。对于任何需要快速高效生成产品发布社交文案的开发者或产品团队来说,这是一套非常实用的指南。

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

在你喜欢的 AI 中提问

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

文档

发布推文

此技能帮助为产品发布撰写社交媒体公告。其原则因平台而异——在 X 上有效的文案,直接复制粘贴到 LinkedIn 上就行不通——但核心目标一致:吸引目光,传递价值,驱动行动。

单条发布推文

单条推文是你最重要的发布资产。即使你要发布一个完整线程,这条推文也必须能独立发挥作用,因为大多数用户只会看到它。

结构

[强有力的首行 —— 你发布了什么,以价值为导向表述]

[1-2 句话展开说明它的功能/重要性]

[媒体:视频、GIF 或截图 —— 直接附加,非链接]

规则

  1. 首行承担所有工作。 必须让人清楚你在发布什么东西,以及别人为什么要在意。避免使用“很激动地宣布”或“经过数月的努力” —— 直接从产品价值切入。

  2. 首条推文附带媒体。 始终如此。带有视频或图片的推文相比纯文本能获得显著更高的互动率。直接附加媒体 —— 不要链接到 YouTube 或外部页面。

  3. 首条推文中不要放链接。 平台算法会惩罚外部链接。把你的链接放在回复或线程的第二条推文中。如果必须包含链接且希望显示预览卡片,请确保整条推文(包括 URL)不超过 280 个字符。

  4. 具体性胜于空洞的炒作。 “现在你可以用 5 行代码构建语音应用” 比 “革命性的新 API” 更吸引人。数字、具体用例和前后对比能有效“抓住眼球”。

示例

好的首行:

  • “隆重介绍 [产品]: [产品的具体功能]”
  • “[产品] 现在支持 [具体能力]。这意味着什么 →”
  • “你现在可以用 [产品] [执行某个操作]。无需再 [之前的痛点]。”
  • “我们刚刚发布了 [功能]。 [一行证明点或结果]。”

弱的首行(避免使用):

  • “兴奋地宣布...” (埋没了价值)
  • “经过数月的努力...” (没人在乎你的时间线)
  • “线程 🧵” (被算法惩罚,不提供价值)
  • “重大消息!” (空洞的炒作)

发布线程

线程适用于一级发布和一些二级发布,前提是你有足够的内容填充 4-8 条推文而不显得冗余。

线程结构

推文 1:钩子 与单条推文的规则相同。必须能独立发挥作用。包含你最好的媒体(视频或关键截图)。不放链接。

推文 2-4:价值主张与证明 每条推文覆盖一个价值主张或证明点。包含支持性媒体——截图、GIF、简短演示片段。每 2-3 条推文设置一个视觉间隔,让用户保持滚动。

推文 5-7(可选):社会证明或用例 客户评价、基准测试、对比、示例用例。这是让价值具体化的地方。

最后一条推文:行动号召 + 链接 链接放在这里。明确点击后会发生什么:“免费试用 →”、“查看文档 →”、“观看完整演示 →”。

线程原则

  • 5-8 条推文是发布内容的最佳长度。超过 15 条的线程,参与度会急剧下降。
  • 每条推文必须独立提供价值。 用户会在每条推文时流失——不要到最后一条才揭示重点。
  • 视觉间隔很重要。 交替使用文字密集型与媒体密集型推文。
  • 不要有水分的推文。 如果你无法用实质内容填满 5 条推文,那就只发单条。

跨平台适配

同一则公告在不同平台上需要不同的处理方式。不要简单复制粘贴。

X/Twitter

  • 简洁有力、视觉优先
  • 较大发布可采用线程格式
  • 标签:少用(最多 1-2 个),或直接跳过
  • 最佳互动时间:早晨和午后(依受众而定)

LinkedIn

  • 篇幅更长、叙事性更强
  • 以钩子开头,但可以比 X 更富有上下文
  • 适合 B2B 发布和技术产品
  • 每 3-5 行加入换行以提高可读性(LinkedIn 会在约 3 行后截断,因此前 3 行必须赢得“查看更多”点击)
  • @提及相关人员和公司
  • 不要堆砌标签——最多 3 个,放在末尾

BlueSky

  • 格式和语气与 X 相似
  • 受众稍微更偏向技术/小众(截至 2025-2026 年)
  • 线程在这里效果也不错
  • 算法放大作用较小——更依赖社区分享

Threads

  • 更随意、对话式的语气
  • 较短的帖子通常效果更好
  • 从 Instagram 交叉发布有助于分发
  • 受众不那么侧重商业/技术——应面向更广泛的吸引力

Hacker News

  • 不是社交媒体意义上的“帖子”——它是带有标题的提交
  • 标题应实事求是且具体,避免炒作:“Show HN: [产品] – [白话说明它的功能]”
  • 讨论线程比提交本身更重要
  • 准备好诚实且详细地回答技术问题
  • 不要要求别人点赞——会适得其反

撰写流程

在起草发布社交媒体文案时,遵循以下顺序:

  1. 从信息简报开始(来自 launch-strategy)。如果没有简报,请询问:产品/功能名称、目标受众、主要价值主张、以及 2-3 个次级价值主张。

  2. 先写 X/Twitter 版本。 字符限制迫使你清晰表达。如果价值主张连一条推文都放不下,说明消息还不够锐利。

  3. 扩展为线程(如果发布值得的话——一级发布或规模较大的二级发布)。将每个次级价值主张映射到一条推文。

  4. 适配其他平台。 LinkedIn 获得更多上下文和叙事。BlueSky 保持简洁。Hacker News 使用事实性的标题。

  5. 起草多个首行选项。 首行是杠杆率最高的句子。写 3-5 个变体,选择最能平衡清晰度、具体性和抓眼球能力的那个。

常见错误

  • 在首条推文中放链接。 会降低覆盖。总是把链接放在回复或线程后面。
  • 没有媒体。 纯文本的发布推文效果远远不如。即便只是一张截图也比没有好。
  • 埋没价值。 用三句开场白铺垫才说发布了什么。直接以产品开头。
  • 到处用相同的文案。 每个平台有不同的规范。复制粘贴显得懒惰且效果差。
  • 线程注水。 如果你只是为了让线程更长而添加推文,删除它们。短而强胜过长而稀。
  • 忘记行动号召。 每篇发布帖子都需要给读者一个清晰的下一步。你希望他们做什么?

配套技能

  • launch-strategy —— 为社交媒体文案提供信息简报
  • launch-email —— 邮件主题行遵循与推文相同的“首行”技巧
  • launch-video —— 放在推文中的演示视频或 GIF(直接附加,非链接)
  • launch-distribution —— 何时何地发布,以及如何放大
  • launch-metrics —— 通过 UTM 追踪哪些社交媒体帖子带来了注册

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.

相关技能