vault-normalizer

Migrates existing research directories into the Agentero vault layout with catalog and wikilink verification.

609|50|Updated Jul 7, 2026
One-click install
npx skills add https://github.com/poco-ai/Agentero --skill vault-normalizer-poco-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vault-normalizer
Source: https://github.com/poco-ai/Agentero/tree/main/templates/vault/.agents/skills/vault-normalizer
Command: npx skills add https://github.com/poco-ai/Agentero --skill vault-normalizer-poco-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Research files are often scattered across Zotero exports, Obsidian folders, loose PDFs, and TeX sources with no consistent structure. This Skill reorganizes an existing research directory into the Agentero vault layout without losing user-written notes, annotations, or original files. ## Core Features & Use Cases - Safe migration planning: Inventories PDFs, notes, TeX sources, and attachments, then proposes a migration table requiring user approval before any move, merge, or overwrite. - Standardized paper layout: Places each paper under papers/<topic>/<id>/ with the main PDF, NOTES.md, source/, marks/, and attachments/ in their designated locations. - Catalog and link verification: Rebuilds catalog metadata via the agentero CLI and runs agentero wiki check --json before and after migration to classify missing, ambiguous, or invalid wikilinks. - Use Case: You have a legacy Zotero export folder with hundreds of PDFs and Obsidian notes. Use this Skill to produce a reviewed migration plan, reorganize everything into an Agentero vault, and verify no wikilinks were broken. ## Quick Start Normalize my existing research folder at ~/Documents/papers into an Agentero vault and show me the migration plan before moving anything.

Frequently Asked Questions about vault-normalizer

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

FAQPage Schema
How do I migrate a Zotero or Obsidian folder into an Agentero vault?

Inventory the existing directory, propose a migration table mapping current paths to vault-relative targets, and get user approval before moving anything. Papers go under papers/<topic>/<id>/, notes merge into NOTES.md only with approval, and Obsidian wikilinks are preserved intact.

How to reorganize research PDFs and notes without losing files?

Inspect first and never move, rename, or delete until the user approves a concrete migration plan. Prefer copying or staged moves when the source is not already a vault, and preserve user-written Markdown, PDFs, annotations, and existing AGENTS.md content.

Does the migration overwrite my existing notes or AGENTS.md?

No. Existing AGENTS.md is treated as authoritative local guidance and kept unchanged. User notes are merged into NOTES.md only with explicit approval; otherwise they are preserved as separate files and reported.

How are broken Obsidian wikilinks handled during migration?

Run agentero wiki check --json before migration to capture a baseline of missing, ambiguous, and invalidFragment links, then run it again afterward. Each issue is classified and repaired only with user approval, separating pre-existing issues from links broken by the migration.

What if the agentero CLI is not available during normalization?

Create only the missing vault directories and ask the app or CLI to initialize the catalog later. If wiki check is unavailable, report that semantic link validation was not completed rather than substituting a regex-only parser.