Skip to content
SkillModel-led1,944 tokens in use

wiki-rebuild

Archives an Obsidian wiki to a timestamped snapshot, clears it for a full re-ingest, or restores an earlier archive, always confirming before a destructive step.

3,792 stars on the repository MIT LicenseAr9av/obsidian-wiki · skills/wiki-rebuild
pip install obsidian-wiki
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing wiki-rebuild costs

42tokens idle
1,944tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

shelldetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Excellent
  • Frontmatter8/15
  • Structure25/25
  • Examples12/15
  • Output15/15
  • Size15/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent
  • Runs shell commands−5

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 173

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Excellent
  • Development activity100
  • Maintenance100
  • Community60
  • Maturity28
  • Momentum40

wiki-rebuild is the recovery tool for a wiki that needs a full restart. It has three modes: archive only, archive then clear for a rebuild, and restore from a previous archive.

Each archive is a timestamped folder with a copy of the category pages, index, log, manifest and an archive-meta file. The skill always archives first, asks before clearing the live wiki, and leaves the Obsidian settings folder alone.

What You Get

  • A timestamped archive folder with pages, index, log, manifest and metadata
  • A cleared vault ready for a selective full re-ingest
  • A restore from any earlier archive after a safety snapshot
  • Log entries for each archive, rebuild or restore
  • A final report that includes the state of the QMD search index

Common Use Cases

  • Taking a snapshot of a wiki before a risky bulk operation
  • Starting a wiki again from its sources after the structure has drifted
  • Rolling a vault back to an earlier archive

What Makes It Unique

It treats archiving as a rule with no exceptions and makes the user choose what to re-ingest and in what order, since some sources may no longer matter. Restore takes a pre-restore snapshot first, so the restore itself can be undone. It also keeps the search index in step, because a cleared wiki would otherwise return results for deleted pages.

Under The Hood

The skill is instructions for the agent. It copies and deletes markdown files inside the vault, writes the archive metadata and appends to the log. It never touches the Obsidian settings folder or an env file in the vault. When a QMD collection is configured it runs the qmd command line tool to update, embed and verify the search index. It does not fetch web pages or call remote APIs.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers