martech-event-instrumentation

v0.1.2

Martech / event-instrumentation & CDP team — agents (event-taxonomy-architect, instrumentation-engineer) for the ENGINEERING of event collection: the tracking plan / event taxonomy (object-action naming), the identity model (anonymous → known, stitching), CDP & collection-architecture selection (Segment, RudderStack, Snowplow, mParticle; client vs server vs hybrid; warehouse-first / reverse-ETL via Hightouch / Census), and consent & privacy-by-design (Consent Mode, IAB TCF, GPC) plus destination wiring. skills (design-a-tracking-plan, choose-cdp-and-collection-architecture, implement-event-instrumentation-and-consent), a knowledge bank + templates. Distinct from marketing-operations (campaign strategy), analytics-engineering (dbt models events downstream), experimentation-growth-engineering (runs tests on them), data-governance-privacy (org policy/DSAR), and data-platform (warehouse) — the event-collection layer they sit on. Requires ravenclaude-core@>=0.7.0.

Claude Code3 Skills

By Matt CorbettLicense: MIT7 GitHub starsUpdated last week

Directory evidence

Runtimes: Claude Code
Parsed components: 3 skill or MCP entries
Source updated: Sep 15, 2026
Manifest status: Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →

Install martech-event-instrumentation for Claude Code

Installs for the current user

claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install martech-event-instrumentation@agent-plugin-marketplace

Paste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.

The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.

Get the source manually

$ git clone https://github.com/mcorbett51090/RavenClaude

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/martech-event-instrumentation/.

Plugin files

plugins/martech-event-instrumentation/

├── .claude-plugin/plugin.json
├── skills/choose-cdp-and-collection-architecture/SKILL.md
├── skills/design-a-tracking-plan/SKILL.md
└── skills/implement-event-instrumentation-and-consent/SKILL.md

Included Skills3

choose-cdp-and-collection-architectureskills/choose-cdp-and-collection-architecture/SKILL.md

Pick the right CDP and event-collection architecture for a described workload by traversing the CDP/collection decision tree (source of truth & activation → packaged CDP vs warehouse-first/reverse-ETL vs Snowplow self-hosted; accuracy vs UI-richness → client-side vs server-side vs hybrid), then return the recommendation, the trade-offs, and the conditions that would flip it. Reach for this when the user asks "Segment vs RudderStack vs Snowplow?", "packaged CDP or warehouse-first?", or "client, server, or hybrid?". Used by `event-taxonomy-architect` (primary).

design-a-tracking-planskills/design-a-tracking-plan/SKILL.md

Turn product and business questions into an event tracking plan — derive the event taxonomy (object-action naming), the properties, the naming convention, the identity model (anonymousId → userId stitching), and the per-event spec table, captured as the contract instrumentation builds to. Reach for this when the user asks "what events should we track?", "how should we name these?", or "how do we stitch anonymous to known users?". Used by `event-taxonomy-architect` (primary).

implement-event-instrumentation-and-consentskills/implement-event-instrumentation-and-consent/SKILL.md

Implement a tracking plan as working event collection — typed client/server-side Track/Identify calls, a codegen'd tracking library, schema validation in CI, consent gating at the source (Google Consent Mode v2 / IAB TCF / GPC), destination + reverse-ETL wiring, then QA the live stream. Reach for this when the user asks "implement these events", "add schema validation to CI", "wire consent", or "why is this event missing/wrong?". Used by `instrumentation-engineer` (primary).

Plugin manifests1

plugins/martech-event-instrumentation/.claude-plugin/plugin.json

{
  "name": "martech-event-instrumentation",
  "version": "0.1.2",
  "description": "Martech / event-instrumentation & CDP team — agents (event-taxonomy-architect, instrumentation-engineer) for the ENGINEERING of event collection: the tracking plan / event taxonomy (object-action naming), the identity model (anonymous → known, stitching), CDP & collection-architecture selection (Segment, RudderStack, Snowplow, mParticle; client vs server vs hybrid; warehouse-first / reverse-ETL via Hightouch / Census), and consent & privacy-by-design (Consent Mode, IAB TCF, GPC) plus destination wiring. skills (design-a-tracking-plan, choose-cdp-and-collection-architecture, implement-event-instrumentation-and-consent), a knowledge bank + templates. Distinct from marketing-operations (campaign strategy), analytics-engineering (dbt models events downstream), experimentation-growth-engineering (runs tests on them), data-governance-privacy (org policy/DSAR), and data-platform (warehouse) — the event-collection layer they sit on. Requires ravenclaude-core@>=0.7.0.",
  "author": {
    "name": "Matt Corbett"
  },
  "homepage": "https://github.com/mcorbett51090/RavenClaude",
  "license": "MIT",
  "keywords": [
    "event-tracking",
    "cdp",
    "segment",
    "rudderstack",
    "snowplow",
    "tracking-plan",
    "event-taxonomy",
    "identity-resolution",
    "consent-mode",
    "reverse-etl",
    "instrumentation",
    "analytics"
  ],
  "requires": {
    "plugins": [
      "ravenclaude-core@>=0.7.0"
    ]
  }
}

Browse the “event-tracking” tag →

experimentation-growth-engineering

by Matt Corbett

Experimentation & growth-engineering team — agents (experimentation-architect, feature-flag-engineer, product-analytics-instrumentation-engineer) for the APPARATUS that lets a team learn fast and ship safely: feature flags + progressive delivery (kill switches, targeting, flag lifecycle/debt), A/B-test plumbing (assignment, exposure logging, SRM checks, sequential-peeking guards, the results read), and trustworthy event instrumentation (a tracking plan, a consistent event schema, identity stitching, a CDP). The engineering of experimentation — statistical VALIDITY (power/MDE, significance) is applied-statistics'. skills, a decision-tree knowledge bank (flag-vs-config + ship-decision trees + a dated 2026 map), best-practices, templates, commands, an advisory hook. Seams: significance -> applied-statistics, hypothesis/outcome -> product-management, rollout -> devops-cicd, pipelines -> data-platform. Requires ravenclaude-core@>=0.7.0.

Claude Code5 Skills

7Updated last week

For maintainers

If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.

[martech-event-instrumentation on Agent Plugins Marketplace](https://pluginsmp.com/plugins/martech-event-instrumentation)