wiki-update

Sync the current project's knowledge into the Obsidian wiki. Use this skill from any project when the user says "update wiki", "sync to wiki", "save this to my wiki", "update obsidian", or wants to distill what they've been working on into their knowledge base. This is the cross-project skill that lets you push knowledge from wherever you are into the vault. Accepts inline named-vault routing like "@work update wiki" via the shared Config Resolution Protocol.

Quality

89%

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

88%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 high-quality, actionable workflow document with strong validation and feedback loops appropriate to a batch write operation. The main improvement areas are tightening the verbose Step 3b and shipping the referenced shared-protocol material as bundled reference files so the cross-skill references resolve locally.

Suggestions

Tighten Step 3b: move the five focus-map handling rules into a short checklist and defer the codegraph install/offer detail to a reference file, since it inflates the core flow.

Fix the numbering in 'Before You Start' (it jumps 1 → 3 → 4), which is a small but real clarity flaw in the entry sequence.

Bundle the shared protocols referenced from llm-wiki/SKILL.md (Config Resolution, Link Format, Provenance Markers) as local reference files under references/ so the skill's navigation resolves without assuming another skill is present.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of concepts Claude already knows (no 'what is a wiki' padding), with purposeful heuristics like the worth/not-worth-distilling lists; a few sections, notably the long Step 3b focus-map guidance, could be trimmed.	4 / 5
Actionability	Provides copy-paste-ready bash commands (git merge-base, obsidian-wiki code-understand, qmd update/embed/get/ls), a concrete JSON manifest template, a full frontmatter template, and a directory layout — all executable with clearly marked variables.	5 / 5
Workflow Clarity	A clearly sequenced 7-step process with explicit validation checkpoints (merge-base ancestor check, stop-if-no-change, QMD page verification) and feedback loops (rebase/force-push fallback to full scan, stale-relationship pruning, optional-step GUARDs).	5 / 5
Progressive Disclosure	Well-organized into labeled steps with one-level-deep, clearly signaled references to shared protocols in llm-wiki/SKILL.md (Config Resolution, Link Format, Provenance Markers); held back from a 5 because the single file is fairly dense and the referenced files are external to this skill's bundle (no bundle files ship alongside).	4 / 5
	Total	18 / 20 Passed

Description

90%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 description: third-person, concise, and explicit about both capability and trigger conditions with natural user phrases. The only soft spot is specificity, since the single sync/distill capability is restated rather than expanded into multiple concrete actions.

Dimension	Reasoning	Score
Specificity	Names the domain ('sync knowledge into the Obsidian wiki') and the concrete action of distilling/syncing plus inline named-vault routing, but these are restatements of one capability rather than the multiple distinct actions the top anchor rewards.	3 / 5
Completeness	Explicitly states both what ('Sync the current project's knowledge into the Obsidian wiki') and when ('Use this skill ... when the user says ...') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Lists several natural phrases a user would actually say — 'update wiki', 'sync to wiki', 'save this to my wiki', 'update obsidian' — covering synonyms and variations comprehensively.	5 / 5
Distinctiveness Conflict Risk	Carves a clear niche as the cross-project skill that pushes knowledge into the vault, with distinct triggers ('update wiki', 'update obsidian') that are unlikely to fire for unrelated skills.	5 / 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/wiki-update/SKILL.md
Commit: 52c9f2b

Reviewed: 1 day 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.