CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tag-taxonomy

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.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

68%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.

A well-organized, largely executable instruction set covering audit, normalization, tagging, and vocabulary extension, with concrete commands, formats, and good separation of modes. Its main weakness is the batch normalization workflow lacking a post-write validation/feedback loop, which caps workflow clarity at 3; the mock audit report is also slightly longer than needed as a format illustration.

Suggestions

Add a verification step at the end of Mode 2 (Tag Normalization): re-run the audit scan and confirm unknown/alias tags are zero before reporting completion, creating an explicit fix-and-recheck feedback loop for the batch rewrite.

Trim the illustrative audit report to its structural skeleton (one or two example rows per table) so the output format is conveyed without a page of fabricated counts.

Move the full memory-sync/QMD procedure detail into the referenced MEMORY.md (or a short references/ file in this skill's bundle) and keep only the one-command summary inline.

DimensionReasoningScore

Conciseness

The body is largely lean — rules, a compact visibility-tag table, and a worked before/after YAML example with no padding explaining concepts Claude already knows. The full mock audit report (lines 69–101) with fabricated counts is somewhat longer than needed to convey the output format, which is a minor trim opportunity; it is far from the noticeably-verbose anchor 2 and mostly at anchor 4.

4 / 5

Actionability

Guidance is mostly executable: a concrete Glob pattern with exclusions, a ready-to-use report template, a copy-paste YAML before/after example, and runnable commands (`obsidian-wiki memory sync ...`, `${QMD_CLI:-qmd} update|embed|ls`). Minor gaps — e.g., "Write the updated frontmatter" and "Extract: tags field from YAML frontmatter" describe intent without exact mechanics — keep it just below fully copy-paste-ready anchor 5.

4 / 5

Workflow Clarity

Each of the four modes has a clear sequenced procedure, and there are some checkpoints ("Ask the user before making changes to unknown tags"; audit-before-normalize; QMD failure handled without rollback). However, Mode 2 rewrites frontmatter in batch across many pages with no post-write verification (e.g., re-running the audit to confirm zero non-canonical tags remain), and the rubric explicitly caps batch operations lacking validation/feedback loops at 3.

3 / 5

Progressive Disclosure

The single-file body is well-sectioned (Before You Start, taxonomy, reserved tags, four modes, post-op, QMD) with external procedures signaled one level deep (`llm-wiki/SKILL.md` config protocol, `.skills/llm-wiki/references/MEMORY.md`). The structure matches the good-organization anchor 4; the memory-sync details and the long audit-report template could arguably live in a reference file, and one reference path is external to the skill bundle, so it does not reach the cleanly split anchor 5.

4 / 5

Total

15

/

20

Passed

Description

88%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.

A strong third-person description that explicitly states what the skill does and when to use it, with concrete action verbs covering the full tag-vocabulary lifecycle. Trigger terminology is natural and domain-specific; only minor synonym coverage and a small overlap with general wiki-authoring contexts keep it from full marks.

DimensionReasoningScore

Specificity

"Apply and maintain the wiki's controlled tag vocabulary. Use for choosing, normalizing, auditing, or extending tags" names the domain plus multiple concrete actions (choosing, normalizing, auditing, extending) that comprehensively cover the tag-vocabulary lifecycle. Anchor 4 would apply if there were minor coverage gaps, but the four verbs span selection, correction, inspection, and growth of the vocabulary.

5 / 5

Completeness

The 'what' is explicit ("Apply and maintain the wiki's controlled tag vocabulary") and the 'when' is an explicit 'Use for...' clause with concrete trigger situations ("when creating or updating wiki pages; consult the taxonomy before assigning tags"). Both are present, explicit, and concrete, matching the anchor-5 example structure; not 4, since the 'when' is specific rather than generic.

5 / 5

Trigger Term Quality

Natural terms include "tags", "tag vocabulary", "taxonomy", "wiki pages", "normalizing", "auditing" — phrases a user would plausibly say when needing this skill. A few natural synonyms/variations (e.g., "label", "categorize", "keyword cleanup") are missing, so it falls just short of the comprehensive-synonym anchor 5 but is clearly above anchor 3.

4 / 5

Distinctiveness Conflict Risk

"Controlled tag vocabulary", "taxonomy", and "tag audit/normalization" carve a clear niche with minimal conflict risk. Slight overlap remains with a generic wiki page-authoring skill via "when creating or updating wiki pages", keeping it below the minimal-conflict anchor 5 but well above the somewhat-specific anchor 3.

4 / 5

Total

18

/

20

Passed

Validation

100%

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

Reviewed

Table of Contents

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.