mindpalacelisted

Resource-first knowledge vault for an AI agent. Single source of truth per resource: infra/ for servers, hosting and DNS; accounts/ for platform logins per owner or client; projects/ as thin pointer files that link to infra and accounts via YAML frontmatter relations. Plus runbooks/ for repeatable ops, docs/ for artifacts, and LOG.md as the raw timeline. Use this skill when the user asks about credentials, secrets, API keys, server URLs, ports, deploy steps, account logins, past decisions or project docs; when scaffolding a new project, server or account entry; or when recording knowledge that should survive the session. Trigger phrases include "where are the credentials", "what's the prod URL", "how do we deploy", "scaffold a new project", "save this to the vault", "check the vault for X", "what server runs Y", "rotate keys", "what client owns Z".
aashutosh396/mindpalace-skill · ★ 0 · AI & Automation · score 73

Install: claude install-skill aashutosh396/mindpalace-skill

# mindpalace — resource-first knowledge vault A layout and a set of rules that let an AI agent build a durable second brain instead of re-learning your world every session. The core idea: **shared resources live in dedicated files that many projects reference — never duplicated.** One server, one file. One client account, one file. Projects are thin pointers that link to them. A credential exists in exactly one place, so rotating it is a one-file edit, not a grep-and-pray. This file is the whole skill. It is host-agnostic — see `README.md` for how to load it into Claude Code, Claude.ai, the OpenAI Agents SDK, Cursor, or any harness that can read a markdown instruction file. --- ## Location Resolve the vault root in this order: 1. `$MINDPALACE_VAULT`, if set 2. `~/.mindpalace/vault/` — the default, and the same path the full mindpalace tool uses 3. A `vault/` or `mindpalace/` directory in the current project If none exists, offer to create one (see **Bootstrapping** below). Never guess a path and never scatter files outside the resolved root. --- ## Mental model ``` infra/<resource>.md ← one file per server, hosting plan, DNS zone, CI runner accounts/<owner>.md ← one file per party — a client, or yourself projects/<slug>.md ← THIN pointer; frontmatter links to infra + accounts runbooks/<verb>-<x>.md ← repeatable procedures docs/<type>/ ← dated artifacts: PDFs, diagrams, exports, notes README.md ← indexes of every resource, acco