aashutosh396

Mindpalace Skill — AI skill for Claude Code

AI community

🧠 A resource-first knowledge vault your AI agent can actually maintain — one portable SKILL.md for Claude Code, Claude.ai, OpenAI Agents SDK, Cursor or any wrapper.

How to install Mindpalace Skill

This entry records only its repository, not the path inside it, so there is no exact command to give. Open aashutosh396/mindpalace-skill and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Mindpalace Skill does

🧠 A resource-first knowledge vault your AI agent can actually maintain — one portable SKILL.md for Claude Code, Claude.ai, OpenAI Agents SDK, Cursor or any wrapper. Companion to the full mindpalace tool.

Alternatives in AI

  • Opencodex — Universal provider proxy for OpenAI Codex & Claude Code — use any LLM (Claude, Gemini, Grok, DeepSeek, Ollama… 12.3k ★
  • Anthropic SDK TypeScript — Access to Anthropic's safety-first language model APIs in TypeScript 2.1k ★
  • Flow Next — Plan-first AI workflow plugin for Claude Code, OpenAI Codex, and Factory Droid 569 ★

README

mindpalace — a knowledge vault your AI agent can actually maintain

🧠 mindpalace-skill

**A resource-first knowledge vault your AI agent can actually maintain.**

Drop one markdown file into Claude Code, Claude.ai, the OpenAI Agents SDK, Cursor, or your own wrapper — and your assistant stops re-learning your infrastructure every session.

[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](LICENSE) [![Skill format](https://img.shields.io/badge/format-SKILL.md-8A2BE2.svg)](SKILL.md) [![Works with](https://img.shields.io/badge/works%20with-Claude%20·%20OpenAI%20·%20any%20LLM-blue.svg)](#-install-it-in-your-wrapper)

[The skill](SKILL.md) · [Install](#-install-it-in-your-wrapper) · [Templates](templates/) · [Full tool](#-want-the-whole-thing-running-live)


The problem

Your agent is brilliant for twenty minutes and amnesiac forever after. You paste the same server IP into the same chat for the fourth time this month. Credentials end up copied across six notes, so rotating one means finding all six. Someone asks "what's actually running on that box?" and the honest answer is that nobody knows.

The idea

**Shared resources get dedicated files. Everything else links to them.**

One server → one file. One client account → one file. Projects are *thin pointers* that reference those files through YAML frontmatter relations, so a fact exists in exactly one place.

infra/hetzner-vps-01.md     ← the server: IP, SSH, what runs on it
accounts/acme-corp.md       ← the client: logins, billing owner
projects/storefront.md      ← thin pointer:  hosts_on: [hetzner-vps-01]
                                             client: acme-corp

Because the relations are plain YAML, "what runs on this box?" is a `grep`, not an archaeology expedition:

grep -l "hosts_on:.*hetzner-vps-01" vault/projects/*.md

Rotating a key is a one-file edit. Decommissioning a