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

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

78%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 highly actionable, well-sequenced skill with strong validation feedback loops and concrete copy-paste commands throughout. It is somewhat verbose in its distillation heuristics and frontmatter mechanics, and relies on prose pointers to sibling skills rather than a structured reference index, which lightly caps conciseness and progressive disclosure.

Suggestions

Tighten the 'Worth distilling / Not worth distilling' lists and provenance rationale into a compact heuristic or move them to a reference file; Claude already knows how to judge what is worth recording.

Add a small 'References' section indexing the llm-wiki sections (Config Resolution, Link Format, Provenance Markers, .manifest.json contract) as a navigable list rather than inline prose pointers.

Move the full page-frontmatter template into a bundled template file and reference it, keeping only the field-purpose summary inline to reduce token weight.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete bash snippets and tight tables, but sections like the 'Worth distilling / Not worth distilling' lists and repeated provenance rationale re-explain judgment Claude already has, and the page-format block restates frontmatter mechanics at length.	3 / 5
Actionability	Copy-paste-ready commands throughout (git merge-base check, obsidian-wiki code-understand invocations, qmd update/embed/get/ls) plus a complete page-frontmatter template and concrete manifest/index/log/hot update formats — fully executable and covers the common cases.	5 / 5
Workflow Clarity	Seven clearly sequenced steps with explicit validation checkpoints and feedback loops: the git merge-base ancestor check with rebase/force-push fallback (Step 2), prune-stale-relationships verification (Step 3b), and QMD refresh with failure/skip reporting (Step 7) — exactly the validate→fix→retry pattern the rubric rewards.	5 / 5
Progressive Disclosure	Well-organized into clearly signaled steps and sub-sections, and it points one level deep to llm-wiki/SKILL.md sections for shared protocol detail rather than duplicating them; however no bundle reference/scripts/assets files exist and several shared protocols are referenced by prose pointer rather than a navigable file index, leaving minor organization gaps.	4 / 5
	Total	17 / 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 description that clearly states what the skill does and when to use it, with rich natural trigger phrases and the distinctive cross-project-push framing. Minor overlap risk with sibling wiki skills and slightly limited action enumeration keep it just short of perfect.

Dimension	Reasoning	Score
Specificity	Names the domain (sync project knowledge into the Obsidian wiki) plus several concrete actions — distill what they've been working on, push knowledge into the vault, route via inline named-vault routing — but is light on enumerated mechanical actions, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers 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 score-5 anchor.	5 / 5
Trigger Term Quality	Comprehensive natural trigger phrases users would actually say ("update wiki", "sync to wiki", "save this to my wiki", "update obsidian") plus the @name inline routing form; covers synonyms and the product name.	5 / 5
Distinctiveness Conflict Risk	The Obsidian-wiki / cross-project-push niche is distinct with clear triggers, but the generic phrasing 'distill what they've been working on into their knowledge base' could lightly overlap with a sibling wiki-ingest skill.	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/wiki-update/SKILL.md
Commit: 29b810d

Reviewed: 5 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.