amplitude
出典を確認した実質的な文書を持つ Skill が 6 件あります。カードを開くと原文、パッケージ内容、導入方法を確認できます。
amplitudeadd-analytics-instrumentation
End-to-end analytics instrumentation workflow for a PR, branch, file, directory, or feature. Reads the code, discovers what events should be tracked, and produces a concrete instrumentation plan — all in one shot. Use this skill whenever a user wants to add analytics to a PR, asks "instrument this PR", "add tracking to this branch", "what analytics does this file need", "instrument the checkout flow", "run the full instrumentation workflow", or any request that implies going from code changes to
- 24時間の導入数
- 558
- GitHub Stars
- 46
- 更新日
- 10月31日
amplitudediff-intake
Reads a PR or branch diff and produces a structured YAML change brief for downstream analytics instrumentation skills. Use this as the first step whenever a user shares a PR link, branch comparison, or raw diff and wants to understand what changed, what needs tracking, or how to instrument a feature. Trigger on phrases like "review this PR", "what changed in this branch", "help me instrument this diff", "check analytics coverage for this change", or any request to start the analytics review work
- 24時間の導入数
- 558
- GitHub Stars
- 46
- 更新日
- 10月31日
amplitudediscover-analytics-patterns
Discovers how analytics tracking calls are actually written in this codebase — the concrete SDK calls, function signatures, and import patterns used to send events. Use this skill whenever you need to understand the existing analytics instrumentation patterns before adding new tracking, when someone asks "how do we track events here?", "show me the analytics setup", "what's the analytics pattern in this codebase?", or any time the instrument-events or discover-event-surfaces skills are about to
- 24時間の導入数
- 558
- GitHub Stars
- 46
- 更新日
- 10月31日
amplitudediscover-event-surfaces
Given a changebrief YAML (output from diff-intake), generates an exhaustive list of candidate analytics events to instrument. Takes the perspective of an engineer with a PM mindset — surfaces everything worth considering so a PM can decide what actually matters. Use this as step 2 of the analytics instrumentation workflow, immediately after diff-intake produces a changebrief. Trigger whenever a user has a changebrief YAML and wants to know what analytics events to add, or asks "what should I tra
- 24時間の導入数
- 557
- GitHub Stars
- 46
- 更新日
- 10月31日
amplitudeinstrument-events
Given eventcandidates YAML (output from discover-event-surfaces), generates a concrete instrumentation plan for priority-3 (critical) events. Acts as a Software Architect: discovers existing analytics patterns in the codebase, reads the hinted files to determine what variables are in scope, designs minimal chart-useful properties, and identifies the exact insertion point for each tracking call. Outputs a structured JSON trackingPlan. Use this as step 3 of the analytics instrumentation workflow,
- 24時間の導入数
- 554
- GitHub Stars
- 46
- 更新日
- 10月31日
amplitudetaxonomy
Source of truth for event taxonomy generation, data auditing, and governance best practices in Amplitude. Use when an agent needs to create, validate, audit, score, or recommend improvements to event tracking plans, naming conventions, property standards, data quality, or deprecation workflows, including checking a plan against the customer's own standard (Data → Settings naming conventions and AI Context). Covers naming rules, property standards, scoring frameworks, safe metadata operations, de
- 24時間の導入数
- 553
- GitHub Stars
- 46
- 更新日
- 10月31日