daily-update

Run the daily wiki maintenance cycle: check all source freshness, update the index, and regenerate hot.md. Use this skill when the user says "/daily-update", "run the daily update", "update everything", "morning sync", "refresh the wiki index", or when triggered by the scheduled 9 AM run (launchd, systemd timer, or cron). Also use to set up or verify the cron + terminal notification infrastructure for the first time ("set up the daily cron", "install the terminal notification", "how do I get the morning reminder?").

Quality

90%

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

85%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-sequenced, lean operational runbook with genuine validation checkpoints (impl-validator, unmigrated-vault stop). Its weaknesses are the single-file monolith — Setup Mode platform recipes and the QMD boilerplate should live in reference files — and minor executability gaps such as the undefined `obsidian_wiki_config_dir` helper.

Suggestions

Move Setup Mode's platform-specific install recipes (launchd plist, systemd service/timer, crontab, shell-rc notification wiring) into a references/setup.md file and keep a short platform-dispatch summary in SKILL.md.

Define or inline the resolution of `obsidian_wiki_config_dir` (the XDG-style vs legacy path logic described in Setup Mode Step 5) where it is first used in 'Before You Start', since the state-dir derivation currently depends on an undefined helper.

Extract the generic 'QMD Refresh After Vault Writes' block into a shared reference file (it appears to be cross-skill boilerplate) and reference it from SKILL.md to cut duplicated context.

Dimension	Reasoning	Score
Conciseness	Lean, imperative runbook: no concept explanations, no library tutorials, every section is operational (commands, state-file writes, platform dispatch). Guardrail notes like "Do not enumerate pages with `find` and edit the index by hand" earn their tokens; every token earns its place.	5 / 5
Actionability	Mostly copy-paste-ready commands (`obsidian-wiki memory index/hot`, state-file writes, launchd/systemd/cron install snippets, impl-validator spec), but with minor gaps: `obsidian_wiki_config_dir` is invoked without being defined or resolved anywhere in the body, and `echo "<stale_count>"` is a placeholder rather than a computed value. Level 4 'concrete commands with minor gaps', not the fully executable level 5.	4 / 5
Workflow Clarity	Run Mode is a clearly sequenced Steps 1–7 with explicit validation: the impl-validator subagent checklist (timestamp within 60s, non-negative integer, hot.md updated field), "Apply any FAILs before logging", and a stop-and-escalate path if the vault is unmigrated. The batch-operation validation cap does not apply because feedback loops are present — matches the level-5 anchor with checklist and error recovery.	5 / 5
Progressive Disclosure	There are no bundle reference files at all; everything is inlined in a ~250-line SKILL.md. Content that belongs in separate files is inline: the Setup Mode's three platform-specific install recipes (launchd plist, systemd units, crontab), the shell-rc notification wiring, and the generic QMD Refresh block. Some structure (clear headers, two modes), but the split is missing — level 3, not 4.	3 / 5
	Total	17 / 20 Passed

Description

96%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: concrete actions, explicit 'Use when…' triggers with quoted user phrases, and a clearly delimited niche. The only weakness is the broadly generic trigger "update everything", which risks matching non-wiki update requests.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — "check all source freshness, update the index, and regenerate hot.md" — and additionally covers setup/verification of "the cron + terminal notification infrastructure". Coverage is comprehensive with no gaps, matching the top anchor rather than the 'minor gaps' level 4.	5 / 5
Completeness	Explicitly answers both questions: the "what" is the maintenance cycle (freshness check, index update, hot.md regeneration) and the "when" is a full "Use this skill when the user says…" clause with concrete trigger phrases. Clearly matches the level-5 anchor, not the level-4 'when could be more specific'.	5 / 5
Trigger Term Quality	Quotes literal natural phrases a user would say: "/daily-update", "run the daily update", "update everything", "morning sync", "refresh the wiki index", "set up the daily cron", "install the terminal notification", "how do I get the morning reminder?" — comprehensive synonym coverage including scheduled-trigger contexts (launchd, systemd timer, cron).	5 / 5
Distinctiveness Conflict Risk	The wiki-maintenance niche and named artifacts (hot.md, wiki index) are distinct, but the trigger "update everything" is generic enough to overlap with unrelated update/sync skills. Mostly distinct with minor overlap risk — level 4, not 5.	4 / 5
	Total	19 / 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/daily-update/SKILL.md
Commit: 972de66

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