wiki-status

Compare Obsidian vault sources against the manifest to report ingest deltas.

4|Updated May 9, 2026
One-click install
npx skills add https://github.com/itsmarsss/memento --skill wiki-status-itsmarsss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wiki-status
Source: https://github.com/itsmarsss/memento/tree/main/obsidian-wiki/.skills/wiki-status
Command: npx skills add https://github.com/itsmarsss/memento --skill wiki-status-itsmarsss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates uncertainty about what your Obsidian wiki has ingested, what changed since the last ingest, and what remains pending, so you can choose the right next action with confidence.

Core Features & Use Cases

  • Ingest delta reporting: Compares on-disk sources (documents, Claude project history, Codex sessions) against the vault’s .manifest.json ledger to classify New, Modified, Touched, Unchanged, and Deleted items.
  • Vault health visibility: Summarizes page visibility distribution (public/internal/pii) by scanning frontmatter tags across the vault.
  • Structure intelligence (insights mode): Builds a wikilink graph to surface hubs, bridges, cohesion/fractured clusters, surprising cross-category connections, and orphan-adjacent pages, then writes an _insights.md report at the vault root.
  • Pipeline-aware fallback: When AGENTS.md indicates an external ingest pipeline, replaces manifest deltas with pipeline-fed counts and warnings for failed raw artifacts.

Quick Start

Ask your assistant to run the wiki-status skill to report what has been ingested and what is left to process in your current Obsidian vault.

Frequently Asked Questions about wiki-status

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

FAQPage Schema
How do I check what changed in my Obsidian vault since the last ingest?

To check what changed since the last ingest, audit your Obsidian vault health by comparing on-disk sources against the vault's .manifest.json ledger. This classifies items as New, Modified, Touched, Unchanged, or Deleted to show the exact delta.

What is the best way to find missing updates in an Obsidian knowledge base?

The best way to find missing updates is to compute the ingest delta by scanning source documents and manifest entries. This identifies pending and modified files, clarifying whether you should append new data or rebuild the vault.

How does a wikilink graph help analyze Obsidian vault structure?

A wikilink graph analyzes Obsidian vault structure by surfacing hubs, bridges, and cohesion or fractured clusters. It identifies surprising cross-category connections and orphan-adjacent pages, generating an _insights.md report at the vault root.

Do I need an external ingest pipeline to track Obsidian vault health?

You do not need an external ingest pipeline to track Obsidian vault health. The system uses a pipeline-aware fallback that reads AGENTS.md, replacing manifest deltas with pipeline-fed counts and warnings only if an external pipeline exists.

Can I see page visibility distribution for my Obsidian knowledge base?

You can see page visibility distribution by scanning frontmatter tags across the Obsidian vault. This summarizes how many pages are marked as public, internal, or pii, providing a clear view of your knowledge base health.

When should I rebuild my Obsidian vault instead of appending new content?

You should rebuild your Obsidian vault instead of appending when the manifest delta reveals significant structural changes or widespread modifications. The delta report helps you decide the right next action by showing exactly what is left to ingest.