tag-taxonomy

Enforce consistent tagging across the Obsidian wiki using a controlled vocabulary. Use this skill when the user says "fix my tags", "normalize tags", "clean up tags", "tag audit", "what tags should I use", "tag taxonomy", or whenever you're creating or updating wiki pages and need to choose the right tags. Also trigger when the user asks about tag conventions, wants to add a new tag to the taxonomy, or says "my tags are a mess". Always consult this skill's taxonomy file before assigning tags to any wiki page.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured, actionable, and concise, with clear per-mode workflows and concrete examples. The main gap is an explicit validation/feedback loop for the destructive batch normalization step, which keeps workflow_clarity just below the top anchor.

Suggestions

Add an explicit validation checkpoint before writing normalized frontmatter in Mode 2 (e.g., re-read the page after write to confirm tags are canonical and ≤5), forming a validate->fix->retry loop for the destructive batch operation.

Move the full audit-report markdown template and the before/after normalization example into a separate reference file, keeping SKILL.md as a lean overview that links to it.

Tighten repeated framing (the controlled-vocabulary purpose and taxonomy-file role appear in Before You Start, The Taxonomy File, and the intro); state it once and reference it.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and assumes Claude's competence; minor over-explanation such as restating the controlled-vocabulary framing and the taxonomy-file purpose in multiple sections rather than once.	4 / 5
Actionability	Provides concrete glob patterns, frontmatter YAML examples, log-line templates, and QMD commands that are executable; minor gaps such as no explicit tool/script for extraction and a templated audit report rather than generation logic.	4 / 5
Workflow Clarity	Four modes are each sequenced into numbered steps with a validation-leaning "ask the user before making changes to unknown tags" checkpoint and log-after-operations step; however the destructive batch normalization lacks an explicit validate-before-write feedback loop, capping it just under 5.	4 / 5
Progressive Disclosure	Well-organized into named modes/sections with the taxonomy file correctly deferred to an external path; inline audit-report and example blocks could be moved to a reference file, but overall navigation and structure are good.	4 / 5
	Total	16 / 20 Passed

Description

91%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concrete, trigger-rich, and explicitly answers both what and when, hitting the upper anchors across most dimensions. Its only weak spot is a slightly broad trigger tied to general wiki page creation, which raises minor conflict risk.

Dimension	Reasoning	Score
Specificity	Names the domain (tagging/controlled vocabulary) and several concrete actions (normalize tags, fix tags, audit, add new tag, choose right tags), with minor gaps such as no mention of reporting or migration specifics.	4 / 5
Completeness	Explicitly answers both what ("Enforce consistent tagging... using a controlled vocabulary") and when ("Use this skill when the user says..." with concrete trigger phrases), satisfying both halves concretely.	5 / 5
Trigger Term Quality	Comprehensive coverage of natural phrases users would say ("fix my tags", "normalize tags", "tag audit", "tag taxonomy", "my tags are a mess") plus synonyms and the underlying need (choosing tags when creating pages).	5 / 5
Distinctiveness Conflict Risk	Clear niche (tag taxonomy/normalization) with distinct triggers; minor overlap risk with general wiki/page skills since it also triggers when "creating or updating wiki pages".	4 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Ar9av/obsidian-wiki
Path: .skills/tag-taxonomy/SKILL.md
Commit: 52c9f2b

Reviewed: about 23 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.