Citadel-Archive

Use when a user asks project, architecture, source, or operational questions that may be answered from the Citadel Organization Vault; wants to persist durable project knowledge; needs to connect an agent to Citadel; asks about organization memory, vault search, knowledge mesh, source-learning status, or wants to set up the Citadel MCP plugin for Claude Code, Codex, Cursor, or any MCP-capable coding agent. Triggers include "search citadel", "check citadel", "ask citadel", "add to citadel", "ingest into citadel", "citadel vault", "organization vault", "citadel mcp", "connect citadel", "citadel archive", "organization memory", "knowledge mesh", or any task requiring access to shared company/project memory.

Connects Claude Code, Cursor, Codex, or any MCP-capable agent to the Citadel Archive Organization Vault over its hosted MCP endpoint (no clone, no Python, no local install). Use when the user shares this skill URL, pastes a Citadel token, or says connect/set up/configure Citadel MCP, citadel plugin, organization vault MCP, or add citadel to my agent. Run the full workflow: detect client, collect only the token, write the remote MCP config (URL + Authorization header), verify, then search the vault. Triggers include connect citadel, set up citadel mcp, citadel mcp connector, citadel archive mcp, and https://citadel-archive-production.up.railway.app/skills/connect.

One-command teammate onboarding for Citadel. Use when a teammate wants to set up Citadel in a repo — connect their seat token, install the autonomous git-push + SessionEnd capture hooks, add the Citadel MCP server, and (optionally) declare Approved Capture Roots. Triggers include "onboard me to citadel", "set up citadel", "citadel onboard", "connect citadel", "install citadel here", and https://citadel-archive-production.up.railway.app/skills/onboard.