
Tag Taxonomy
Apply and maintain the wiki's controlled tag vocabulary.
Install
npx skills add Ar9av/obsidian-wiki --skill tag-taxonomy -g -a claude-code -y- Repository
- Ar9av/obsidian-wiki3.6k
- Category
- Engineering
- Updated
- 3d ago
- License
- MIT
- Context cost
- Mediumabout 1,727 tokens
- Runs scripts
- No, instructions only
What it does
Apply and maintain the wiki's controlled tag vocabulary. Use for choosing, normalizing, auditing, or extending tags when creating or updating wiki pages; consult the taxonomy before assigning tags.
Tag Taxonomy, Controlled Vocabulary for Wiki Tags
You are enforcing consistent tagging across the wiki by normalizing tags to a controlled vocabulary.
Before You Start
- Resolve config, follow the Config Resolution Protocol in
llm-wiki/SKILL.md(inline@nameoverride → walk up CWD for.env→ global config → prompt setup). This givesOBSIDIAN_VAULT_PATH - Read
$OBSIDIAN_VAULT_PATH/_meta/taxonomy.md, this is the canonical tag list - Read
index.mdto understand the wiki's scope
The Taxonomy File
The canonical tag vocabulary lives at $OBSIDIAN_VAULT_PATH/_meta/taxonomy.md. It defines:
- Canonical tags, the tags that should be used
- Aliases, common alternatives that should be mapped to the canonical form
- Rules, max 5 tags per page, lowercase/hyphenated, prefer broad over narrow
- Migration guide, specific renames for known inconsistencies
Always read this file before tagging. It's the source of truth.
Reserved System Tags
visibility/ is a reserved tag group with special rules. These tags are not domain or type tags and are managed separately from the taxonomy vocabulary:
| Tag | Purpose |
|---|---|
visibility/public | Explicitly public, shown in all modes (same as no tag) |
visibility/internal | Team-only, excluded in filtered query/export mode |
visibility/pii | Sensitive data, excluded in filtered query/export mode |
Rules for visibility/ tags:
- They do not count toward the 5-tag limit
- Only one
visibility/tag per page - Omit entirely when content is clearly public, no tag needed
- Never add
visibility/internaljust because content is technical; use it only for genuinely team-restricted knowledge - When running a tag audit, report
visibility/tag usage separately, do not flag them as unknown or non-canonical
When normalizing tags, leave visibility/ tags untouched, they are not subject to alias mapping.
