smithery.ai

instrumentation

Use when defining events, fields, and governance for GTM analytics pipelines.

First seen Apr 1, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,291 B
  • docs SUMMARY.md 100 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

SKILL.md

Analytics Instrumentation Standards Skill

When to Use

  • Planning event tracking for product, marketing, or revenue analytics.
  • Auditing existing tracking plans before model refreshes.
  • Coordinating engineering, product, and RevOps on data contracts.

Framework

  1. Event Naming & Structure – action-oriented names, consistent casing, required properties.
  2. Identity Management – user/account IDs, anonymous IDs, device IDs, cross-system mapping.
  3. Consent & Privacy – capture consent status, honor suppression, regional storage rules.
  4. Versioning – change logs, backward compatibility, deprecation timelines.
  5. Observability – sampling dashboards, schema change alerts, volume anomaly detection.

Templates

  • Tracking plan sheet (event, description, properties, source, owner, status).
  • Data contract checklist (fields, types, validation rules, SLA).
  • Observability runbook (metrics, thresholds, notification channels).

Tips

  • Pair each event with QA instructions and sample payloads.
  • Store tracking plans in version control to align with code releases.
  • Review instrumentation quarterly with stakeholders.