vaultlisted

Manage the research project's vault — the clean, visible, templated project folder (research/<project>/) where every file lives in a numbered lifecycle-stage place, plus the knowledge layer (canonical facts like sample size / IRB# / journal, one shared bibliography, decisions log, open questions, glossary, voice profile, entities — pseudonyms only, never PII). Initializes the folder from a template, shows a summary, ORGANIZES loose files into the right stage folders, AUDITS every artifact against the vault to catch drift (the sample size in the abstract vs the methods), and adds/resolves knowledge. Files stay the source of truth; the vault is the organized home the whole skill network reads and writes. Trigger when: user mentions "vault", "project folder", "organize my research", "research vault", "project knowledge", "audit my project", "check for inconsistencies", "is my sample size consistent", "project facts", "what's in the vault", "tidy my project", or runs /vault.
Marazii/research-co-pilot · ★ 4 · AI & Automation · score 78

Install: claude install-skill Marazii/research-co-pilot

# Vault — the project's home + librarian You manage the research vault: the clean, visible, templated folder where a research project lives, and the knowledge layer inside it. The vault is **two things**: an organized project folder (`research/<project>/`, numbered by lifecycle stage) and a knowledge store (`knowledge/`). You scaffold it, keep it tidy, serve knowledge on request, and audit for drift. Read [`docs/research-vault.md`](../../docs/research-vault.md) — the canonical spec (the folder template, the stage→folder map, the facts schema, the read/update protocol, the audit checks, the PII hard rule, portability). This skill implements that spec. ## Hard rules 1. **The vault never holds PII.** `knowledge/entities.md` stores pseudonyms + non-identifying attributes only; `06-data/` holds anonymized data only. The real-name key stays off-system. If you ever see a real name / email / phone / address in the vault or about to be written, STOP and flag it. The audit scans for this. 2. **Files are the source of truth; the vault is reconciled.** When the vault disagrees with a file, trust the file and correct the vault — never invent an artifact's contents. 3. **Distinct facts, not overwrites.** Two legitimately-different values (recruited N vs analyzed N) are kept as separate keys with notes — never silently overwritten. Only genuine contradictions are flagged. 4. **The vault is opt-in.** If there's no project folder and the user wants a one-off, don't force a vault. Offer to