Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计通过

utm-link-generatorutm 链接生成器

Agent Skill

utm-link-generator 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

582

周安装

25

GitHub Stars

106

下载量

204
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:utm-link-generator(utm 链接生成器)
来源仓库:https://github.com/onewave-ai/claude-skills
仓库路径:skills/utm-link-generator
安装命令:
npx skills add https://github.com/onewave-ai/claude-skills --skill utm-link-generator
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/onewave-ai/claude-skills --skill utm-link-generator

简介

用于查找、检索和筛选相关信息。

  • 适合在 Codex、Claude、Cursor、Gemini CLI 中根据关键词或任务场景快速定位候选结果。
  • 通过 npx skills add 命令从指定 GitHub 仓库安装并使用。
  • 安装前需确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写操作。
  • utm-link-generator 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

UTM Link Generator

A disciplined UTM link generation system that enforces consistent naming conventions across all campaigns, maintains a registry to prevent duplicates and naming drift, and outputs platform-ready links. This is not a simple URL concatenator -- it is a naming governance system for marketing attribution.

Why This Exists

UTM chaos is the number one cause of broken marketing attribution. When team members use "linkedin" vs "LinkedIn" vs "linked-in" vs "li" as a source, your analytics become useless. This skill enforces a single source of truth: the UTM registry.

Capabilities

  1. Generate UTM-tagged URLs with validated, consistent parameters
  2. Maintain a utm-registry.json file that tracks all generated links and enforces naming conventions
  3. Prevent duplicates -- warns when a similar link already exists in the registry
  4. Platform-specific formatting -- outputs links optimized for LinkedIn, email, social, and ad platforms
  5. Bulk generation -- create multiple variants for A/B testing or multi-channel campaigns
  6. Validation -- rejects malformed URLs, empty parameters, and convention violations
  7. Reporting -- generates campaign tracking summaries from the registry

UTM Parameter Reference

ParameterRequiredPurposeExample
utm_sourceYesWhere the traffic comes fromlinkedin, google, newsletter
utm_mediumYesMarketing mediumcpc, email, social, organic
utm_campaignYesCampaign identifierq1-2026-product-launch
utm_termNoPaid keyword (search ads)project-management-software
utm_contentNoDifferentiates similar linkshero-cta, sidebar-banner, variant-a
utm_idNoCampaign ID for GA4camp-2026-q1-001

Naming Conventions (Enforced)

These conventions are non-negotiable. The skill will reject or auto-correct any violations.

General Rules

  1. All lowercase -- Never LinkedIn, always linkedin
  2. Hyphens for spaces -- Never product launch, always product-launch
  3. No special characters -- Only alphanumeric and hyphens
  4. No trailing/leading hyphens -- Never -campaign-name-
  5. No double hyphens -- Never my--campaign
  6. Maximum length: 50 characters per parameter value
  7. Date format in campaigns: q[N]-[YYYY] or [YYYY]-[MM] prefix

Source Values (Canonical List)

Only these source values are allowed. Any new source must be explicitly added to the registry.

Canonical SourceAliases (auto-corrected)Platform
googlegoog, google-ads, adwordsGoogle Ads / Organic
linkedinli, linked-in, linkedin-adsLinkedIn
facebookfb, meta, facebook-adsFacebook / Meta
instagramig, instaInstagram
twitterx, x-com, twX (Twitter)
youtubeyt, you-tubeYouTube
tiktoktt, tik-tokTikTok
redditrdReddit
emailmail, e-mail, emEmail campaigns
newsletternl, news-letterNewsletter specifically
bingmicrosoft-ads, msnBing / Microsoft
directnone, (direct)Direct traffic
referralref, partnerReferral traffic
podcastpod, spotifyPodcast channels
slackslSlack communities
producthuntph, product-huntProduct Hunt
hackernewshn, hacker-newsHacker News

Medium Values (Canonical List)

