Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
cyanotex avatar

Vault Status

  • 1 installs
  • Updated July 11, 2026
  • cyanotex/claudian

Helps with ai & agent building tasks.

About

vault-status is a Claude Code skill for ai & agent building. It helps developers move faster with AI-assisted coding.

  • vault-status
  • AI & Agent Building
  • AI-coding skill

Vault Status by the numbers

  • 1 all-time installs (skills.sh)
  • Ranked #14,102 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
  • Data as of Jul 12, 2026 (Skillselion catalog sync)
npx skills add https://github.com/cyanotex/claudian --skill vault-status

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs1
Last updatedJuly 11, 2026
Repositorycyanotex/claudian

What it does

Helps with ai & agent building tasks.

Files

SKILL.mdMarkdownGitHub ↗

vault-status

Report the health of the Claudian Obsidian vault as a concise dashboard.

When to Use

  • User asks "how's the vault?" or "vault status"
  • Start of a session to surface maintenance needs
  • After a batch of vault-write calls to check for orphans
  • Before vault-link to find what needs linking

Fresh Vault Detection

If all notes were created today, knowledge/ and ideas/ are empty, and only project stubs exist — report it as fresh instead of flagging false issues:

VAULT STATUS — {date}

Vault just initialized. No knowledge notes yet.
Projects registered: {list}

Get started:
- Write freeform ideas in {vault}/ideas/ and run /vault-extract
- Use /vault-write when you discover durable knowledge
- The SessionStart hook will surface relevant notes as the vault grows

Skip the full dashboard for fresh vaults.

Checks

Run all checks, then present results as a single dashboard.

Orphan notes — no inbound wikilinks from any other vault note. Report count + top 5 by last-updated.

Stale notesupdated frontmatter more than 30 days old AND linked to by at least one other note. Report count + up to 5 with last-updated date.

Unprocessed ideas — files in {vault}/ideas/ without processed: true. Report count + titles and creation dates.

Tag distribution — count occurrences per tag across all tags: frontmatter blocks. Report top 10 tags and any used only once.

Project coverage — count files per {vault}/projects/{project-name}/, check for index.md. Report as table.

Missing frontmatter — notes missing any of: title, type, project, tags, created, updated. Report count + up to 5 with missing fields listed.

Output Format

VAULT STATUS — {date}

Orphan notes:        {N}  [list top 5 if N > 0]
Stale notes (>30d):  {N}  [list top 5 if N > 0]
Unprocessed ideas:   {N}  [list all if N > 0]
Missing frontmatter: {N}  [list top 5 if N > 0]

Tag coverage ({total} tags):
  Most used: <tag> ({N}), <tag> ({N}), <tag> ({N})
  Single-use: <tag>, <tag>

Project coverage:
  <project>: {N} notes  [index: yes/no]

If everything is healthy: "Vault looks healthy — no orphans, no stale notes, all ideas processed."

Recommended Actions

  • Orphans → run vault-link
  • Unprocessed ideas → run vault-extract
  • Missing frontmatter → offer to fix with vault-write (update mode)
  • Stale notes → offer to review and update them

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.