/url-slug
When the user wants to create, optimize, or validate URL slugs for content pages. Also use when the user mentions "URL slug," "URL path," "blog URL," "article URL," "short URL," "clean slug," "permalink," "slug optimization," "URL structure," "SEO-friendly URL," "create URL
$ npx -y skills add kostja94/marketing-skills --skill url-slug --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/url-slug
Context preview
The summary Claude sees to decide when to auto-load this skill.
When the user wants to create, optimize, or validate URL slugs for content pages. Also use when the user mentions "URL slug," "URL path," "blog URL," "article URL," "short URL," "clean slug," "permalink," "slug optimization," "URL structure," "SEO-friendly URL," "create URL
SKILL.md
url-slug.SKILL.mdname: url-slug-generator
description: When the user wants to create, optimize, or validate URL slugs for content pages. Also use when the user mentions "URL slug," "URL path," "blog URL," "article URL," "short URL," "clean slug," "permalink," "slug optimization," "URL structure," "SEO-friendly URL," "create URL slug," or "SEO slug." For site-wide URL policy, use url-structure.
metadata:
version: 1.0.1
Components: URL Slug
Guides creation of SEO-friendly URL slugs for blog posts, articles, and content pages. Research on 11.8M Google results shows shorter URLs tend to rank higher; position #1 URLs average 50–60 characters.
**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.
Scope
- **URL slug**: The path segment after the base (e.g., `ai-people-search` in `/blog/ai-people-search`)
- **Applies to**: Blog posts, articles, guides, category pages, product pages
Best Practices
Length
| Guideline | Target | |-----------|--------| | **Slug length** | Under 60 characters total (including path prefix) | | **Word count** | 3–5 words | | **Principle** | Shorter = easier to read, share, remember; less truncation in SERPs; see **serp-features** |
**Example**: "The Complete Guide to AI Search Engine for Finding People" → `ai-people-search` (3 words) or `ai-search-finding-people` (4 words), not `ai-search-engine-finding-people-speed-discovery-outreach` (9 words, 51 chars).
Format
| Rule | Do | Avoid | |------|-----|-------| | **Separators** | Hyphens (`-`) | Underscores (`_`), spaces, periods | | **Case** | Lowercase only | Mixed case (causes duplicate content) | | **Characters** | Letters (a-z), numbers (0-9), hyphens | Special chars | | **Stop words** | Remove when possible: the, a, and, or, to | Keep when needed: "how-to" |
Content
| Rule | Guideline | |------|-----------| | **Primary keyword** | Include near start; one focus per URL | | **Descriptive** | Clear what page is about from slug alone | | **No keyword stuffing** | One keyword mention is enough | | **No dates** | Omit unless time-specific (news, annual roundups) |
Non-ASCII Characters
| Scenario | Rule | |----------|------| | **Accented letters** | Convert to ASCII: é→e, ü→u, ñ→n, ç→c | | **Non-Latin scripts** | Use UTF-8 percent-encoding if required; prefer ASCII for compatibility | | **Example** | `jalapeno` not `jalapeño`; `cafe` not `café` |
Common Mistakes
- **Copy-pasting full title**: Summarize instead — long title → short slug
- **Auto-generated IDs**: `/post/12847` — always customize
- **Tracking params in slug**: UTM, session IDs — use query params separately
- **Changing without redirect**: Always 301 from old to new slug
Slug Generation Workflow
1. **Extract primary keyword** from title or target keyword 2. **Summarize** in 3–5 words (don't copy full title) 3. **Remove stop words** (the, a, and, or) unless needed for readability 4. **Lowercase, hyphenate**, validate length < 60 chars 5. **Check uniqueness** — no duplicate slugs site-wide
Examples
| Title / Topic | ❌ Too long | ✅ Recommended | |---------------|-------------|-----------------| | AI Search Engine for Finding People: Speed vs. Discovery | `ai-search-engine-finding-people-speed-discovery-outreach` | `ai-people-search` or `ai-search-finding-people` | | The Ultimate SEO Checklist for 2025 | `the-ultimate-seo-checklist-for-2025` | `seo-checklist-2025` | | How to Increase Website Traffic | `how-to-increase-the-traffic-to-your-website` | `increase-website-traffic` | | Best Running Shoes for Marathon Training | `best-running-shoes-for-marathon-training-in-2025` | `best-running-shoes-2025` |
Output Format
When creating or auditing a slug:
- **Recommended slug** (3–5 words)
- **Character count** (slug only)
- **Primary keyword** included
- **Alternatives** if multiple valid options
- **Reference**: [Alignify URL optimization](https://alignify.co/zh/seo/url-optimization)
Related Skills
- **url-structure**: URL hierarchy, site structure; references this skill for slug conventions
- **canonical-tag**: When changing slugs, set up 301 redirects
- **article-page-generator**: Article URL slugs
- **blog-page-generator**: Blog post URL slugs
- **glossary-page-generator**: Glossary term slugs
- **products-page-generator**: Product page slugs
- **customer-stories-page-generator**: Case study page slugs
- **resources-page-generator**: Resource page slugs
- **features-page-generator**: Per-feature page slugs
Read more
name: url-slug-generator description: When the user wants to create, optimize, or validate URL slugs for content pages. Also use when the user mentions "URL slug," "URL path," "blog URL," "article URL," "short URL," "clean slug," "permalink," "slug optimization," "URL structure," "SEO-friendly URL," "create URL slug," or "SEO slug." For site-wide URL policy, use url-structure. metadata: version: 1.0.1
Components: URL Slug
Guides creation of SEO-friendly URL slugs for blog posts, articles, and content pages. Research on 11.8M Google results shows shorter URLs tend to rank higher; position #1 URLs average 50–60 characters.
**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.
Scope
- **URL slug**: The path segment after the base (e.g., `ai-people-search` in `/blog/ai-people-search`)
- **Applies to**: Blog posts, articles, guides, category pages, product pages
Best Practices
Length
| Guideline | Target | |-----------|--------| | **Slug length** | Under 60 characters total (including path prefix) | | **Word count** | 3–5 words | | **Principle** | Shorter = easier to read, share, remember; less truncation in SERPs; see **serp-features** |
**Example**: "The Complete Guide to AI Search Engine for Finding People" → `ai-people-search` (3 words) or `ai-search-finding-people` (4 words), not `ai-search-engine-finding-people-speed-discovery-outreach` (9 words, 51 chars).
Format
| Rule | Do | Avoid | |------|-----|-------| | **Separators** | Hyphens (`-`) | Underscores (`_`), spaces, periods | | **Case** | Lowercase only | Mixed case (causes duplicate content) | | **Characters** | Letters (a-z), numbers (0-9), hyphens | Special chars | | **Stop words** | Remove when possible: the, a, and, or, to | Keep when needed: "how-to" |
Content
| Rule | Guideline | |------|-----------| | **Primary keyword** | Include near start; one focus per URL | | **Descriptive** | Clear what page is about from slug alone | | **No keyword stuffing** | One keyword mention is enough | | **No dates** | Omit unless time-specific (news, annual roundups) |
Non-ASCII Characters
| Scenario | Rule | |----------|------| | **Accented letters** | Convert to ASCII: é→e, ü→u, ñ→n, ç→c | | **Non-Latin scripts** | Use UTF-8 percent-encoding if required; prefer ASCII for compatibility | | **Example** | `jalapeno` not `jalapeño`; `cafe` not `café` |
Common Mistakes
- **Copy-pasting full title**: Summarize instead — long title → short slug
- **Auto-generated IDs**: `/post/12847` — always customize
- **Tracking params in slug**: UTM, session IDs — use query params separately
- **Changing without redirect**: Always 301 from old to new slug
Slug Generation Workflow
1. **Extract primary keyword** from title or target keyword 2. **Summarize** in 3–5 words (don't copy full title) 3. **Remove stop words** (the, a, and, or) unless needed for readability 4. **Lowercase, hyphenate**, validate length < 60 chars 5. **Check uniqueness** — no duplicate slugs site-wide
Examples
| Title / Topic | ❌ Too long | ✅ Recommended | |---------------|-------------|-----------------| | AI Search Engine for Finding People: Speed vs. Discovery | `ai-search-engine-finding-people-speed-discovery-outreach` | `ai-people-search` or `ai-search-finding-people` | | The Ultimate SEO Checklist for 2025 | `the-ultimate-seo-checklist-for-2025` | `seo-checklist-2025` | | How to Increase Website Traffic | `how-to-increase-the-traffic-to-your-website` | `increase-website-traffic` | | Best Running Shoes for Marathon Training | `best-running-shoes-for-marathon-training-in-2025` | `best-running-shoes-2025` |
Output Format
When creating or auditing a slug:
- **Recommended slug** (3–5 words)
- **Character count** (slug only)
- **Primary keyword** included
- **Alternatives** if multiple valid options
- **Reference**: [Alignify URL optimization](https://alignify.co/zh/seo/url-optimization)
Related Skills
- **url-structure**: URL hierarchy, site structure; references this skill for slug conventions
- **canonical-tag**: When changing slugs, set up 301 redirects
- **article-page-generator**: Article URL slugs
- **blog-page-generator**: Blog post URL slugs
- **glossary-page-generator**: Glossary term slugs
- **products-page-generator**: Product page slugs
- **customer-stories-page-generator**: Case study page slugs
- **resources-page-generator**: Resource page slugs
- **features-page-generator**: Per-feature page slugs
Markdown skill library for AI agents - SEO, content, pages, paid ads, channels, strategies. Add project context + skills; your agent delivers tailored, production-ready output. Works with Cursor, Claude Code, OpenClaw, Lovable, and any AI that reads markdown.
Repo: kostja94/marketing-skills
Other skills on kostja94-marketing-skills.
- /google-search-console
When the user wants to analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries,"
Open skill - /seo-monitoring
When the user wants to build an SEO data analysis system, monitor indexing/traffic/keywords/backlinks, or set up benchmarks. Also use when the user mentions "SEO data analysis," "SEO monitoring," "article database," "traffic benchmark," "penalty recovery," "SEO work document,"
Open skill - /ai-traffic
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to
Open skill - /traffic
When the user wants to analyze website traffic sources, attribution, or dark traffic. Also use when the user mentions "traffic sources," "dark traffic," "direct traffic," "UTM parameters," "traffic attribution," "channel attribution," "attribution optimization," "channel
Open skill - /tracking
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event
Open skill - /community-forum
When the user wants to promote via forums, communities, or invite users to join a community. Also use when the user mentions "forum promotion," "Indie Hacker," "Hacker News," "community growth," "Discord promotion," "vertical community," "brand encyclopedia," "Wikipedia,"
Open skill

