Skip to main content
skill CX Codex

daily-update — Claude Code skill: what it does, how to install

daily-update maintains an Obsidian wiki by checking source freshness, refreshing the index and hot.md, and setting up a daily scheduler when needed.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add Ar9av/obsidian-wiki --skill daily-update -a claude-code
Open on GitHub

What daily-update does

daily-update runs a maintenance cycle for an Obsidian wiki. It compares source file modification times with .manifest.json, classifies sources as fresh, stale, or missing, then calls obsidian-wiki memory index and obsidian-wiki memory hot. The index is reconciled with pages on disk, while hot.md receives refreshed activity and status sections.

The skill writes vault-scoped state, appends a record to log.md, and runs impl-validator after the cycle. A scheduled wiki-lint check can run in manual, daily, or weekly mode. Setup mode configures a 9 AM launch through launchd, systemd, or cron, with an optional terminal reminder.

If the vault is unmigrated, the cycle stops until obsidian-wiki memory migrate and then --apply are run. Check migration first when preparing a new vault.

What it helps with

  • check source freshness in .manifest.json
  • reconcile the page index with the vault contents
  • refresh hot.md and persist cycle state
  • configure a daily launch with launchd, systemd, or cron
  • run scheduled wiki-lint health checks

Example prompts for the agent

  • Run daily-update to refresh my Obsidian wiki this morning.
  • Set up daily-update to run through cron at 9 AM.
  • Check the vault, refresh the index and hot.md, then report stale sources.

How to install daily-update

1Skills CLI (Vercel)

npx skills add Ar9av/obsidian-wiki --skill daily-update -a claude-code

2Manually: put the files in place

~/.claude/skills/daily-update/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/daily-update/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about daily-update

How do I install daily-update in Claude Code?

Run npx skills add Ar9av/obsidian-wiki --skill daily-update -a claude-code, run the same command again, then use the skill from ~/.claude/skills/daily-update/SKILL.md.

What does daily-update do?

It checks source freshness, refreshes the wiki index and hot.md, writes cycle state, logs the result, and validates the artifacts with impl-validator.

Which daily scheduling methods does daily-update support?

Setup mode uses launchd on macOS, a user systemd timer on Linux, or cron in other environments. The scheduled launch is set for 9 AM.

Source text

SKILL.md · MIT
---
name: daily-update
description: >
  Run or configure the daily wiki maintenance cycle: check source freshness, refresh the index and hot.md, and manage its scheduled 9 AM launchd/systemd/cron reminder. Use for daily or morning wiki refresh or scheduler setup and verification.
---

# Daily Update — Wiki Maintenance Cycle

You run a lightweight maintenance pass over the wiki: check source freshness, refresh the index, update hot.md, and write the state file that the terminal notification reads.

## Before You Start

1. **Resolve config** — follow the Config Resolution Protocol in `llm-wiki/SKILL.md` (inline `@name` override → walk up CWD for `.env` → global config → prompt setup). This gives `OBSIDIAN_VAULT_PATH` and `OBSIDIAN_WIKI_REPO`.
2. **Derive vault-scoped state dir** — all runtime state is scoped to the resolved vault, not global:
   ```bash
   VAULT_ID=$(echo "$OBSIDIAN_VAULT_PATH" | md5sum 2>/dev/null | cut -c1-8 || md5 -q - <<< "$OBSIDIAN_VAULT_PATH" | cut -c1-8)
   STATE_DIR="$(obsidian_wiki_config_dir)/state/$VAULT_ID"
   mkdir -p "$STATE_DIR"
   ```
3. Read `$OBSIDIAN_VAULT_PATH/.manifest.json`.

## Modes

### Run Mode (default — triggered by cron or `/daily-update`)

Execute the maintenance cycle:

**Step 1: Source freshness check**

Compare each source in `.manifest.json` against its file's modification time. Classify as:
- **Fresh** — `mtime ≤ ingested_at`
- **Stale** — `mtime > ingested_at` (new content exists, not yet ingested)
- **Missing** — source file no longer exists

**Step 2: Index refresh**

```bash
obsidian-wiki memory index --vault "$OBSIDIAN_VAULT_PATH"
```

This reconciles `index.md` against the pages on disk under the memory lock — missing entries added, entries for deleted pages removed, the owner's own sections left untouched. Note `added`/`removed` from the output for the log line in Step 6. Do not enumerate pages with `find` and edit the index by hand.

**Step 3: hot.md update**

```bash
obsidian-wiki memory hot --vault "$OBSIDIAN_VAULT_PATH"
```

Recent Activity, Active Threads, and Flagged Contradictions are regenerated from the log, the todo index, and page frontmatter; `## Key Takeaways` carries across unchanged. If the takeaways are older than ~48h *and* the vault has changed materially since, refresh them: read the 10 most recently updated pages and pass a fresh ~500-word snapshot with `--takeaways -` on stdin. Otherwise leave them — a rebuild without new takeaways is cheap and correct.

