SkillAgentSearch skills...

utm-tracking-generator

Generate consistent UTM parameters, GA4 event naming, and conversion tracking specs following taxonomy best practices

Install / Use

npx skills add irinabuht12-oss/marketing-skills --skill utm-tracking-generator

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

92/100

Category

Marketing

Supported Platforms

Zed

Tags

Our assessment of utm-tracking-generator

utm-tracking-generator scores 92/100 on our quality scale, 173rd of 642 Marketing skills we index (top 27%).

Its SKILL.md is 6.5 KB long, well organised into 32 sections with 8 code examples: a thorough specification that gives an agent plenty to work with.

With 7,761 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
29/30
Structure
20/20
Description
12/15
Adoption
17/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 20 days ago, so utm-tracking-generator is actively maintained.
  • Our last check on 2026-10-28 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

Review

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review judged it risky: The skill instructs the agent to add a third-party MCP connector (`https://connector.get-ryze.ai/mcp`) using commands like `claude mcp add ryze --transport http ...`, which would grant an unofficial service access to the user's Google Ads,.

AI review: risky

  • The skill instructs the agent to add a third-party MCP connector (`https://connector.get-ryze.ai/mcp`) using commands like `claude mcp add ryze --transport http ...`, which would grant an unofficial service access to the user's Google Ads,
  • Adding an external MCP connector from a skill file redirects the agent's API traffic through an unofficial proxy and meaningfully expands the agent's permissions and attack surface.
  • The rest of the file is benign marketing taxonomy, but the data-access section turns the skill into a vehicle for connecting privileged accounts to a third-party service.

AI review by kimi-k2.7-code on 2026-10-01. Automated pattern scan on 2026-09-30. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

utm-tracking-generator compared with similar skills

All 4 of these similar skills score higher than utm-tracking-generator; compare them before choosing.

SkillScoreStarsUpdatedFormat
utm-tracking-generator (this skill)by irinabuht12-oss927.8k20d agoSKILL.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md
designby nextlevelbuilder100149.0k6d agoSKILL.md

Frequently asked questions

