Skip to content
Agentmart
Submit a tool

suede-analytics

Suede AI measurement discipline: tracking plans, event and key-event instrumentation in GA4 and GTM, consent mode v2, UTM hygiene, AI assistant and organic…

Skill by JasonColapietro

IndexedMIT★ 125
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/jasoncolapietro-suede-analytics

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Suede AI measurement discipline: tracking plans, event and key-event instrumentation in GA4 and GTM, consent mode v2, UTM hygiene, AI assistant and organic search channel grouping, and readback proof of what actually fires. Use when setting up, auditing, or repairing analytics across web, product, paid, and lifecycle surfaces. NOT FOR: experiment design or significance (use suede-ab-testing), campaign optimization (use suede-ads), attribution models, model comparison, or cross-tool reconciliation (use suede-attribution), or revenue-process architecture (use suede-revops).

Use cases: design, testing, data, marketing

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/suede-analytics

What's inside

Skill name
suede-analytics
Description
Suede AI measurement discipline: tracking plans, event and key-event instrumentation in GA4 and GTM, consent mode v2, UTM hygiene, AI assistant and organic search channel grouping, and readback proof of what actually fires. Use when setting up, auditing, or repairing analytics across web, product, paid, and lifecycle surfaces. NOT FOR: experiment design or significance (use suede-ab-testing), campaign optimization (use suede-ads), attribution models, model comparison, or cross-tool reconciliation (use suede-attribution), or revenue-process architecture (use suede-revops).
License
MIT
Metadata
version: 2.1.0
Instructions
345 lines in SKILL.md · view on GitHub

Files (7)

  • CARD.md
  • SKILL.md
  • openai.yaml · agents/
  • evals.json · evals/
  • event-library.md · references/
  • ga4-implementation.md · references/
  • gtm-implementation.md · references/

SKILL.md (first lines)

# Suede AI Analytics Skills

Read [the worked delivery contract](references/worked-contract.md) for a concrete
input, expected artifact, failure response and validation example.

## Compatibility

Works with event schemas, source and exports; browser/debugger and existing authorized analytics access for live firing proof. Configuration changes follow the production-change boundary in this skill.

Use this measurement playbook to build tracking that supports auditable marketing and product decisions.

## Initial Assessment

Check for `.agents/product-marketing.md` (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md`) and read it if present: the key conversions, the decisions the data has to serve, and the tools already in place drive every recommendation here.

Then work the intake list under Task-Specific Questions below; ask only what the context file did not already answer.

---

## Production Changes: Halt Before Mutating

Editing live tags, properties, destinations, or consent settings is the
highest-consequence action in this skill, and Boundaries below forbids doing it
without explicit authorization and a rollback plan. When a task requires one and
you do not have both, halt in four parts:

1. Stop. Do not publish the container, edit the property, or change the consent
   configuration.
2. Name the blocker in one line ("publishing this GTM container version changes
   what fires for all live traffic; I have no rollback version identified").
3. Offer 2-4 options (stage it in Preview and hand over the trace; write the
   change as a diff for the owner to publish; publish after the user names the
   rollback version; scope the change to a test environment).
4. Wait for the answer. Do not pick one and continue.

The same halt applies to anything the Privacy and Compliance section below sends
to legal or privacy review: an unresolved lawful-basis question blocks
implementation, it does not get an assumption.

---

## Tracking Plan Framework

### Structure

```
Event Name | Category | Properties | Trigger | Notes
---------- | -------- | ---------- | ------- | -----
```

### Event Types

| Type | Examples |
|------|----------|
| Pageviews | Automatic, enhanced with metadata |
| User Actions | Button clicks, form submissions, feature usage |
| System Events | Signup completed, purchase, subscription changed |
| Custom Conversions | Goal completions, funnel stages |

**For comprehensive event lists**: See [references/event-library.md](references/event-library.md)

---

## Event Naming Conventions

### Recommended Format: Object-Action

```
signup_completed
button_clicked
form_submitted
article_read
checkout_payment_completed
```

### Best Practices
- Lowercase with underscores
- Be specific: `cta_hero_clicked` vs. `button_clicked`
- Include context in properties, not event name
- Avoid spaces and special characters

---

## Essential Events

### Marketing Site

| Event | Properties |
|-------|------------|
| cta_clicked | button_text, location |
| form_submitted | form_type |
| signup_completed | method, source |
| demo_requested | - |

### Product/App

| Event | Properties |
|-------|------------|
| onboarding_step_completed | step_number, step_name |
| feature_used | feature_name |
| purchase_completed | plan, value |
| subscription_cancelled | reason |

**For full event library by business type**: See [references/event-library.md](references/event-library.md)

---

## Event Properties

### Standard Properties

| Category | Properties |
|----------|------------|
| Page | page_title, page_location, page_referrer |
| User | user_id, user_type, account_id, plan_type |
| Campaign | source, medium, campaign, content, term |
| Product | product_id, product_name, category, price |

### Best Practices

From JasonColapietro/suede-creator-skills, MIT.

More from JasonColapietro/suede-creator-skills

Signals

Stars
125
Forks
12
Open issues
4
Contributors
3
Last commit (this folder)
Oct 24, 2026 (3 days ago)
Last release
Aug 4, 2026 (2 months ago)

From GitHub (fetched Oct 24, 2026).

Details

Version
2.1.0
License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from JasonColapietro

Cite this page

suede-analytics skill. Agent Mart. https://agentmart.dev/skills/jasoncolapietro-suede-analytics (last updated 2026-10-24)