If either command reports the vault is **unmigrated**, stop and tell the user to run `obsidian-wiki memory migrate` (preview) then `--apply`; do not fall back to hand-editing.

**Step 4: Write state**

Write to the vault-scoped `$STATE_DIR` derived in "Before You Start":

```bash
date +%s > "$STATE_DIR/.last_update"
echo "<stale_count>" > "$STATE_DIR/.pending_delta"
echo "$OBSIDIAN_VAULT_PATH" > "$STATE_DIR/.vault_path"
```

**Step 4a: Scheduled health check (wiki-lint)**

`LINT_SCHEDULE` (default `weekly`) controls how often this cycle also runs `wiki-lint`:

- `manual` — never auto-run; skip this step entirely.
- `daily` — run `wiki-lint` every cycle.
- `weekly` — run `wiki-lint` only if `$STATE_DIR/.last_lint` is missing or older than 7 days.

```bash
LINT_SCHEDULE="${LINT_SCHEDULE:-weekly}"
NOW=$(date +%s)
LAST_LINT=$(cat "$STATE_DIR/.last_lint" 2>/dev/null || echo 0)
```

If the schedule says to run, invoke the `wiki-lint` skill, then record the run:

```bash
date +%s > "$STATE_DIR/.last_lint"
```

Fold its summary (broken links, orphans, stale pages found) into Step 7's report as a `Health check:` line; omit the line entirely on a cycle where lint didn't run.

**Step 5: Spawn impl-validator**

After the cycle, spawn `impl-validator` as a subagent:

```
impl-validator check:
  goal: "Daily wiki maintenance — index reconciled, hot.md refreshed, state file written"
  artifacts:
    - $OBSIDIAN_VAULT_PATH/index.md
    - $OBSIDIAN_VAULT_PATH/hot.md
    - $STATE_DIR/.last_update
    - $STATE_DIR/.pending_delta
  checks:
    - Does .last_update contain a recent Unix timestamp (within the last 60 seconds)?
    - Does .pending_delta contain a non-negative integer?
    - Does hot.md have an updated: frontmatter field set to today?
    - Does index.md list at least as many pages as exist in the vault?
```

Apply any FAILs before logging.

**Step 6: Log**

Append to `$OBSIDIAN_VAULT_PATH/log.md`:
```
obsidian-wiki memory log DAILY-UPDATE fresh=<N> stale=<N> missing=<N> index_added=<N> hot_refreshed=<true|false> lint=<ran|skipped>
```

**Step 7: Report to user**

```
## Daily Wiki Update

- Sources: N fresh · N stale · N missing
- Index: N pages (N added, N removed)
- hot.md: refreshed / up to date
- Health check: N broken links, N orphans, N stale pages (omit this line if lint didn't run this cycle)

Stale sources (run to sync):
  /wiki-history-ingest claude   — N sessions since last ingest
  /wiki-history-ingest codex    — N sessions since last ingest
```

### Setup Mode (triggered by "set up the daily cron" or "install terminal notification")

Walk the user through first-time setup:

**Step 1: Verify script exists**

Check that `$OBSIDIAN_WIKI_REPO/scripts/daily-update.sh` exists and is executable. If not, point the user to it.

**Step 2: Install the scheduler** — pick by platform (`uname -s`).

macOS (`Darwin`) — launchd:

```bash
# Replace placeholder in plist
sed "s|OBSIDIAN_WIKI_REPO|$OBSIDIAN_WIKI_REPO|g" \
  "$OBSIDIAN_WIKI_REPO/scripts/com.obsidian-wiki.daily-update.plist" \
  > "$HOME/Library/LaunchAgents/com.obsidian-wiki.daily-update.plist"

# Load it
launchctl load "$HOME/Library/LaunchAgents/com.obsidian-wiki.daily-update.plist"
```

Linux with systemd (`systemctl --user` works) — a user timer:

```bash
UNIT_DIR="${XDG_CONFIG_HOME:-$HOME/.config}/systemd/user"
mkdir -p "$UNIT_DIR"
sed "s|OBSIDIAN_WIKI_REPO|$OBSIDIAN_WIKI_REPO|g" \
  "$OBSIDIAN_WIKI_REPO/scripts/obsidian-wiki-daily-update.service" \
  > "$UNIT_DIR/obsidian-wiki-daily-update.service"
cp "$OBSIDIAN_WIKI_REPO/scripts/obsidian-wiki-daily-update.timer" "$UNIT_DIR/"
systemctl --user daemon-reload
systemctl --user enable --now obsidian-wiki-daily-update.timer
```

On a headless server, user timers only run while the user is logged in unless lingering is on — suggest `sudo loginctl enable-linger "$USER"`.

Anything else (no systemd, containers, WSL without systemd) — crontab. Append this line via `crontab -e`, skipping it if an `obsidian-wiki` daily-update line is already there:

```cron
0 9 * * * /bin/bash "$OBSIDIAN_WIKI_REPO/scripts/daily-update.sh" >> /tmp/obsidian-wiki-daily.log 2>&1
```

