Eldoria Vault Auditor

This skill follows CONVENTIONS.md for tag formatting, linking rules, and vault structure. Key paths:

Audit Procedures

1. Targeted Entity Audit

When the DM says something like "X was cut" or "X was moved to Y":

1. Grep the entire vault for the entity name (try variations — with/without apostrophes, partial matches)
2. Categorize each mention:
   • Stale reference — a file mentions the entity as if it still exists in the old location
   • Valid reference — the entity's actual files in its correct (or new) location
   • Historical reference — session journals or event logs that describe past events (these are usually fine to keep)
   • Index/generated files — HTML docs, JSON indexes, workspace config (flag for the DM but lower priority)
3. Report findings as a table: file path, line number, what it says, and recommended action (remove, update, or keep)
4. Confirm with the DM before making any changes
5. Apply fixes — edit files to remove or update stale references

2. Settlement Audit

When the DM asks to audit a settlement (or you're about to create content there):

1. Read the settlement's private and public files to get the listed entities (NPCs, stores, landmarks, districts)
2. Remember the embed rule: Private settlement files embed the public file via ![[Public/...]]. Entities listed in the public file are already visible in the private view — don't flag them as "missing from private." Only flag entities that are absent from both the private-only sections and the embedded public content.
3. List the actual files in that settlement's directory (both Private and Public)
4. Cross-reference: For each entity mentioned in either file, check if a matching file exists
5. Check the reverse: For each file in the directory, check if either the private or public settlement file mentions it
6. Report discrepancies:
   • Phantom entities — mentioned in the settlement file but no corresponding file exists (may have been cut or never created)
   • Unlisted entities — files exist but aren't mentioned in either the private or public settlement overview (may need to be added or may be orphaned)
   • Location mismatches — entities whose files place them in a different settlement than where they're referenced

3. Cross-Reference Audit

For a broader consistency check:

1. Scan wiki-links in a file or set of files
2. Verify each link target exists — check if the linked file is actually present
3. Check public/private pairing — every entity should have both a private and public file
4. Verify tag consistency — do the tags in frontmatter match the entity's actual location and type?
5. Check link scope — public files should only link to other public files

4. Duplicate Detection

When the DM suspects duplicates:

1. Search for the entity name across the entire vault
2. Check for near-duplicates — similar names, same role, same location (e.g., two blacksmiths in one small town)
3. Compare file contents — are they truly duplicates or intentionally separate?
4. Report with context — show what's in each file so the DM can decide which to keep

Reporting Format

Present audit findings as a clear, scannable list. Group by severity:

## Audit: {Target}

### Stale References (action needed)
| File | Line | Reference | Issue | Fix |
|---|---|---|---|---|
| Highreach.md | 19 | Steelshaper's Forge | Listed in Blacksmith District but store was moved to Ardenville | Remove from district list |

### Warnings (DM decision needed)
- {File} mentions {Entity} which has no corresponding .md file — was this intentional?

### Info (no action needed)
- Session Journal 12 mentions {Entity} in past tense — historical reference, no change needed

Keep the report scannable. The DM should be able to glance at it and know what needs fixing in under 30 seconds.

Fixing References

When the DM approves changes:

• Settlement files: Remove the stale bullet point or line referencing the cut entity
• NPC files: Update or remove relationship links to moved/deleted entities
• Store files: Update location references in frontmatter and body text
• Public files: Mirror any changes made to private files (maintaining the no-secrets rule)
• Never delete session journals or historical event references — those describe what happened, not what currently exists
• Never delete entity files without explicit DM confirmation — just flag them

What NOT to Change

• Session journals — past events are history, even if they reference entities that no longer exist
• Event logs — same as journals
• DM scratch notes — these are working documents, not canonical references
• Entity files themselves — unless the DM explicitly says to delete them; the audit skill flags issues, the DM decides

Removing Content

The vault is a living document — content gets removed just as often as it gets added. Removing outdated, incorrect, or superseded information is a core part of vault maintenance, not an exception. When the DM says something is no longer relevant, remove it cleanly:

What removal looks like

• Delete a bullet from a settlement's NPC list, store list, or landmark list
• Remove an interaction entry from an NPC's ## Interactions section
• Clear a section that's become irrelevant (e.g., a Plot Hook that was resolved)
• Remove a wiki-link from a Links section when the connection no longer applies
• Update frontmatter — change status fields, remove stale tags
• Delete entire files — only with explicit DM confirmation, and always clean up references in other files afterward

Removal rules

1. Always update both private and public files — if a bullet is removed from a public NPC file, the private file's embed will reflect it automatically, but check for any private-only references too
2. Clean up cross-references — when removing an entity, search for every file that links to it and update or remove those links
3. Never silently remove — when the DM asks for a removal, confirm what will be affected and execute. If removing something would break other files, list the cascade before proceeding
4. Session journals and event logs are exempt — historical records describe what happened, not what currently exists. Never edit these even if they reference removed content

Common Patterns

These are the most frequent issues you'll find: