Skill Detail

Generate stable URL slugs from multilingual titles before publishing pages, docs, or filenames

Use python-slugify when an agent has messy human titles and needs safe, repeatable slugs for URLs, filenames, or record IDs. This skill stays tightly focused on transliteration and normalization, not routing, redirects, or full publishing workflows.

Content Writing & SEOMulti-Framework
Content Writing & SEO Multi-Framework Security Reviewed
โญ 1.6k GitHub stars
INSTALL WITH ANY AGENT
npx skills add agentskillexchange/skills --skill generate-stable-url-slugs-from-multilingual-titles-before-publishing-pages-docs-or-filenames Copy
Works best when you want a reusable capability, not another fragile one-off prompt.
At a glance
Tools required
Python, pip
Install & setup
pip install python-slugify
Author
un33k
Publisher
GitHub User
Last updated
Apr 12, 2026
Quick brief

Tool: python-slugify

How it works

What this skill actually does

This skill gives an agent a clean, bounded way to turn human-written titles into stable machine-safe slugs. python-slugify is useful when titles include spaces, punctuation, accented characters, non-Latin scripts, or inconsistent separators and the next automation step needs a predictable string for a URL, filename, content key, or folder name. The agent behavior is straightforward: take raw text, normalize entities and punctuation, transliterate Unicode when needed, apply stopword and separator rules, honor length limits, and emit a slug that can be reused consistently across systems.

Invoke this skill before creating pages, docs, image filenames, knowledge-base articles, export bundles, or database records where the identifier needs to be readable and repeatable. It is particularly strong in multilingual publishing or ingestion workflows, where a basic lowercase-and-dashes helper often breaks on real-world input.

The scope boundary is what keeps this from becoming a generic product card. This skill does not publish the page, manage redirects, choose SEO keywords, or operate a CMS. It does one narrow job: convert source text into a slug under clear rules. That narrow boundary makes it easy to compose with site generators, CMS APIs, file storage jobs, content migration scripts, and naming conventions enforced elsewhere.

Typical integration points include WordPress or headless CMS creation flows, static-site generators, file packaging jobs, docs repositories, and import pipelines that need stable identifiers before writing records downstream.