Write the literal repo path in place of `$OBSIDIAN_WIKI_REPO` — cron does not load your shell env.

**Step 3: Install terminal notification (optional)**

Ask the user: "Do you want a terminal reminder when your wiki is stale? (y/n)" — skip this step if they say no, or if the environment is headless/VPS.

If yes, detect the user's shell and target the right rc file:

```bash
SHELL_NAME=$(basename "$SHELL")   # zsh, bash, fish, etc.
case "$SHELL_NAME" in
  zsh)  RC_FILE="$HOME/.zshrc" ;;
  bash) RC_FILE="$HOME/.bashrc" ;;
  *)    echo "Shell '$SHELL_NAME' not auto-detected. Add the source line manually to your shell rc file." ; return ;;
esac
```

Check if `wiki-notify.sh` is already sourced in that rc file. If not, append:

```bash
echo "" >> "$RC_FILE"
echo "# obsidian-wiki terminal notification" >> "$RC_FILE"
echo "source $OBSIDIAN_WIKI_REPO/scripts/wiki-notify.sh" >> "$RC_FILE"
```

For Fish shell, source syntax is different — provide the manual instruction:
```fish
# Add to ~/.config/fish/config.fish:
bass source $OBSIDIAN_WIKI_REPO/scripts/wiki-notify.sh
# (requires bass plugin, or copy the logic natively)
```

**Step 4: Run the script once**

```bash
bash "$OBSIDIAN_WIKI_REPO/scripts/daily-update.sh"
```

This initializes `$STATE_DIR/.last_update` so the terminal notification works immediately.

**Step 5: Confirm**

Tell the user:
- The scheduler runs daily at 9 AM (launchd and the systemd timer catch up on the next login/boot if missed; plain cron does not)
- `wiki-lint` health checks run on the `LINT_SCHEDULE` cadence (default `weekly`) as part of that cycle — set `LINT_SCHEDULE=daily` or `manual` in `.env` to change it
- Terminal notifications appear when the wiki is >20 hours stale
- State is stored in `<global config dir>/state/<vault-id>/` (XDG-style `~/.config/obsidian-wiki` by default, or the legacy `~/.obsidian-wiki` if that already exists) — supports multiple vaults independently
- They can run `/daily-update` anytime to force a sync
- Logs go to `/tmp/obsidian-wiki-daily.log` (launchd, cron) or `journalctl --user -u obsidian-wiki-daily-update` (systemd)

## QMD Refresh After Vault Writes

QMD is a search index, not the source of truth. If `$QMD_WIKI_COLLECTION` is empty or unset, skip this step. Run it only after this skill has written or rewritten vault markdown. If QMD refresh fails, do not roll back the vault changes; report the QMD status separately.

Use `$QMD_CLI` if set; otherwise use `qmd`.

```bash
${QMD_CLI:-qmd} update
```

If the output says vectors are needed or embeddings may be stale, run:

```bash
${QMD_CLI:-qmd} embed
```

Verify the collection with either:

```bash
${QMD_CLI:-qmd} ls "$QMD_WIKI_COLLECTION"
```

or, when a specific page path is known:

```bash
${QMD_CLI:-qmd} get "qmd://$QMD_WIKI_COLLECTION/<page>.md" -l 5
```

Record one of:
- `QMD refreshed: update + embed + verified`
- `QMD refreshed: update only + verified`
- `QMD skipped: QMD_WIKI_COLLECTION unset`
- `QMD skipped: qmd CLI unavailable`
- `QMD failed: <short error summary>`

© Ar9av · MIT · Ar9av/obsidian-wiki

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set38

codex-history-ingest Mines your Claude CLI session logs and turns them into Obsidian wiki pages. Useful once rollout files pile up and the decisions inside them are hard to find. CX Codex +1 2,600installs memory-bridge Browse an Obsidian wiki by which AI tool wrote each page, then diff two agents against each other. Handy when Claude, Codex and Copilot sessions pile up in separate silos. CX Codex +1 2,400installs wiki-agent Searches raw conversation history from a specific AI agent, distills matching sessions into an Obsidian vault, and returns an answer. Useful when recalling past decisions across different CLI tools. CX Codex +1 2,400installs hermes-history-ingest Distills Hermes memories and session history into an Obsidian wiki. Use it for regular imports or for mining durable knowledge from past work. CX Codex +1 2,400installs openclaw-history-ingest Imports durable knowledge from OpenClaw history into Obsidian. Use it to mine session logs, memory files, and notes without turning every session into a separate page. CX Codex +1 2,200installs impl-validator Independently checks whether finished work matches its stated goal and returns PASS, WARN or FAIL with a list of issues. CX Codex +1 2,200installs wiki-switch Switches named Obsidian vault profiles, lists them and scaffolds new ones. Handy once you keep more than one vault and need a different default. CX Codex +1 2,100installs wiki-digest Turns recent wiki activity into a readable report of what you learned, updated and connected. Useful for a regular review session. CX Codex +1 2,100installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor