Token导航 LogoToken导航

Agent Skill · 研究检索

utm-link-generator(utm 链接生成器)

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

utm-link-generator 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 51,536。

总安装 582周安装 25GitHub Stars 106下载 204核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 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

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

用于查找、检索和筛选相关信息。适合在 Codex、Claude、Cursor、Gemini CLI 中根据关键词或任务场景快速定位候选结果。通过 npx skills add 命令从指定 GitHub 仓库安装并使用。安装前需确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写操作。

utm-link-generator 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/utm-link-generator

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/onewave-ai/claude-skills --skill utm-link-gene…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

utm-link-generator 怎么安装?

在终端执行 npx skills add https://github.com/onewave-ai/claude-skills --skill utm-link-generator。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

utm-link-generator 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

utm-link-generator 需要什么权限?

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

utm-link-generator 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

utm-link-generator 用的人多吗?

公开数据是累计安装 582 次,近一周安装 25 次,下载 204 次,GitHub 106 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

utm-link-generator 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
utm-link-generator

utm 链接生成器 · 本页

582106需要联网未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

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.

平台分布

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