Canonical MediumAliases (auto-corrected)Use Case
cpcppc, paid-click, cost-per-clickPaid search / paid social clicks
cpmdisplay, paid-impressionDisplay / impression campaigns
emaile-mail, mailEmail campaigns
socialsocial-media, organic-socialOrganic social posts
organicseo, organic-searchOrganic search traffic
referralref, partner, affiliateReferral / partner links
videovid, youtube, pre-rollVideo ad placements
retargetingremarketing, retargetRetargeting campaigns
contentblog, article, content-syndicationContent marketing
webinarweb, event, virtual-eventWebinar / event registrations
podcastpod, audioPodcast mentions / ads
smstext, mmsSMS / text campaigns
qrqr-code, printQR code / print materials
pushpush-notification, notificationPush notifications

Campaign Naming Pattern

Campaigns follow this structure:

[quarter-or-month]-[year]-[campaign-name]-[optional-variant]

Examples:

  • q1-2026-product-launch
  • 2026-03-spring-webinar
  • q2-2026-brand-awareness-linkedin
  • evergreen-demo-request (for always-on campaigns, skip the date prefix)

Execution Protocol

Step 1: Accept Input

The user provides some or all of these:

  • Destination URL (required) -- The page they want to link to
  • Source (required) -- Where the traffic comes from
  • Medium (required) -- The marketing channel type
  • Campaign (required) -- Campaign name
  • Term (optional) -- Keyword for paid search
  • Content (optional) -- Link differentiator
  • Platforms (optional) -- Which platforms to generate links for (default: all relevant)

If the user provides a brief like "I need links for our Q1 product launch campaign on LinkedIn and email pointing to our pricing page," extract the parameters from natural language.

Step 2: Validate and Normalize

For each parameter:

  1. Convert to lowercase -- LinkedIn becomes linkedin
  2. Replace spaces with hyphens -- product launch becomes product-launch
  3. Strip special characters -- Remove anything not [a-z0-9-]
  4. Check against canonical lists -- Auto-correct known aliases (e.g., fb to facebook)
  5. Reject unknown values -- If a source or medium is not in the canonical list and is not a reasonable addition, warn the user and suggest the closest match
  6. Validate URL -- Ensure the destination URL is well-formed (has protocol, valid domain)
  7. Check length -- Ensure no parameter exceeds 50 characters

Report any corrections made:

## Parameter Validation

- Source: "LinkedIn" -> "linkedin" (normalized to lowercase)
- Medium: "paid" -> "cpc" (corrected to canonical value)
- Campaign: "Q1 Product Launch!" -> "q1-product-launch" (normalized)
- URL: https://example.com/pricing -- Valid

Step 3: Check Registry for Duplicates

Read the utm-registry.json file (or create it if it does not exist). Check for:

  1. Exact duplicates -- Same URL + same parameters. Warn and return the existing link.
  2. Near duplicates -- Same URL + same campaign + different content/medium. Warn but allow (this is often intentional for multi-channel tracking).
  3. Naming conflicts -- Same campaign name but different capitalization or hyphenation. Block and show the existing convention.

Step 4: Generate Links

Build the UTM-tagged URL:

{base_url}?utm_source={source}&utm_medium={medium}&utm_campaign={campaign}[&utm_term={term}][&utm_content={content}][&utm_id={id}]

Rules:

  • If the base URL already has query parameters, append with & not ?
  • URL-encode any parameter values that contain special characters
  • Preserve the base URL's existing query parameters and fragment

Step 5: Generate Platform-Specific Variants

For each platform requested, generate an optimized link:

LinkedIn

## LinkedIn

**Post Link** (organic social):
https://example.com/pricing?utm_source=linkedin&utm_medium=social&utm_campaign=q1-2026-product-launch&utm_content=organic-post

**Ad Link** (paid):
https://example.com/pricing?utm_source=linkedin&utm_medium=cpc&utm_campaign=q1-2026-product-launch&utm_content=sponsored-post

