This is a skill within Amplitude's official AI plugin, run before writing any instrumentation code: first read the .amplitude instrumentation specification file in the repository (if it exists, treat it as authoritative), then use Amplitude MCP to spot-check actual event names and property names; if MCP is unavailable, search for call sites in the code. It groups calls by SDK, method, and parameter structure (treating custom wrapper functions as a separate category), outputting a deduplicated list of patterns, their locations, and naming conventions for event and property names, for use by subsequent skills such as instrument-events within the same plugin.
Why it matters New instrumentation aligns with existing code style, ensuring that casing and prefix conventions for event and property names remain consistent rather than being written arbitrarily.
Security Audit: Not audited
- Not yet scanned
Rationale
- skills.sh 24 hour installs 1324 (indicates attention only)
- Explicitly excludes Amplitude's built-in system event names to avoid mistaking them for team naming conventions
Usage
- Ask "How do we instrument here?" in the repository where instrumentation is being added, or have the agent automatically invoke it before running other instrumentation skills within the same plugin
Risks
- Not yet audited; installation commands are not displayed. It only reads code and instrumentation directories. Connecting to Amplitude MCP requires an Amplitude account, but it can fall back to code search if unavailable.