How do I install the Permanent Rebuilder skill?

Run npx skillmds@latest add atman-33/permanent-rebuilder in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Permanent Rebuilder safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Permanent Rebuilder?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Permanent Rebuilder free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Permanent Rebuilder?

atman-33 (@atman-33) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Permanent Rebuilder by atman-33 — Agent Skill

Name: Permanent Rebuilder
Author: atman-33

Permanent Rebuilder

Rebuild and maintain an Obsidian vault's permanent knowledge base for work knowledge and learning notes. Use when asked to reorganize permanent, design hub/leaf/MOC structure, standardize frontmatter (especially required summary), define tag taxonomy, generate a safe restructure plan (dry-run), and apply non-destructive moves/renames while preserving links.

atman-33 dc40b4a 12 files · 22.3 KB Updated Sep 17, 2026

File contents

Permanent Note Rebuilder

Use this skill to help a user restructure and continuously maintain the permanent/ folder as a durable knowledge base.

Operating Principles

Prefer minimal folders and strong metadata.
Require a decisive summary in every permanent note.
Treat Hub notes as long-form, navigational documents; treat Leaf notes as reusable units.
Avoid destructive operations. Default to planning and dry-runs.

Target Folder Layout

Adopt this layout under permanent/:

permanent/00_inbox/ — promoted candidates awaiting normalization
permanent/10_hub/ — long-form syntheses, study notes, indexes
permanent/20_leaf/ — reusable notes (how-to, principles, decisions, glossary)
permanent/90_meta/ — rules, templates, tag dictionary

If the vault already uses a different structure, map existing folders into these four buckets rather than inventing many new categories.

Required Metadata

For every note in permanent/, enforce:

summary: 1–2 lines describing what the note provides
created: YYYY-MM-DD

Recommended:

updated: YYYY-MM-DD
status: seed | draft | evergreen | deprecated
tags: role-based tags (see references)
related: list of wiki links

Workflow (Plan → Apply → Maintain)

Scan the current permanent/ and produce a report.
- Use scripts/scan_permanent_notes.py.
Design the taxonomy and templates.
- Read references/tag-taxonomy.md and references/note-templates.md.
Build a restructure plan (moves + metadata fixes), but do not apply it yet.
- Use scripts/build_restructure_plan.py.
Apply the plan safely.
- Prefer a staged approach: move files first, then add/normalize metadata, then update MOCs.
- Use scripts/apply_restructure_plan.py with --dry-run first.
Maintain continuously.
- New notes land in 00_inbox/ with minimal metadata.
- Periodically convert inbox items into hub/leaf and update MOCs.

Link & Rename Safety

Prefer moving files without renaming first.
If renaming, do it after moves, and update wiki links.
Keep note titles stable; use aliases rather than frequent renames.

Bundled Resources

Templates: assets/templates/*.md
References: references/*.md
Scripts: scripts/*.ps1

---name: permanent-rebuilderdescription: Rebuild and maintain an Obsidian vault's permanent knowledge base for work knowledge and learning notes. Use when asked to reorganize permanent, design hub/leaf/MOC structure, standardize frontmatter (especially required summary), define tag taxonomy, generate a safe restructure plan (dry-run), and apply non-destructive moves/renames while preserving links.---# Permanent Note RebuilderUse this skill to help a user restructure and continuously maintain the `permanent/` folder as a durable knowledge base.## Operating Principles- Prefer minimal folders and strong metadata.- Require a decisive `summary` in every permanent note.- Treat **Hub** notes as long-form, navigational documents; treat **Leaf** notes as reusable units.- Avoid destructive operations. Default to planning and dry-runs.## Target Folder LayoutAdopt this layout under `permanent/`:- `permanent/00_inbox/` — promoted candidates awaiting normalization- `permanent/10_hub/` — long-form syntheses, study notes, indexes- `permanent/20_leaf/` — reusable notes (how-to, principles, decisions, glossary)- `permanent/90_meta/` — rules, templates, tag dictionaryIf the vault already uses a different structure, map existing folders into these four buckets rather than inventing many new categories.## Required MetadataFor every note in `permanent/`, enforce:- `summary`: 1–2 lines describing what the note provides- `created`: YYYY-MM-DDRecommended:- `updated`: YYYY-MM-DD- `status`: seed | draft | evergreen | deprecated- `tags`: role-based tags (see references)- `related`: list of wiki links## Workflow (Plan → Apply → Maintain)1. **Scan** the current `permanent/` and produce a report. - Use `scripts/scan_permanent_notes.py`.2. **Design** the taxonomy and templates. - Read `references/tag-taxonomy.md` and `references/note-templates.md`.3. **Build** a restructure plan (moves + metadata fixes), but do not apply it yet. - Use `scripts/build_restructure_plan.py`.4. **Apply** the plan safely. - Prefer a staged approach: move files first, then add/normalize metadata, then update MOCs. - Use `scripts/apply_restructure_plan.py` with `--dry-run` first.5. **Maintain** continuously. - New notes land in `00_inbox/` with minimal metadata. - Periodically convert inbox items into hub/leaf and update MOCs.## Link & Rename Safety- Prefer moving files without renaming first.- If renaming, do it after moves, and update wiki links.- Keep note titles stable; use `aliases` rather than frequent renames.## Bundled Resources- Templates: `assets/templates/*.md`- References: `references/*.md`- Scripts: `scripts/*.ps1`

Frequently asked questions