create-glossary
Skill1 starsChanged 10 days agoMITView on GitHub
Use this skill when you want to create a glossary of files in current working directory
1 other project uses a version of this.
Adopted by
Most recently taken up by
- vladcheck/skillsword for word, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 1
- vladcheck/skills★ 1100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- analyze-session-pingpong-logsSkill
- deepseek-reasoning-tier-clarifierSkill
- defineSkill
- find-alternativesSkill
- get-note-links-from-textSkill
- gitlab-eas-tickets-publishSkill
- gitlab-mr-roundtripSkill
- git-rebuild-branchSkill
- git-sequentialSkill
- gost-report-rebuildSkill
- mattpocock-skills-researchSkill
- mirea-moodle-downloadSkill
- obsidian-add-links-to-noteSkill
- opsx-spec-validateSkill
- paretto-principleSkill
- publish-spec-gitlab-milestoneSkill
- publish-tickets-gitlabSkill
- solidSkill
- update-skills-via-skills-shSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 17
Not for: API docs (use doc generators) or cases where plain tree output suffices.
- Distinctive: line 54
Verifying one link in a browser: Run the decode-and-exists script over ALL hrefs.
- Distinctive: line 60
Every href percent-encoded and mechanically verified (0 broken).
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Create Glossary
Overview
Build a single self-contained HTML page listing links to all content files in the working directory, recursively, grouped by folder and in reading order. Links must actually resolve — a glossary with broken links is worse than none.
When to Use
- User asks for a "glossary", "index", "contents page", or "список ссылок" of files/folders
- Course repos, lesson dumps, document collections needing a navigable index
Not for: API docs (use doc generators) or cases where plain tree output suffices.
Core Pattern
- Scan recursively. Include content files (
.html,.pdf,.mp4); exclude the glossary file itself, dotfiles (.DS_Store), and junk. Add supplementary files (code snippets, zips) only if asked. - Order numerically, not lexicographically. Sort by the integer in each filename, so
1, 2, 10never becomes1, 10, 2. Don't rely on zero-padding. - Group by top-level folder (h2), then subfolder (h3). Use
<ol>for ordered items. - Clean display titles: strip vendor prefixes (
[Brand]), the numeric sort key, extension, trailing spaces. Clean group headings too. - Percent-encode every href with a script, never by hand. Python:
urllib.parse.quote(path, safe='/')— encodes spaces (%20) and brackets (%5B%5D), keeps Cyrillic literal. Raw spaces/brackets inhrefare invalid HTML; browsers tolerate them onfile://, but parsers and copied links break. - Verify mechanically, not by eye. Decode every href and assert the file exists:
import re, urllib.parse, pathlib, sys
root = pathlib.Path('.')
html = (root / 'glossary.html').read_text(encoding='utf-8')
hrefs = [h for h in re.findall(r'href="([^"]+)"', html) if not h.startswith('#')]
broken = [h for h in hrefs if not (root / urllib.parse.unquote(h)).exists()]
print(f'{len(hrefs)} links, {len(broken)} broken')
sys.exit(1 if broken else 0) # fix and re-run until 0 broken- Relative paths only — the glossary must survive the folder being moved or zipped.
Quick Reference
| Problem | Fix |
| Link 404s after click | href not encoded — rebuild with urllib.parse.quote |
1, 10, 2 order | sort by integer from filename, not string |
| Glossary lists itself | exclude output filename during scan |
| Ugly titles | strip prefix + number + extension + trailing space |
Common Mistakes
- Raw hrefs with spaces/brackets.
[Course] 01 Intro .htmlas a literalhrefis invalid HTML — encode:%5BCourse%5D%2001%20Intro%20.html. Note the trailing space before.html: encode it (%20.html), never trim the filename. - Lexicographic sort. String sort puts
10before2. Parse the number. - Listing the glossary itself on re-runs, plus dotfiles like
.DS_Store. Filter by extension allowlist and output-name exclusion. - Verifying one link in a browser. Run the decode-and-exists script over ALL hrefs; one broken out of a hundred is still a failure.
- Absolute paths (
/Users/...,file://) — break when the folder moves. - Guessing filenames instead of scanning. Real dumps have inconsistent naming (
QA-сессияvsQA - сессия, stray double spaces). Read the filesystem, never retype names.
Definition of Done
Every href percent-encoded and mechanically verified (0 broken); groups in folder order, items in numeric order, titles cleaned; single self-contained file, relative links only.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

