当用户需要设置、改进或审计分析追踪与测量功能时使用。也适用于用户提及“设置追踪”、“GA4”、“Google Analytics”、“转化追踪”、“事件追踪”、“UTM参数”、“标签管理器”、“GTM”、“分析实现”、“追踪计划”、“如何测量这个”、“追踪转化”、“归因”、“Mixpanel”、“Segment”、“我的事件是否触发”或“分析不工作”等场景。当用户询问如何判断某功能是否正常运作或希望测量营销效果时，也请使用此技能。对于A/B测试测量，请参考 ab-test-setup。
此技能专为需要设置、优化或审计网站/应用分析追踪系统的开发者设计。它覆盖了从 Google Analytics 4 (GA4)、Google Tag Manager (GTM) 到 Mixpanel、Segment 等主流分析平台的配置与调试。当用户遇到追踪数据不准、转化漏斗缺失、UTM参数无效或事件未触发等问题时，此技能可提供标准化的排查流程与最佳实践。它支持通过代码标签（如 dataLayer push）或可视化标签管理器进行事件实现，并强调测试验证（例如使用 GA4 DebugView 或 GTM Preview 模式）。此外，技能还指导如何建立追踪计划文档（Tracking Plan）、设置归因模型（如数据驱动归因）以及确保跨域追踪正确。对于A/B测试测量，它明确建议转用专门的 ab-test-setup 技能。该技能旨在帮助用户从“盲人摸象”式的网站分析转变为可量化、可信赖的数据驱动决策体系。
npx skills add https://github.com/coreyhaines31/marketingskills/tree/main/skills/analytics-trackingInstalled? Explore more 写作与编辑 skills: steipete/notion, langchain-ai/langchain, bytedance/podcast-generation · View all 6 →
当用户需要设置、改进或审计分析追踪与测量功能时使用。也适用于用户提及“设置追踪”、“GA4”、“Google Analytics”、“转化追踪”、“事件追踪”、“UTM参数”、“标签管理器”、“GTM”、“分析实现”、“追踪计划”、“如何测量这个”、“追踪转化”、“归因”、“Mixpanel”、“Segment”、“我的事件是否触发”或“分析不工作”等场景。当用户询问如何判断某功能是否正常运作或希望测量营销效果时，也请使用此技能。对于A/B测试测量，请参考 ab-test-setup。
This repo contains 20 individual skills — each has its own dedicated page.
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions
When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions
When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions
When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions
When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions
When the user wants to figure out which marketing actually drives conversions and revenue, choose or interpret an attribution model, or reconcile conflicting numbers across tools. Also use when the user mentions
When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions
Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Also use when the user mentions
When the user wants to find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities. Use when the user says
Build and leverage online communities to drive product growth and brand loyalty. Use when the user wants to create a community strategy, grow a Discord or Slack community, manage a forum or subreddit, build brand advocates, increase word-of-mouth, drive community-led growth, engage users post-signup, or turn customers into evangelists. Trigger phrases: \
When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions
When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions
When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions
When the user wants to edit, review, or improve existing marketing copy, or refresh outdated content. Also use when the user mentions
When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics-tracking. For page-level conversion optimization, see page-cro.
When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions 'ASO audit,' 'app store optimization,' 'optimize my app listing,' 'improve app visibility,' 'app store ranking,' 'audit my listing,' 'why aren't people downloading my app,' 'improve my app conversion,' 'keyword optimization for app,' or 'compare my app to competitors.' Use when the user shares an App Store or Google Play URL and wants to improve it.
When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' 'battle card,' or 'competitor teardown.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For sales-specific competitor docs, see sales-enablement.
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding-cro.
When the user wants to optimize any form that is NOT signup/registration — including lead capture forms, contact forms, demo request forms, application forms, survey forms, or checkout forms. Also use when the user mentions "form optimization," "lead form conversions," "form friction," "form fields," "form completion rate," "contact form," "nobody fills out our form," "form abandonment," "too many fields," "demo request form," or "lead form isn't converting." Use this for any non-signup form that captures information. For signup/registration forms, see signup-flow-cro. For popups containing forms, see popup-cro.
Notion CLI/API for pages, Markdown content, data sources, files, comments, search, Workers, and raw API calls.
The agent engineering platform.
Use this skill when the user requests to generate, create, or produce podcasts from text content. Converts written content into a two-host conversational podcast audio format with natural dialogue.
Analyze and optimize tweets for maximum reach using Twitter's open-source algorithm insights. Rewrite and edit user tweets to improve engagement and visibility based on how the recommendation system ranks content.
Extracts and analyzes competitors' ads from ad libraries (Facebook, LinkedIn, etc.) to understand what messaging, problems, and creative approaches are working. Helps inspire and improve your own ad campaigns.
Context7 Platform -- Up-to-date code documentation for LLMs and AI code editors