url-slug-generator

kostja94/marketing-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/kostja94/marketing-skills --skill url-slug-generator
0 commentsdiscussion
summary

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.

skill.md

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

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
how to use url-slug-generator

How to use url-slug-generator on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add url-slug-generator
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/kostja94/marketing-skills --skill url-slug-generator

The skills CLI fetches url-slug-generator from GitHub repository kostja94/marketing-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/url-slug-generator

Reload or restart Cursor to activate url-slug-generator. Access the skill through slash commands (e.g., /url-slug-generator) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.851 reviews
  • Anika Lopez· Dec 24, 2024

    We added url-slug-generator from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Chen Haddad· Dec 16, 2024

    url-slug-generator has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Daniel White· Dec 12, 2024

    Useful defaults in url-slug-generator — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Daniel Martin· Dec 12, 2024

    url-slug-generator reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Rahul Santra· Nov 15, 2024

    Registry listing for url-slug-generator matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Isabella Ghosh· Nov 15, 2024

    Solid pick for teams standardizing on skills: url-slug-generator is focused, and the summary matches what you get after install.

  • Noah Li· Nov 11, 2024

    Registry listing for url-slug-generator matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Isabella Desai· Nov 7, 2024

    url-slug-generator fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • William Gupta· Nov 3, 2024

    url-slug-generator is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Charlotte Sethi· Oct 26, 2024

    We added url-slug-generator from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

showing 1-10 of 51

1 / 6