How do I install utm-tracking-generator?
Run npx skills add irinabuht12-oss/marketing-skills --skill utm-tracking-generator. The install tabs above show the steps for each supported agent.
Which AI agents does utm-tracking-generator work with?
It is written for Zed, as a SKILL.md file. Other agents that read the same format can often use it too.
Is utm-tracking-generator safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review judged it risky: The skill instructs the agent to add a third-party MCP connector (https://connector.get-ryze.ai/mcp) using commands like claude mcp add ryze --transport http ..., which would grant an unofficial service access to the user's Google Ads,. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is utm-tracking-generator still maintained?
The repository was last updated 20 days ago, so utm-tracking-generator is actively maintained.

name: utm-tracking-generator description: Generate consistent UTM parameters, GA4 event naming, and conversion tracking specs following taxonomy best practices. Use when describing campaign structure, requesting UTM links, needing GA4 event names, or wanting to standardize tracking nomenclature across marketing channels. Platform: Google and Meta. metadata: platform: Google and Meta

UTM & Tracking Generator

Create standardized tracking parameters for consistent marketing attribution.

Process

  1. Understand campaign context - Channels, goals, audience, offers
  2. Apply naming taxonomy - Consistent, lowercase, documented
  3. Generate UTM strings - Complete parameter sets
  4. Create GA4 event specs - Compliant naming
  5. Provide implementation guidance - Platform-specific instructions

UTM Parameter Taxonomy

| Parameter | Purpose | Example Values | |-----------|---------|----------------| | utm_source | Traffic source platform | google, facebook, linkedin, newsletter | | utm_medium | Marketing channel type | cpc, paid-social, email, display, organic | | utm_campaign | Campaign identifier | spring_sale-us-2024-prospecting | | utm_term | Paid keywords (optional) | running_shoes, [brand_name] | | utm_content | Content variant (optional) | hero_cta, sidebar_banner, email_v2 |

Naming Convention Rules

  1. Always lowercase - UTMs are case-sensitive (google ≠ Google)
  2. No spaces - Use hyphens (-) or underscores (_)
  3. Consistent separators - Pick one style for organization
  4. Descriptive but concise - Balance clarity with length
  5. Document everything - Maintain shared naming guide

Campaign Naming Structure

[product/goal]-[geography]-[date]-[audience]-[offer]

Examples:
- shoes-us-q1_2024-running_enthusiasts-20off
- saas-global-jan2024-smb_trial-free_demo
- ebook-uk-2024_q2-marketers-lead_magnet

Platform-Specific Templates

Google Ads

utm_source=google&utm_medium=cpc&utm_campaign={campaign_name}&utm_term={keyword}&utm_content={creative}

Meta Ads (Dynamic Parameters)

utm_source={{site_source_name}}&utm_medium=paid-social&utm_campaign={{campaign.name}}&utm_content={{adset.name}}&utm_term={{ad.name}}

LinkedIn Ads

utm_source=linkedin&utm_medium=paid-social&utm_campaign=[campaign_name]&utm_content=[ad_name]

Email Marketing

utm_source=klaviyo&utm_medium=email&utm_campaign=[flow_name]-[email_position]&utm_content=[variant]

GA4 Event Naming Rules

| Rule | Requirement | Example | |------|-------------|---------| | Start with letter | No numbers or symbols first | ✅ page_view ❌ 1st_click | | Allowed characters | Letters, numbers, underscores only | ✅ add_to_cart ❌ add-to-cart | | Max length | 40 characters | Keep concise | | No reserved prefixes | Avoid ga_, google_, firebase_ | Use custom prefix | | Case | Use snake_case | form_submit, button_click |

Standard Event Names (Use These)

page_view
scroll_depth
form_submit
button_click
video_play
video_complete
file_download
outbound_click
add_to_cart
begin_checkout
purchase
sign_up
login
search

Output Format

## Tracking Specification

### Campaign Overview
- **Campaign Name**: [Name]
- **Channels**: [List]
- **Goal**: [Conversion objective]

### UTM Parameters

#### [Channel 1]
| Parameter | Value |
|-----------|-------|
| utm_source | |
| utm_medium | |
| utm_campaign | |
| utm_term | |
| utm_content | |

**Full URL**: `https://example.com?utm_source=...`

#### [Channel 2]
...

### GA4 Event Specifications

| Event | Trigger | Parameters |
|-------|---------|------------|
| [event_name] | [When fired] | [Key params] |

### Implementation Notes
- [Platform-specific guidance]
- [Testing recommendations]

### Naming Convention Reference
- Separator: [hyphen/underscore]
- Date format: [YYYY_QN or MMYYYY]
- Geography codes: [us, uk, global]

Example

Input: "I need UTM tracking for a spring sale campaign running on Google Ads, Facebook, and email for US customers, promoting 20% off shoes."

Output:

## Tracking Specification

### Campaign Overview
- **Campaign Name**: shoes-us-spring2024-allcust-20off
- **Channels**: Google Ads, Meta Ads, Email
- **Goal**: Purchase conversions

### UTM Parameters

#### Google Ads
| Parameter | Value |
|-----------|-------|
| utm_source | google |
| utm_medium | cpc |
| utm_campaign | shoes-us-spring2024-allcust-20off |
| utm_term | {keyword} |
| utm_content | {creative} |

**Full URL**: 
`https://yoursite.com/shoes?utm_source=google&utm_medium=cpc&utm_campaign=shoes-us-spring2024-allcust-20off&utm_term={keyword}&utm_content={creative}`

#### Meta Ads
| Parameter | Value |
|-----------|-------|
| utm_source | facebook |
| utm_medium | paid-social |
| utm_campaign | shoes-us-spring2024-allcust-20off |
| utm_content | {{adset.name}} |
| utm_term | {{ad.name}} |

**Full URL**:
`https://yoursite.com/shoes?utm_source=facebook&utm_medium=paid-social&utm_campaign=shoes-us-spring2024-allcust-20off&utm_content={{adset.name}}&utm_term={{ad.name}}`

#### Email (Klaviyo)
| Parameter | Value |
|-----------|-------|
| utm_source | klaviyo |
| utm_medium | email |
| utm_campaign | shoes-us-spring2024-allcust-20off |
| utm_content | promo_blast_1 |

**Full URL**:
`https://yoursite.com/shoes?utm_source=klaviyo&utm_medium=email&utm_campaign=shoes-us-spring2024-allcust-20off&utm_content=promo_blast_1`

### GA4 Events to Track
| Event | Trigger | Parameters |
|-------|---------|------------|
| view_promotion | Promo banner viewed | promotion_id, promotion_name |
| select_promotion | Promo clicked | promotion_id, promotion_name |
| add_to_cart | Shoe added | item_id, item_name, price, discount |
| purchase | Order completed | transaction_id, value, items[] |

### Implementation Notes
- Test all UTMs with Google's Campaign URL Builder before launch
- Verify events in GA4 DebugView
- Document naming convention in shared spreadsheet

Guidelines

  • Always use lowercase for all UTM values
  • Never include PII in tracking parameters
  • Test URLs before distributing
  • Provide platform-specific dynamic parameter syntax
  • Include testing/validation recommendations

Data access (Ryze MCP)

This skill works best with live account data. Connect the free Ryze MCP once and Claude reads your Google Ads, Meta Ads, GA4 and Search Console directly:

  • claude.ai / Claude Desktop: Settings → Connectors → Add custom connector → https://connector.get-ryze.ai/mcp
  • Claude Code: claude mcp add ryze --transport http https://connector.get-ryze.ai/mcp
  • Cursor: Settings → MCP → add the same URL

Setup guide: https://www.get-ryze.ai/how-to-connect-claude-to-google-meta-ads-mcp

Related Skills

View on GitHub
GitHub Stars7.8k
CategoryMarketing
Updated20d ago
Forks579

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium