Khazix WeChat Article Writer
KKKKhazix/khazix-skills
Writes long-form WeChat official account articles in the personal style of the Khazix account, from briefs, links, PDFs or rough notes, with a topic quality check.
A skill your agent uses when applies to blog posts, product pages, and any content page with editable URL slugs.
Install Slug Keywords
$ npx skills add thedaviddias/Front-End-Checklist --skill slug-keywords -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install thedaviddias/Front-End-Checklist slug-keywords --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/slug-keywords .claude/skills/slug-keywords && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "slug-keywords" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/slug-keywords into .claude/skills/slug-keywords/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slug-keywords", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/slug-keywordsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add thedaviddias/Front-End-Checklist --skill slug-keywords -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install thedaviddias/Front-End-Checklist slug-keywords --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/slug-keywords .agents/skills/slug-keywords && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "slug-keywords" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/slug-keywords into .agents/skills/slug-keywords/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slug-keywords", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thedaviddias/Front-End-Checklist --skill slug-keywords -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install thedaviddias/Front-End-Checklist slug-keywords --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/slug-keywords .cursor/skills/slug-keywords && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "slug-keywords" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/slug-keywords into .cursor/skills/slug-keywords/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slug-keywords", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/thedaviddias/Front-End-Checklist.git --path skills/slug-keywords--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add thedaviddias/Front-End-Checklist --skill slug-keywords -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install thedaviddias/Front-End-Checklist slug-keywords --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/slug-keywords .gemini/skills/slug-keywords && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "slug-keywords" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/slug-keywords into .gemini/skills/slug-keywords/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slug-keywords", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install thedaviddias/Front-End-Checklist slug-keywordsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add thedaviddias/Front-End-Checklist --skill slug-keywords -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/slug-keywords .github/skills/slug-keywords && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "slug-keywords" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/slug-keywords into .github/skills/slug-keywords/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slug-keywords", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thedaviddias/Front-End-Checklist --skill slug-keywords -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install thedaviddias/Front-End-Checklist slug-keywords --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/slug-keywords .opencode/skills/slug-keywords && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "slug-keywords" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/slug-keywords into .opencode/skills/slug-keywords/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slug-keywords", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
slug-keywords- GitHub stars
- 74k
- Token cost
- ~546 tokens
- SKILL.md length
- 244 words
- Files
- 2 (incl. references)
- Skills in repo
- 390
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when applies to blog posts, product pages, and any content page with editable URL slugs.
- Applies to blog posts
- SKILL.md covers Quick Reference, Check, Fix and Explain, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Any content page with editable URL slugs
What it does
Slug Keywords is an agent skill from thedaviddias/Front-End-Checklist. Use when applies to blog posts, product pages, and any content page with editable URL slugs. Use when building a URL strategy for a new site or auditing existing URLs for keyword inclusion.
Its SKILL.md is about 550 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/rule.md`).
It sits in Writing & Content, covering Blog and article writing. The repository describes itself as: 🗂 The essential checklist for modern web development, for humans and AI agents. The licence is MIT.
When your agent uses it
- Applies to blog posts
- Any content page with editable URL slugs
- Building a URL strategy for a new site
- Auditing existing URLs for keyword inclusion
Example prompts
- “/slug-keywords”
What it can do on your machine
Read from SKILL.md and the folder at commit e8d14d0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
frontendchecklist.io
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Slug Keywords loads about 546 tokens when it runs, and up to ~1.5k if it reads all its reference files. Until then it costs about 51 tokens; SKILL.md has 244 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from thedaviddias/Front-End-Checklist at commit e8d14d0, republished under its MIT licence (© thedaviddias). 244 words, ~546 tokens.
Download SKILL.mdSave it as
.claude/skills/slug-keywords/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- slug-keywords
- description
- Use when applies to blog posts, product pages, and any content page with editable URL slugs. Use when building a URL strategy for a new site or auditing existing URLs for keyword inclusion.
- metadata.category
- seo
- metadata.priority
- medium
- metadata.difficulty
- beginner
- metadata.estimatedTime
- 10
- metadata.source
- frontendchecklist.io
- metadata.url
- https://frontendchecklist.io/rules/seo/slug-keywords
Include keywords in URL slugs
Descriptive URL slugs help users and search engines understand page content before visiting — a URL like /buy-running-shoes-women communicates topic intent that /products/4832 does not.
Quick Reference
- URL slugs should contain the primary keyword of the page in lowercase, hyphen-separated words
- Avoid numeric IDs (
/page?id=12345), random strings, or meaningless paths (/p/a/) in public URLs - Keep slugs concise: 3–5 meaningful words is typical; avoid keyword stuffing
- Google uses URL words as a weak ranking signal and users use them to assess page relevance before clicking
Check
Crawl the site and examine URL paths. Flag URLs that contain: numeric IDs only, random strings, session tokens, dates without a descriptive slug, or overly generic words (/page, /item, /post). Verify slugs are lowercase and hyphen-separated.
Fix
Rewrite slugs to include the page's primary keyword in natural language. Use lowercase letters and hyphens as word separators. Set up 301 redirects from old URLs to new slugs. Update internal links, sitemaps, and canonical tags.
Explain
Explain how keyword-rich URL slugs improve click-through rates in search results, serve as a weak relevance signal for search engines, and make URLs easier to share and understand.
Code Review
Review metadata generation, rendered HTML, structured data, and response headers related to Include keywords in URL slugs. Flag exact routes or templates where search-facing output violates the rule, and describe how to verify the final page output.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/seo/slug-keywords
© thedaviddias, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in skills/slug-keywords of thedaviddias/Front-End-Checklist.
- SKILL.md
- references/rule.md
Open the folder on GitHubat commit e8d14d0
Compare with similar skills
Slug Keywords next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Slug Keywords this skillthedaviddias/Front-End-Checklist | 74k | — | ~546 | Automated safety check: Pass | MIT | |
| Khazix WeChat Article WriterKKKKhazix/khazix-skills | 21k | 1 repos | ~2.9k | Automated safety check: Pass | MIT | |
| Figurevectorize-io/hindsight | 48k | — | ~1.9k | Automated safety check: Pass | MIT | |
| SepiaNanako0129/sepia | 3.1k | — | ~3.6k | Automated safety check: Pass | MIT | |
| Blog Post Draftingluongnv89/claude-howto | 42k | — | ~2.1k | Automated safety check: Pass | MIT | |
| Notion To Blogwasp-lang/wasp | 19k | — | ~922 | Automated safety check: Pass | MIT |
Similar skills
Figure
vectorize-io/hindsight
Draw an animated figure (boxes, arrows, moving data) as one self-contained SVG for a GitHub README, PR, issue or blog post.
Sepia
Nanako0129/sepia
Make AI-generated writing read as human-written, in fiction and in professional prose.
Blog Post Drafting
luongnv89/claude-howto
Guides drafting a blog post from an idea and optional source material: research, brainstorming, outlining and version-tracked drafts, with user approval at each step.
Notion To Blog
wasp-lang/wasp
Transfer a blog post from Notion to the Wasp blog. An agent skill from wasp-lang/wasp.
Blog Post
nteract/semiotic
Author a new entry for the Semiotic blog. An agent skill from nteract/semiotic.
More from thedaviddias/Front-End-Checklist
All 390 skills in this repoContent Dates Audit
thedaviddias/Front-End-Checklist
Audits article and blog pages for visible publish dates, Article JSON-LD with datePublished and dateModified, and Open Graph time tags, then fixes what is missing.
FAQPage Schema Markup
thedaviddias/Front-End-Checklist
Adds, checks and fixes FAQPage JSON-LD on pages with visible question-and-answer sections so it matches what readers see and can qualify for rich results.
Favicon Audit and Setup
thedaviddias/Front-End-Checklist
Checks that a site's favicon is linked, reachable and large enough for Google search results, and sets up ICO, SVG and Apple touch icon files when they are missing.
Content Freshness Signals
thedaviddias/Front-End-Checklist
Audits article pages for freshness signals, covering the Last-Modified header, Article JSON-LD dateModified and a visible last-updated date, and fixes mismatches.
Geo Meta Tags Audit
thedaviddias/Front-End-Checklist
Audits and fixes geo.region, geo.placename and geo.position meta tags on regional pages, noting where they help (Bing) and where they do not (Google).
Improve a Front-End Checklist Rule
thedaviddias/Front-End-Checklist
Scores and rewrites a Front-End Checklist rule MDX file against a scored quality rubric, replacing generic stub prompts with specific, actionable ones.
Related
Categories
Questions about Slug Keywords
What does Slug Keywords do?
A skill your agent uses when applies to blog posts, product pages, and any content page with editable URL slugs. Slug Keywords is an agent skill from thedaviddias/Front-End-Checklist. Use when applies to blog posts, product pages, and any content page with editable URL slugs.
When should I use Slug Keywords?
Slug Keywords fits situations like: applies to blog posts; any content page with editable URL slugs; building a URL strategy for a new site; auditing existing URLs for keyword inclusion.
How do I install Slug Keywords in Claude Code?
Run `npx skills add thedaviddias/Front-End-Checklist --skill slug-keywords -a claude-code`. Or copy the skill folder (skills/slug-keywords in thedaviddias/Front-End-Checklist) into .claude/skills/slug-keywords in your project. Claude Code loads it when a task matches its description.
How do I install Slug Keywords in Codex?
Run `npx skills add thedaviddias/Front-End-Checklist --skill slug-keywords -a codex`. Or copy the skill folder (skills/slug-keywords in thedaviddias/Front-End-Checklist) into .agents/skills/slug-keywords in your project. Codex loads it when a task matches its description.
Can I use Slug Keywords in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add thedaviddias/Front-End-Checklist --skill slug-keywords -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/slug-keywords, .gemini/skills/slug-keywords, .github/skills/slug-keywords and .opencode/skills/slug-keywords in your project.
What does Slug Keywords need to run?
SKILL.md names no scripts, command-line tools or credentials: Slug Keywords is instructions for the agent only.
Does Slug Keywords access the network?
SKILL.md names 1 domain. As links in the text: frontendchecklist.io. This is read from the text; nothing was executed.
Is Slug Keywords safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Slug Keywords use?
Slug Keywords is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Slug Keywords use?
About 546 tokens (SKILL.md is roughly 2.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 999 tokens, read only when the agent opens those files.
What are the alternatives to Slug Keywords?
Skills that share tags, products or a category with Slug Keywords: Khazix WeChat Article Writer (KKKKhazix/khazix-skills, 21k stars), Figure (vectorize-io/hindsight, 48k stars), Sepia (Nanako0129/sepia, 3.1k stars) and Blog Post Drafting (luongnv89/claude-howto, 42k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Slug Keywords?
thedaviddias (a GitHub user) maintains it in thedaviddias/Front-End-Checklist, which has 74,421 GitHub stars. The repository holds 390 skills in this directory. The repository was last updated on October 6, 2026.
Source: thedaviddias/Front-End-Checklist on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.