beeweave: Skill for Claude Code

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 beeweave-core/SKILL.md (inline @name override → walk up CWD for .env → ~/.beeweave/config → prompt setup). This gives BEEWEAVE_VAULT_PATH and BEEWEAVE_REPO.
2. Derive vault-scoped state dir — all runtime state is scoped to the resolved vault, not global:

   VAULT_ID=$(echo "$BEEWEAVE_VAULT_PATH" | md5sum 2>/dev/null | cut -c1-8 || md5 -q - <<< "$BEEWEAVE_VAULT_PATH" | cut -c1-8)
   STATE_DIR="$HOME/.beeweave/state/$VAULT_ID"
   mkdir -p "$STATE_DIR"
   

3. Read $BEEWEAVE_VAULT_PATH/.manifest.json.

Modes

Run Mode (default — triggered by cron or /beeweave-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

Read $BEEWEAVE_VAULT_PATH/index.md. If any pages in the vault are missing from the index (or vice versa), update the index. Use find $BEEWEAVE_VAULT_PATH -name "*.md" -not -path "*/_*" to enumerate vault pages, then reconcile against the index.

Step 3: hot.md update

Read hot.md. If it's >48h old based on its updated: frontmatter, regenerate it: read the 10 most recently modified wiki pages and write a fresh ~500-word semantic snapshot of what the wiki covers. This keeps the next session's context warm without a full vault crawl.

Step 4: Write state

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

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