**Message Link** (InMail/DM):
https://example.com/pricing?utm_source=linkedin&utm_medium=social&utm_campaign=q1-2026-product-launch&utm_content=inmail

**Profile Link** (bio/featured):
https://example.com/pricing?utm_source=linkedin&utm_medium=social&utm_campaign=q1-2026-product-launch&utm_content=profile-link

Email

## Email

**Primary CTA**:
https://example.com/pricing?utm_source=email&utm_medium=email&utm_campaign=q1-2026-product-launch&utm_content=primary-cta

**Secondary CTA**:
https://example.com/pricing?utm_source=email&utm_medium=email&utm_campaign=q1-2026-product-launch&utm_content=secondary-cta

**Header Link**:
https://example.com/pricing?utm_source=email&utm_medium=email&utm_campaign=q1-2026-product-launch&utm_content=header-link

**Footer Link**:
https://example.com/pricing?utm_source=email&utm_medium=email&utm_campaign=q1-2026-product-launch&utm_content=footer-link

Social (General)

## Social

**Twitter/X**:
https://example.com/pricing?utm_source=twitter&utm_medium=social&utm_campaign=q1-2026-product-launch

**Facebook**:
https://example.com/pricing?utm_source=facebook&utm_medium=social&utm_campaign=q1-2026-product-launch

**Instagram** (bio link):
https://example.com/pricing?utm_source=instagram&utm_medium=social&utm_campaign=q1-2026-product-launch&utm_content=bio-link

**Reddit**:
https://example.com/pricing?utm_source=reddit&utm_medium=social&utm_campaign=q1-2026-product-launch

Ads (Paid)

## Paid Ads

**Google Ads**:
https://example.com/pricing?utm_source=google&utm_medium=cpc&utm_campaign=q1-2026-product-launch&utm_term={keyword}

**LinkedIn Ads**:
https://example.com/pricing?utm_source=linkedin&utm_medium=cpc&utm_campaign=q1-2026-product-launch

**Facebook/Meta Ads**:
https://example.com/pricing?utm_source=facebook&utm_medium=cpc&utm_campaign=q1-2026-product-launch

Note: For Google Ads, use {keyword} as a dynamic placeholder that Google will auto-replace.

Step 6: Update Registry

Append all generated links to utm-registry.json:

{
  "version": "1.0",
  "lastUpdated": "2026-04-10T12:00:00Z",
  "namingConventions": {
    "sources": ["google", "linkedin", "facebook", "instagram", "twitter", "email", "newsletter"],
    "mediums": ["cpc", "cpm", "email", "social", "organic", "referral", "video", "retargeting"]
  },
  "campaigns": [
    {
      "name": "q1-2026-product-launch",
      "createdAt": "2026-04-10T12:00:00Z",
      "description": "Q1 2026 product launch campaign",
      "links": [
        {
          "id": "utm-001",
          "url": "https://example.com/pricing?utm_source=linkedin&utm_medium=social&utm_campaign=q1-2026-product-launch&utm_content=organic-post",
          "source": "linkedin",
          "medium": "social",
          "campaign": "q1-2026-product-launch",
          "content": "organic-post",
          "platform": "linkedin",
          "variant": "organic-post",
          "createdAt": "2026-04-10T12:00:00Z",
          "status": "active"
        }
      ]
    }
  ],
  "stats": {
    "totalLinks": 1,
    "totalCampaigns": 1,
    "sourcesUsed": ["linkedin"],
    "mediumsUsed": ["social"]
  }
}

Step 7: Output Summary

Present the final output in a clean, copy-paste-ready format:

## UTM Links Generated

**Campaign**: q1-2026-product-launch
**Destination**: https://example.com/pricing
**Generated**: 2026-04-10

### Ready-to-Copy Links

| Platform | Variant | Link |
|----------|---------|------|
| LinkedIn (organic) | organic-post | [full URL] |
| LinkedIn (paid) | sponsored-post | [full URL] |
| Email (primary CTA) | primary-cta | [full URL] |
| Email (secondary CTA) | secondary-cta | [full URL] |
| Twitter | default | [full URL] |
| Facebook | default | [full URL] |

