obsidian-vault-architect

Designs and enforces folder structure, naming conventions, and template standards for Obsidian vaults.

Quality

50%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/obsidian-vault-architect/SKILL.md

Quality

Content

50%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 skill is concise and clearly sectioned, but its workflow is descriptive rather than executable and the destructive rename/batch operations lack explicit validation-feedback loops, capping workflow clarity. No bundle files exist to support progressive disclosure despite the sectioned structure.

Suggestions

Add concrete, executable guidance: example template skeletons, canonical tag-set examples for META/tags.md, and a sample rename-batch command or script in scripts/.

Insert an explicit validation checkpoint in the Enforce step (e.g., preview the rename/move batch, verify no broken wikilinks, then apply) to establish a validate-fix-retry feedback loop.

Move detailed material (template definitions, full tag taxonomy, PARA hierarchy examples) into reference files under references/ and link to them from the body to realize progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient and assumes Claude's competence (short Purpose, terse workflow bullets, compact Inputs/Outputs) with only minor explanatory padding like the '(PARA or custom)' and '(user must confirm before execution)' asides, sitting clearly above the 3-anchor.	4 / 5
Actionability	Guidance is high-level and descriptive rather than executable: 'Survey current vault structure', 'Create note templates for each domain', 'Apply naming conventions to existing notes via rename batch' give no concrete commands, scripts, or templates, matching the minimal-guidance 2-anchor.	2 / 5
Workflow Clarity	Six sequenced workflow steps are clearly listed, but per the rubric a destructive/batch skill (rename/move batches of notes) without explicit validation-verification checkpoints cannot score above 3; the Safety section adds confirmation but no validate/retry feedback loop.	3 / 5
Progressive Disclosure	The body is well-sectioned but references are only two external web links rather than in-bundle detail files; the empty references/scripts/assets directories confirm no one-level-deep bundle materials exist, so navigation depth is unutilized despite clear section structure.	3 / 5
	Total	12 / 20 Passed

Description

50%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 clearly conveys what the skill does and occupies a distinct niche, but it omits any explicit 'Use when...' trigger guidance, which caps completeness and limits trigger-term quality. Adding a concrete usage clause would lift it toward the top anchors.

Suggestions

Add an explicit 'Use when ...' clause naming natural triggers (e.g., 'Use when organizing an Obsidian vault, setting up folder structure, or enforcing naming/template conventions').

Tighten capability phrasing toward concrete operations (e.g., 'Audits vault structure, proposes PARA/custom hierarchies, generates templates, and enforces rename batches') to reach the specificity 4-5 anchors.

Include natural synonyms users say (e.g., 'Obsidian notes', 'vault organization', 'MOC', '.md templates') to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (Obsidian vaults) and several concrete actions ('folder structure, naming conventions, and template standards'), but the actions are somewhat generic compared to the 'Extract text, fill forms, merge documents' level of the 5-anchor; it lists categories of work rather than fully concrete operations.	3 / 5
Completeness	It clearly answers 'what does this do' but provides no explicit 'when should Claude use it' / 'Use when...' trigger clause, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Contains relevant keywords ('Obsidian vaults', 'folder structure', 'naming conventions', 'templates') that a user might say, but lacks common synonyms or extensions and has no natural 'when...' phrasing in the description itself.	3 / 5
Distinctiveness Conflict Risk	The niche (Obsidian vault architecture) is fairly distinct with clear triggers ('folder structure, naming conventions, template standards'); only minor overlap risk with closely related Obsidian skills, so it sits noticeably above the 3-anchor.	4 / 5
	Total	13 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: pvnkmnk/AgenticSelfHostSkills
Path: skills/obsidian-vault-architect/SKILL.md
Commit: 0f62e6b

Reviewed: 4 days 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.