Communitygithub.com

amplitude/builder-skills

為產品發佈撰寫啟動推文、公告串以及跨平台社交貼文(X/Twitter、LinkedIn、BlueSky、Threads)。當有人要求為產品發佈撰寫推文、草擬公告串、建立社交行銷文案,或將發佈訊息轉化為不同平台版本時,請使用此技能。

builder-skills 是什麼?

此技能專門用於為產品發佈撰寫高轉化的社交媒體貼文。它提供一套平台感知的寫作框架,涵蓋單一推文、推文串以及跨平台(X/Twitter、LinkedIn、BlueSky、Threads、Hacker News)文案改寫。核心原則是「第一行決定成敗」——推文的第一行必須直接呈現產品價值,避免空洞的開場白。技能強調在首條推文內附上媒體(圖片或影片),且不放入外部連結,以避免演算法降權。對於較大型的發佈,技能提供標準推文串結構(掛鉤、價值主張、社會證明、行動呼籲),並建議5-8則推文為最佳長度。此外,技能還包含各平台的專屬寫作提示:LinkedIn需使用3-5行換行以爭取「查看更多」點擊;BlueSky適合技術性與社群分享;Threads則需更輕鬆的語氣。Hacker News的提交應以事實性標題為主,並準備好回答技術問題。整個寫作流程從訊息簡報開始,先寫X/Twitter版本以強制訊息精煉,再擴展為推文串,最後針對其他平台改寫。常見錯誤包括在首條推文放連結、缺乏媒體、埋沒價值以及在不同平台貼相同文案。此技能可與其他發佈技能(如launch-strategy、launch-email、launch-video)搭配使用,形成完整的產品發佈流程。

相容平台~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. 第一條推文不要放連結。 平台演算法會懲罰外部連結。將連結放在回覆中或推文串的第二條。如果必須包含連結且希望預覽卡能正常顯示,請確保整條推文(包括網址)少於 280 個字元。

  4. 具體優於誇大。 「現在你可以用 5 行程式碼建立語音應用」勝過「革命性的新 API」。數字、具體使用案例和對比能有效抓住目光。

範例

好的第一行:

  • 「隆重介紹 [產品]:[它具體做什麼]」
  • 「[產品] 現在可以 [特定功能]。以下是這個意義 →」
  • 「你現在可以透過 [產品] [執行某動作]。不再需要 [先前的痛點]。」
  • 「我們剛剛推出了 [功能]。[一行證明或結果]。」

弱的第一行(避免):

  • 「興奮地宣佈...」(埋沒價值)
  • 「經過數月的努力...」(沒人在乎你的時程)
  • 「Thread 🧵」(受演算法懲罰,提供零價值)
  • 「重大消息!」(空洞的誇大)

發佈推文串

推文串適用於 Tier 1 以及某些 Tier 2 的發佈,前提是內容豐富到足以填充 4-8 則推文而不顯空洞。

推文串結構

推文 1:掛鉤 規則與單一推文相同。必須能獨立運作。包含最好的媒體(影片或關鍵截圖)。不放連結。

推文 2-4:價值主張與證明 每則推文涵蓋一個價值主張或證明點。包含輔助媒體——截圖、GIF、簡短示範影片。每 2-3 則推文插入視覺中斷,讓讀者保持滾動。

推文 5-7(可選):社會證明或使用案例 客戶引述、基準測試、比較、範例使用案例。這裡讓價值變得具體。

最後推文:行動呼籲 + 連結 這是放連結的地方。具體說明他們點擊後會發生什麼:「免費試用 →」、「查看文件 →」、「觀看完整示範 →」。

推文串原則

  • 5-8 則推文是發佈內容的最佳長度。 超過 15 則的推文串互動會明顯下降。
  • 每則推文都必須獨立提供價值。 讀者會在每一則推文處流失——不要等到第 7 則才揭曉重點。
  • 視覺中斷很重要。 在文字密集與媒體密集的推文之間交替。
  • 不要有填充的推文。 如果你無法用實質內容填滿 5 則推文,那就只寫一條單一推文。

跨平台改寫

同一個公告在不同平台需要不同的處理方式。不要直接複製貼上。

X/Twitter

  • 簡潔、有力、視覺優先
  • 較大發佈使用推文串格式
  • 主題標籤:謹慎使用(最多 1-2 個)或完全省略
  • 最佳互動時機:早上和下午早些時候(依受眾而異)

LinkedIn

  • 較長篇幅,更具敘事性
  • 以掛鉤開場,但可以比 X 更有背景說明
  • 適合 B2B 發佈和技術產品
  • 包含 3-5 個換行以提高可讀性(LinkedIn 會在大約 3 行後截斷,所以前 3 行必須贏得「查看更多」的點擊)
  • 標記相關人士和公司
  • 不要堆砌主題標籤——最多 3 個,放在結尾

BlueSky

  • 在格式和語氣上類似於 X
  • 受眾稍微偏向技術/小眾(截至 2025-2026)
  • 推文串在此效果良好
  • 演算法放大效果較弱——更多依賴社群分享

Threads

  • 更輕鬆、對話式的語氣
  • 較短的貼文通常效果更好
  • 從 Instagram 交叉貼文有助於分發
  • 受眾較少商業/技術背景——以更廣泛的吸引力為框架

Hacker News

  • 不是社交媒體意義上的「貼文」——而是帶有標題的提交
  • 標題應基於事實且具體,不要誇大:「Show HN:[產品] – [用平實語言說明它做什麼]」
  • 討論串本身比提交更重要
  • 準備好誠實且詳細地回答技術問題
  • 不要請人 upvote——會適得其反

寫作流程

在草擬發佈社交文案時,依下列順序進行:

  1. 從訊息簡報開始(來自 launch-strategy)。如果沒有簡報,請詢問:產品/功能名稱、目標受眾、主要價值主張以及 2-3 個次要價值主張。

  2. 先寫 X/Twitter 版本。 字元限制迫使訊息精煉。如果價值主張無法容納在一條推文中,代表訊息不夠犀利。

  3. 擴展為推文串,如果發佈規模夠大(Tier 1 或較大的 Tier 2)。將每個次要價值主張對應到一則推文。

  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.

相關技能