### Registry Updated
- New links added: 6
- Total links in registry: 6
- Registry file: ./utm-registry.json

### Validation Report
- All parameters normalized to convention
- No duplicate links found
- No naming conflicts detected

Bulk Generation Mode

For generating links across many campaigns or many URLs at once.

Input Format (Bulk)

The user can provide a table or list:

Generate UTM links for these pages:
- /pricing -- linkedin, email, twitter -- q1-2026-product-launch
- /demo -- linkedin, google-ads -- q1-2026-demo-push
- /case-studies -- email, linkedin -- q1-2026-social-proof

Processing

  1. Parse each line into (URL, platforms, campaign)
  2. Validate and normalize all parameters
  3. Generate all variant links for each URL/platform combination
  4. Deduplicate across the batch
  5. Update registry with all new links
  6. Output a master table

Output Format (Bulk)

## Bulk UTM Generation -- 3 campaigns, 8 platform variants, 24 total links

| Campaign | URL | Platform | Variant | Full Link |
|----------|-----|----------|---------|-----------|
| q1-2026-product-launch | /pricing | linkedin-organic | organic-post | [URL] |
| q1-2026-product-launch | /pricing | linkedin-paid | sponsored-post | [URL] |
| q1-2026-product-launch | /pricing | email | primary-cta | [URL] |
| ... | ... | ... | ... | ... |

Registry updated: 24 new links added.

Registry Management Commands

The user can also invoke this skill for registry operations:

Audit Registry

"Audit my UTM registry"

Reads utm-registry.json and reports:

  • Total campaigns and links
  • Naming convention violations (if any crept in manually)
  • Stale campaigns (older than 6 months with no new links)
  • Unused sources or mediums
  • Duplicate or near-duplicate links

Add Custom Source/Medium

"Add 'partnerstack' as a UTM source"

Adds the new value to the canonical list in the registry and documents it.

Campaign Report

"Show me all links for the q1-2026-product-launch campaign"

Filters the registry and displays all links for that campaign, grouped by platform.

Export for Google Sheets

"Export my UTM registry as CSV"

Generates a CSV file with columns: Campaign, URL, Source, Medium, Content, Term, Full Link, Created Date, Status.

Error Handling

ErrorResponse
Invalid URL (no protocol)Auto-prepend https:// and warn
Unknown sourceSuggest closest canonical match, ask for confirmation
Unknown mediumSuggest closest canonical match, ask for confirmation
Campaign name too longSuggest abbreviated version
Duplicate link existsShow existing link, ask if user wants to create anyway
Registry file missingCreate new registry with default conventions
Registry file corruptedAttempt to parse what exists, back up, create fresh
Base URL has existing UTMsStrip existing UTM params, warn user, apply new ones

Integration Notes

  • Google Analytics 4: All parameters map directly to GA4 dimensions. utm_id maps to campaign_id.
  • HubSpot: Source and medium map to HubSpot's Original Source properties.
  • Salesforce: Campaign name can map to Salesforce Campaign records via integration.
  • Mixpanel / Amplitude: UTM params auto-captured on page load via standard SDKs.

Best Practices Embedded in This Skill

  1. One registry, one truth -- All UTM links flow through the registry. No ad-hoc link creation.
  2. Convention over configuration -- Canonical lists prevent naming drift before it starts.
  3. Auto-correction over rejection -- When possible, fix the input rather than blocking the user.
  4. Platform awareness -- Different platforms need different utm_content values to distinguish placements.
  5. Date-prefixed campaigns -- Makes it trivial to filter analytics by time period.
  6. Audit trail -- Every link is timestamped and attributed in the registry.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

32.87%
按下载量换算67

Claude

31.87%
按下载量换算65

Cursor

20.94%
按下载量换算43

Gemini CLI

8.66%
按下载量换算18

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills