Creator Β· Ar9av
Last updated Β· Sep 4, 2026
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 launchd cr
Creator Β· Ar9av
Last updated Β· Sep 4, 2026
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 launchd cr
Creator Β· Ar9av
Last updated Β· Sep 4, 2026
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 launchd cr
Creator Β· Ar9av
Last updated Β· Sep 4, 2026
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 launchd cr
Sandbox only
Install targets
Codex install prompt
Install the "daily-update" agent skill from https://github.com/Ar9av/obsidian-wiki/tree/main/.skills/daily-update. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: 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 launchd cron at 9 AM. 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?"). After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"ar9av-daily-update","task":"Install daily-update","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Deep research, source comparison, literature review, RAG, knowledge search, and reports.
Scenario
Research agents
I need my agent to research a topic, compare sources, and produce a concise report.
Agent fit
Claude Code + OpenAI Agents + CLI
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add Ar9av/obsidian-wiki --skill daily-update
Maintenance
fresh
3d since push
Risk
Needs review
Dependency or permission surface needs review
GitHub quality
3.3K
82/100 Quality Β· 77/100 Trust
Coverage tags
Review notes
Dependency or permission surface needs review Β· Permission surface may require sandboxing
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
StrongSolid option that is likely worth shortlisting for production workflows.
Trust
Sandbox onlyUseful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
Audit
Needs reviewA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Run only in a sandbox and compare close alternatives before using it for real work.
Stars
3.3K GitHub stars
Repo activity
3.3K stars, 330 forks
Maintenance
3d since push
License
MIT
Install
npx skills add Ar9av/obsidian-wiki --skill daily-update
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add Ar9av/obsidian-wiki --skill daily-updateDo not use when
Alternative
1.9K Stars
npx skills add yanliudesign/mono-color-skill --skill mono-color
Alternative
61.0K Stars
npx skills add mvanhorn/last30days-skill -g
Alternative
38.4K Stars
npx skills add Imbad0202/academic-research-skills
Alternative
28.0K Stars
npx skills add assafelovic/gpt-researcher
Agent safety v2
Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
Test manually in an isolated workspace and compare against safer alternatives.
high
Skill metadata references terminal, CLI, shell, subprocess, or command execution workflows.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
medium
Skill may read or write project files, documents, generated artifacts, or local workspace state.
high
Skill metadata references credentials, tokens, environment variables, or secret-bearing workflows.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20daily-update%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20daily-update%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/ar9av-daily-update/install
Agent should check
Copy prompt
Task: Use daily-update in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20daily-update%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/ar9av-daily-update/install
Install command: npx skills add Ar9av/obsidian-wiki --skill daily-update
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/ar9av-daily-update/install
LLM text format
/api/skills/ar9av-daily-update/install?format=text
Find alternatives
/api/skills/search?q=daily-update&limit=3
Agent prompt
Use daily-update for this task. Review https://www.openagentskill.com/api/skills/ar9av-daily-update/install, then install with: npx skills add Ar9av/obsidian-wiki --skill daily-updateRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/ar9av-daily-update
LLM text
/api/registry/manifest/ar9av-daily-update?format=text
Install alias
/api/registry/install/ar9av-daily-update
Recommend
/api/registry/recommend?task=Use%20daily-update%20in%20an%20agent%20workflow&limit=3
Agent fit
Research agents
Use-case tags
Platforms
Claude Code, OpenAI Agents
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Use this as a leading candidate, then validate the README and install path in your own agent stack.
Role in stack
Primary pick
Primary fit
Research agents
Trust label
Production-ready
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Useful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
GitHub adoption
PASS3.3K GitHub stars
Stars/forks activity
PASS3.3K stars, 330 forks; issue activity unavailable in current metadata
Recent maintenance
PASS3d since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Run only in a sandbox and compare close alternatives before using it for real work.
Quality profile
Solid option that is likely worth shortlisting for production workflows.
Workflow fit
Investigate faster
I need my agent to research a topic, compare sources, and produce a concise report.
Search private knowledge
I need my agent to build a RAG workflow over documents and retrieve reliable context.
Publish consistently
I need my agent to turn research and product updates into useful content drafts.
Workflow fit
Find, compare, and synthesize
A workflow for agents that gather sources, compare claims, summarize long material, and draft useful research briefs.
Ingest, retrieve, and cite
A workflow for document-heavy agents that ingest files, create searchable knowledge, retrieve relevant context, and answer with grounded sources.
Turn skills into distribution
A workflow for turning newly indexed skills into SEO briefs, social drafts, comparison pages, and reusable publishing workflows.
Alternative shortlist
Similar skills that may fit this task.
Generate original one-ink or controlled two-ink editorial images from any theme, sentence, article idea, object, or reference photo. Always use this skill when the user asks for εθ²ζ΅·ζ₯γεθ²ε°ε·γεθ²θ°θ§θ§γθθ²/η»Ώθ²εηε°ε·γrisographγη½ηΉη §ηγε€ε€ζε½δ»£ηΌθΎζηγzine poster, monochrome editorial poster, duotone print, or asks to use the mono-color style. It uses an adaptive white, gray, or pale-beige substrate, no more than two printing inks, active negative space, terse human language, and strong serif/grotesk/mono typography without making retro styling the default or copying a source composition, wording, logo, or artwork. Produce both the final generation prompt and the generated raster image unless the user explicitly asks for prompt only.
Research the last 30 days across Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesize a grounded brief for an AI agent.
Academic Research Skills for Claude Code: research β write β review β revise β finalize
Run autonomous deep research over web and local sources
--- name: daily-update description: > 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 launchd cron at 9 AM. 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?"). ---
# 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**
Read `$OBSIDIAN_VAULT_PATH/index.md`. If any pages in the vault are missing from the index (or vice versa), update the index. Use `find $OBSIDIAN_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":
```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`: ``` - [TIMESTAMP] 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 launchd plist**
```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" ```
**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 cron runs daily at 9 AM (or on next login if missed) - `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`
## 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>`
Source provenance
Decision snapshot
3,339 GitHub stars
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for daily-update, ready for a manual X post.
daily-update: Run the daily wiki maintenance cycle: check all source freshness, update the index, and regen... 3.3K stars https://www.openagentskill.com/skills/ar9av-daily-update?ref=x
Listing + install path for daily-update: https://www.openagentskill.com/skills/ar9av-daily-update?ref=x Install: npx skills add Ar9av/obsidian-wiki --skill daily-update
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to Ar9av but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/ar9av-daily-update?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/ar9av-daily-update?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/ar9av-daily-update/audit)
[](https://www.openagentskill.com/skills/ar9av-daily-update?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)Ar9av
@ar9av
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Sandbox only
mono-color
Generate original one-ink or controlled two-ink editorial images from any theme, sentence, article idea, object, or reference photo. Always use this skill when the user asks for εθ²ζ΅·ζ₯γεθ²ε°ε·γεθ²θ°θ§θ§γθθ²/η»Ώθ²εηε°ε·γrisographγη½ηΉη §ηγε€ε€ζε½δ»£ηΌθΎζηγzine poster, monochrome editorial poster, duotone print, or asks to use the mono-color style. It uses an adaptive white, gray, or pale-beige substrate, no more than two printing inks, active negative space, terse human language, and strong serif/grotesk/mono typography without making retro styling the default or copying a source composition, wording, logo, or artwork. Produce both the final generation prompt and the generated raster image unless the user explicitly asks for prompt only.
1.9K StarsLast30days Skill
Research the last 30 days across Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesize a grounded brief for an AI agent.
61.0K StarsAcademic Research Skills
Academic Research Skills for Claude Code: research β write β review β revise β finalize
38.4K StarsGPT Researcher
Run autonomous deep research over web and local sources
28.0K StarsSandbox only
Install targets
Codex install prompt
Install the "daily-update" agent skill from https://github.com/Ar9av/obsidian-wiki/tree/main/.skills/daily-update. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: 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 launchd cron at 9 AM. 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?"). After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"ar9av-daily-update","task":"Install daily-update","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Deep research, source comparison, literature review, RAG, knowledge search, and reports.
Scenario
Research agents
I need my agent to research a topic, compare sources, and produce a concise report.
Agent fit
Claude Code + OpenAI Agents + CLI
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add Ar9av/obsidian-wiki --skill daily-update
Maintenance
fresh
3d since push
Risk
Needs review
Dependency or permission surface needs review
GitHub quality
3.3K
82/100 Quality Β· 77/100 Trust
Coverage tags
Review notes
Dependency or permission surface needs review Β· Permission surface may require sandboxing
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
StrongSolid option that is likely worth shortlisting for production workflows.
Trust
Sandbox onlyUseful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
Audit
Needs reviewA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Run only in a sandbox and compare close alternatives before using it for real work.
Stars
3.3K GitHub stars
Repo activity
3.3K stars, 330 forks
Maintenance
3d since push
License
MIT
Install
npx skills add Ar9av/obsidian-wiki --skill daily-update
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add Ar9av/obsidian-wiki --skill daily-updateDo not use when
Alternative
1.9K Stars
npx skills add yanliudesign/mono-color-skill --skill mono-color
Alternative
61.0K Stars
npx skills add mvanhorn/last30days-skill -g
Alternative
38.4K Stars
npx skills add Imbad0202/academic-research-skills
Alternative
28.0K Stars
npx skills add assafelovic/gpt-researcher
Agent safety v2
Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
Test manually in an isolated workspace and compare against safer alternatives.
high
Skill metadata references terminal, CLI, shell, subprocess, or command execution workflows.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
medium
Skill may read or write project files, documents, generated artifacts, or local workspace state.
high
Skill metadata references credentials, tokens, environment variables, or secret-bearing workflows.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20daily-update%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20daily-update%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/ar9av-daily-update/install
Agent should check
Copy prompt
Task: Use daily-update in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20daily-update%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/ar9av-daily-update/install
Install command: npx skills add Ar9av/obsidian-wiki --skill daily-update
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/ar9av-daily-update/install
LLM text format
/api/skills/ar9av-daily-update/install?format=text
Find alternatives
/api/skills/search?q=daily-update&limit=3
Agent prompt
Use daily-update for this task. Review https://www.openagentskill.com/api/skills/ar9av-daily-update/install, then install with: npx skills add Ar9av/obsidian-wiki --skill daily-updateRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/ar9av-daily-update
LLM text
/api/registry/manifest/ar9av-daily-update?format=text
Install alias
/api/registry/install/ar9av-daily-update
Recommend
/api/registry/recommend?task=Use%20daily-update%20in%20an%20agent%20workflow&limit=3
Agent fit
Research agents
Use-case tags
Platforms
Claude Code, OpenAI Agents
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Use this as a leading candidate, then validate the README and install path in your own agent stack.
Role in stack
Primary pick
Primary fit
Research agents
Trust label
Production-ready
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Useful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
GitHub adoption
PASS3.3K GitHub stars
Stars/forks activity
PASS3.3K stars, 330 forks; issue activity unavailable in current metadata
Recent maintenance
PASS3d since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Run only in a sandbox and compare close alternatives before using it for real work.
Quality profile
Solid option that is likely worth shortlisting for production workflows.
Workflow fit
Investigate faster
I need my agent to research a topic, compare sources, and produce a concise report.
Search private knowledge
I need my agent to build a RAG workflow over documents and retrieve reliable context.
Publish consistently
I need my agent to turn research and product updates into useful content drafts.
Workflow fit
Find, compare, and synthesize
A workflow for agents that gather sources, compare claims, summarize long material, and draft useful research briefs.
Ingest, retrieve, and cite
A workflow for document-heavy agents that ingest files, create searchable knowledge, retrieve relevant context, and answer with grounded sources.
Turn skills into distribution
A workflow for turning newly indexed skills into SEO briefs, social drafts, comparison pages, and reusable publishing workflows.
Alternative shortlist
Similar skills that may fit this task.
Generate original one-ink or controlled two-ink editorial images from any theme, sentence, article idea, object, or reference photo. Always use this skill when the user asks for εθ²ζ΅·ζ₯γεθ²ε°ε·γεθ²θ°θ§θ§γθθ²/η»Ώθ²εηε°ε·γrisographγη½ηΉη §ηγε€ε€ζε½δ»£ηΌθΎζηγzine poster, monochrome editorial poster, duotone print, or asks to use the mono-color style. It uses an adaptive white, gray, or pale-beige substrate, no more than two printing inks, active negative space, terse human language, and strong serif/grotesk/mono typography without making retro styling the default or copying a source composition, wording, logo, or artwork. Produce both the final generation prompt and the generated raster image unless the user explicitly asks for prompt only.
Research the last 30 days across Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesize a grounded brief for an AI agent.
Academic Research Skills for Claude Code: research β write β review β revise β finalize
Run autonomous deep research over web and local sources
--- name: daily-update description: > 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 launchd cron at 9 AM. 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?"). ---
# 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**
Read `$OBSIDIAN_VAULT_PATH/index.md`. If any pages in the vault are missing from the index (or vice versa), update the index. Use `find $OBSIDIAN_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":
```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`: ``` - [TIMESTAMP] 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 launchd plist**
```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" ```
**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 cron runs daily at 9 AM (or on next login if missed) - `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`
## 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>`
Source provenance
Decision snapshot
3,339 GitHub stars
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for daily-update, ready for a manual X post.
daily-update: Run the daily wiki maintenance cycle: check all source freshness, update the index, and regen... 3.3K stars https://www.openagentskill.com/skills/ar9av-daily-update?ref=x
Listing + install path for daily-update: https://www.openagentskill.com/skills/ar9av-daily-update?ref=x Install: npx skills add Ar9av/obsidian-wiki --skill daily-update
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to Ar9av but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/ar9av-daily-update?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/ar9av-daily-update?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/ar9av-daily-update/audit)
[](https://www.openagentskill.com/skills/ar9av-daily-update?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)Ar9av
@ar9av
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Sandbox only
mono-color
Generate original one-ink or controlled two-ink editorial images from any theme, sentence, article idea, object, or reference photo. Always use this skill when the user asks for εθ²ζ΅·ζ₯γεθ²ε°ε·γεθ²θ°θ§θ§γθθ²/η»Ώθ²εηε°ε·γrisographγη½ηΉη §ηγε€ε€ζε½δ»£ηΌθΎζηγzine poster, monochrome editorial poster, duotone print, or asks to use the mono-color style. It uses an adaptive white, gray, or pale-beige substrate, no more than two printing inks, active negative space, terse human language, and strong serif/grotesk/mono typography without making retro styling the default or copying a source composition, wording, logo, or artwork. Produce both the final generation prompt and the generated raster image unless the user explicitly asks for prompt only.
1.9K StarsLast30days Skill
Research the last 30 days across Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesize a grounded brief for an AI agent.
61.0K StarsAcademic Research Skills
Academic Research Skills for Claude Code: research β write β review β revise β finalize
38.4K StarsGPT Researcher
Run autonomous deep research over web and local sources
28.0K StarsSandbox only
Install targets
Codex install prompt
Install the "daily-update" agent skill from https://github.com/Ar9av/obsidian-wiki/tree/main/.skills/daily-update. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: 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 launchd cron at 9 AM. 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?"). After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"ar9av-daily-update","task":"Install daily-update","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Deep research, source comparison, literature review, RAG, knowledge search, and reports.
Scenario
Research agents
I need my agent to research a topic, compare sources, and produce a concise report.
Agent fit
Claude Code + OpenAI Agents + CLI
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add Ar9av/obsidian-wiki --skill daily-update
Maintenance
fresh
3d since push
Risk
Needs review
Dependency or permission surface needs review
GitHub quality
3.3K
82/100 Quality Β· 77/100 Trust
Coverage tags
Review notes
Dependency or permission surface needs review Β· Permission surface may require sandboxing
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
StrongSolid option that is likely worth shortlisting for production workflows.
Trust
Sandbox onlyUseful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
Audit
Needs reviewA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Run only in a sandbox and compare close alternatives before using it for real work.
Stars
3.3K GitHub stars
Repo activity
3.3K stars, 330 forks
Maintenance
3d since push
License
MIT
Install
npx skills add Ar9av/obsidian-wiki --skill daily-update
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add Ar9av/obsidian-wiki --skill daily-updateDo not use when
Alternative
1.9K Stars
npx skills add yanliudesign/mono-color-skill --skill mono-color
Alternative
61.0K Stars
npx skills add mvanhorn/last30days-skill -g
Alternative
38.4K Stars
npx skills add Imbad0202/academic-research-skills
Alternative
28.0K Stars
npx skills add assafelovic/gpt-researcher
Agent safety v2
Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
Test manually in an isolated workspace and compare against safer alternatives.
high
Skill metadata references terminal, CLI, shell, subprocess, or command execution workflows.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
medium
Skill may read or write project files, documents, generated artifacts, or local workspace state.
high
Skill metadata references credentials, tokens, environment variables, or secret-bearing workflows.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20daily-update%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20daily-update%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/ar9av-daily-update/install
Agent should check
Copy prompt
Task: Use daily-update in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20daily-update%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/ar9av-daily-update/install
Install command: npx skills add Ar9av/obsidian-wiki --skill daily-update
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/ar9av-daily-update/install
LLM text format
/api/skills/ar9av-daily-update/install?format=text
Find alternatives
/api/skills/search?q=daily-update&limit=3
Agent prompt
Use daily-update for this task. Review https://www.openagentskill.com/api/skills/ar9av-daily-update/install, then install with: npx skills add Ar9av/obsidian-wiki --skill daily-updateRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/ar9av-daily-update
LLM text
/api/registry/manifest/ar9av-daily-update?format=text
Install alias
/api/registry/install/ar9av-daily-update
Recommend
/api/registry/recommend?task=Use%20daily-update%20in%20an%20agent%20workflow&limit=3
Agent fit
Research agents
Use-case tags
Platforms
Claude Code, OpenAI Agents
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Use this as a leading candidate, then validate the README and install path in your own agent stack.
Role in stack
Primary pick
Primary fit
Research agents
Trust label
Production-ready
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Useful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
GitHub adoption
PASS3.3K GitHub stars
Stars/forks activity
PASS3.3K stars, 330 forks; issue activity unavailable in current metadata
Recent maintenance
PASS3d since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Run only in a sandbox and compare close alternatives before using it for real work.
Quality profile
Solid option that is likely worth shortlisting for production workflows.
Workflow fit
Investigate faster
I need my agent to research a topic, compare sources, and produce a concise report.
Search private knowledge
I need my agent to build a RAG workflow over documents and retrieve reliable context.
Publish consistently
I need my agent to turn research and product updates into useful content drafts.
Workflow fit
Find, compare, and synthesize
A workflow for agents that gather sources, compare claims, summarize long material, and draft useful research briefs.
Ingest, retrieve, and cite
A workflow for document-heavy agents that ingest files, create searchable knowledge, retrieve relevant context, and answer with grounded sources.
Turn skills into distribution
A workflow for turning newly indexed skills into SEO briefs, social drafts, comparison pages, and reusable publishing workflows.
Alternative shortlist
Similar skills that may fit this task.
Generate original one-ink or controlled two-ink editorial images from any theme, sentence, article idea, object, or reference photo. Always use this skill when the user asks for εθ²ζ΅·ζ₯γεθ²ε°ε·γεθ²θ°θ§θ§γθθ²/η»Ώθ²εηε°ε·γrisographγη½ηΉη §ηγε€ε€ζε½δ»£ηΌθΎζηγzine poster, monochrome editorial poster, duotone print, or asks to use the mono-color style. It uses an adaptive white, gray, or pale-beige substrate, no more than two printing inks, active negative space, terse human language, and strong serif/grotesk/mono typography without making retro styling the default or copying a source composition, wording, logo, or artwork. Produce both the final generation prompt and the generated raster image unless the user explicitly asks for prompt only.
Research the last 30 days across Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesize a grounded brief for an AI agent.
Academic Research Skills for Claude Code: research β write β review β revise β finalize
Run autonomous deep research over web and local sources
--- name: daily-update description: > 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 launchd cron at 9 AM. 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?"). ---
# 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**
Read `$OBSIDIAN_VAULT_PATH/index.md`. If any pages in the vault are missing from the index (or vice versa), update the index. Use `find $OBSIDIAN_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":
```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`: ``` - [TIMESTAMP] 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 launchd plist**
```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" ```
**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 cron runs daily at 9 AM (or on next login if missed) - `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`
## 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>`
Source provenance
Decision snapshot
3,339 GitHub stars
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for daily-update, ready for a manual X post.
daily-update: Run the daily wiki maintenance cycle: check all source freshness, update the index, and regen... 3.3K stars https://www.openagentskill.com/skills/ar9av-daily-update?ref=x
Listing + install path for daily-update: https://www.openagentskill.com/skills/ar9av-daily-update?ref=x Install: npx skills add Ar9av/obsidian-wiki --skill daily-update
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to Ar9av but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/ar9av-daily-update?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/ar9av-daily-update?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/ar9av-daily-update/audit)
[](https://www.openagentskill.com/skills/ar9av-daily-update?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)Ar9av
@ar9av
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Sandbox only
mono-color
Generate original one-ink or controlled two-ink editorial images from any theme, sentence, article idea, object, or reference photo. Always use this skill when the user asks for εθ²ζ΅·ζ₯γεθ²ε°ε·γεθ²θ°θ§θ§γθθ²/η»Ώθ²εηε°ε·γrisographγη½ηΉη §ηγε€ε€ζε½δ»£ηΌθΎζηγzine poster, monochrome editorial poster, duotone print, or asks to use the mono-color style. It uses an adaptive white, gray, or pale-beige substrate, no more than two printing inks, active negative space, terse human language, and strong serif/grotesk/mono typography without making retro styling the default or copying a source composition, wording, logo, or artwork. Produce both the final generation prompt and the generated raster image unless the user explicitly asks for prompt only.
1.9K StarsLast30days Skill
Research the last 30 days across Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesize a grounded brief for an AI agent.
61.0K StarsAcademic Research Skills
Academic Research Skills for Claude Code: research β write β review β revise β finalize
38.4K StarsGPT Researcher
Run autonomous deep research over web and local sources
28.0K StarsSandbox only
Install targets
Codex install prompt
Install the "daily-update" agent skill from https://github.com/Ar9av/obsidian-wiki/tree/main/.skills/daily-update. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: 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 launchd cron at 9 AM. 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?"). After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"ar9av-daily-update","task":"Install daily-update","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Deep research, source comparison, literature review, RAG, knowledge search, and reports.
Scenario
Research agents
I need my agent to research a topic, compare sources, and produce a concise report.
Agent fit
Claude Code + OpenAI Agents + CLI
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add Ar9av/obsidian-wiki --skill daily-update
Maintenance
fresh
3d since push
Risk
Needs review
Dependency or permission surface needs review
GitHub quality
3.3K
82/100 Quality Β· 77/100 Trust
Coverage tags
Review notes
Dependency or permission surface needs review Β· Permission surface may require sandboxing
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
StrongSolid option that is likely worth shortlisting for production workflows.
Trust
Sandbox onlyUseful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
Audit
Needs reviewA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Run only in a sandbox and compare close alternatives before using it for real work.
Stars
3.3K GitHub stars
Repo activity
3.3K stars, 330 forks
Maintenance
3d since push
License
MIT
Install
npx skills add Ar9av/obsidian-wiki --skill daily-update
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add Ar9av/obsidian-wiki --skill daily-updateDo not use when
Alternative
1.9K Stars
npx skills add yanliudesign/mono-color-skill --skill mono-color
Alternative
61.0K Stars
npx skills add mvanhorn/last30days-skill -g
Alternative
38.4K Stars
npx skills add Imbad0202/academic-research-skills
Alternative
28.0K Stars
npx skills add assafelovic/gpt-researcher
Agent safety v2
Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
Test manually in an isolated workspace and compare against safer alternatives.
high
Skill metadata references terminal, CLI, shell, subprocess, or command execution workflows.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
medium
Skill may read or write project files, documents, generated artifacts, or local workspace state.
high
Skill metadata references credentials, tokens, environment variables, or secret-bearing workflows.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20daily-update%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20daily-update%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/ar9av-daily-update/install
Agent should check
Copy prompt
Task: Use daily-update in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20daily-update%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/ar9av-daily-update/install
Install command: npx skills add Ar9av/obsidian-wiki --skill daily-update
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/ar9av-daily-update/install
LLM text format
/api/skills/ar9av-daily-update/install?format=text
Find alternatives
/api/skills/search?q=daily-update&limit=3
Agent prompt
Use daily-update for this task. Review https://www.openagentskill.com/api/skills/ar9av-daily-update/install, then install with: npx skills add Ar9av/obsidian-wiki --skill daily-updateRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/ar9av-daily-update
LLM text
/api/registry/manifest/ar9av-daily-update?format=text
Install alias
/api/registry/install/ar9av-daily-update
Recommend
/api/registry/recommend?task=Use%20daily-update%20in%20an%20agent%20workflow&limit=3
Agent fit
Research agents
Use-case tags
Platforms
Claude Code, OpenAI Agents
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Use this as a leading candidate, then validate the README and install path in your own agent stack.
Role in stack
Primary pick
Primary fit
Research agents
Trust label
Production-ready
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Useful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
GitHub adoption
PASS3.3K GitHub stars
Stars/forks activity
PASS3.3K stars, 330 forks; issue activity unavailable in current metadata
Recent maintenance
PASS3d since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Run only in a sandbox and compare close alternatives before using it for real work.
Quality profile
Solid option that is likely worth shortlisting for production workflows.
Workflow fit
Investigate faster
I need my agent to research a topic, compare sources, and produce a concise report.
Search private knowledge
I need my agent to build a RAG workflow over documents and retrieve reliable context.
Publish consistently
I need my agent to turn research and product updates into useful content drafts.
Workflow fit
Find, compare, and synthesize
A workflow for agents that gather sources, compare claims, summarize long material, and draft useful research briefs.
Ingest, retrieve, and cite
A workflow for document-heavy agents that ingest files, create searchable knowledge, retrieve relevant context, and answer with grounded sources.
Turn skills into distribution
A workflow for turning newly indexed skills into SEO briefs, social drafts, comparison pages, and reusable publishing workflows.
Alternative shortlist
Similar skills that may fit this task.
Generate original one-ink or controlled two-ink editorial images from any theme, sentence, article idea, object, or reference photo. Always use this skill when the user asks for εθ²ζ΅·ζ₯γεθ²ε°ε·γεθ²θ°θ§θ§γθθ²/η»Ώθ²εηε°ε·γrisographγη½ηΉη §ηγε€ε€ζε½δ»£ηΌθΎζηγzine poster, monochrome editorial poster, duotone print, or asks to use the mono-color style. It uses an adaptive white, gray, or pale-beige substrate, no more than two printing inks, active negative space, terse human language, and strong serif/grotesk/mono typography without making retro styling the default or copying a source composition, wording, logo, or artwork. Produce both the final generation prompt and the generated raster image unless the user explicitly asks for prompt only.
Research the last 30 days across Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesize a grounded brief for an AI agent.
Academic Research Skills for Claude Code: research β write β review β revise β finalize
Run autonomous deep research over web and local sources
--- name: daily-update description: > 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 launchd cron at 9 AM. 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?"). ---
# 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**
Read `$OBSIDIAN_VAULT_PATH/index.md`. If any pages in the vault are missing from the index (or vice versa), update the index. Use `find $OBSIDIAN_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":
```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`: ``` - [TIMESTAMP] 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 launchd plist**
```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" ```
**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 cron runs daily at 9 AM (or on next login if missed) - `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`
## 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>`
Source provenance
Decision snapshot
3,339 GitHub stars
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for daily-update, ready for a manual X post.
daily-update: Run the daily wiki maintenance cycle: check all source freshness, update the index, and regen... 3.3K stars https://www.openagentskill.com/skills/ar9av-daily-update?ref=x
Listing + install path for daily-update: https://www.openagentskill.com/skills/ar9av-daily-update?ref=x Install: npx skills add Ar9av/obsidian-wiki --skill daily-update
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to Ar9av but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/ar9av-daily-update?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/ar9av-daily-update?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/ar9av-daily-update/audit)
[](https://www.openagentskill.com/skills/ar9av-daily-update?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)Ar9av
@ar9av
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Sandbox only
mono-color
Generate original one-ink or controlled two-ink editorial images from any theme, sentence, article idea, object, or reference photo. Always use this skill when the user asks for εθ²ζ΅·ζ₯γεθ²ε°ε·γεθ²θ°θ§θ§γθθ²/η»Ώθ²εηε°ε·γrisographγη½ηΉη §ηγε€ε€ζε½δ»£ηΌθΎζηγzine poster, monochrome editorial poster, duotone print, or asks to use the mono-color style. It uses an adaptive white, gray, or pale-beige substrate, no more than two printing inks, active negative space, terse human language, and strong serif/grotesk/mono typography without making retro styling the default or copying a source composition, wording, logo, or artwork. Produce both the final generation prompt and the generated raster image unless the user explicitly asks for prompt only.
1.9K StarsLast30days Skill
Research the last 30 days across Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesize a grounded brief for an AI agent.
61.0K StarsAcademic Research Skills
Academic Research Skills for Claude Code: research β write β review β revise β finalize
38.4K StarsGPT Researcher
Run autonomous deep research over web and local sources
28.0K StarsPermission surface
secrets or environment access, shell or command execution
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness
Permission surface
secrets or environment access, shell or command execution
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness
Permission surface
secrets or environment access, shell or command execution
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness
Permission surface
secrets or environment access, shell or command execution
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness