wiki-status

Report page counts, category breakdowns, and structural insights for Obsidian vaults.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/HelloWorldSungin/ark-skills --skill wiki-status-helloworldsungin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wiki-status
Source: https://github.com/HelloWorldSungin/ark-skills/tree/main/skills/wiki-status
Command: npx skills add https://github.com/HelloWorldSungin/ark-skills --skill wiki-status-helloworldsungin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Vaults with many pages and dispersed metadata lose visibility into overall health, structure, and progress. This Skill provides a concise, at-a-glance health report for Obsidian vaults.

Core Features & Use Cases

  • Report vault statistics: total pages, per-category counts, and generation timestamp.
  • Validate vault freshness: compare index coverage with on-disk files and surface discrepancies.
  • Generate actionable insights: identify central pages, orphan pages, and tag/summary coverage to guide curation.

Quick Start

Run the wiki-status workflow to generate a live vault health report from the CLAUDE.md and index.md.

Frequently Asked Questions about wiki-status

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check my Obsidian vault health and page count metrics?

Obsidian vault health is assessed by parsing index.md for summaries and counting on-disk MD files to report total page counts, category breakdowns, and generation timestamps.

How do I find orphan pages and structural gaps in an Obsidian vault?

Orphan pages and structural gaps are identified by analyzing the vault index and on-disk files to surface central pages, orphan pages, and tag coverage, generating actionable insights to guide curation.

Does this vault metrics reporting tool require specific files to work?

Vault metrics reporting requires a CLAUDE.md file to locate the vault path and an index.md file to parse summary and generated fields for calculating coverage and freshness.

What is the best way to validate Obsidian vault freshness and index coverage?

The best way to validate vault freshness is to compare index coverage with on-disk MD files, surfacing discrepancies between the index.md summary and the actual files present in the vault.

Why does my Obsidian vault index show different page counts than the actual files?

Your vault index shows different page counts because of discrepancies between index coverage and on-disk files, which this Skill detects by parsing index.md and counting the actual MD files to surface gaps.