Citadel

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.

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.

Use to capture durable engineering knowledge into Citadel automatically and proactively while working in an org repo. Covers (0) proactive citadel_search at task start plus optional citadel_share_session for dead-end routes (user-approved), (1) mid-session citadel_ingest for durable facts (personal-by-default; all seat writes land on the Node — Central via Promotion Agent only), (2) git pre-push commit snapshots (universal baseline — Cursor, Codex, Claude), (3) optional Claude Code SessionEnd distill, and (4) server-side Railway cron for GitHub org sync, Linear sync, and the learning pipeline. Triggers include "auto sync my sessions", "remember this in citadel", "proactive ingest", "set up citadel autosync", "personal kb sync", "install autosync", and https://citadel-archive-production.up.railway.app/skills/proactive-ingest.

Use when a user asks project, source, architecture, or operational questions that may be answered from the Citadel Organization Vault; wants to persist durable project knowledge in Citadel; asks about organization memory, vault search, knowledge mesh, source-learning status, or needs to interact with the Citadel vault in any way. Triggers include "search citadel", "check citadel", "ask citadel", "add to citadel", "ingest into citadel", "citadel vault", "organization vault", and https://citadel-archive-production.up.railway.app/skills/vault.

Use when deciding what Citadel data may be quoted, committed, or shared; when onboarding agents to Masumi Citadel; or when the user asks what is public vs private, what goes in git, or whether vault content can be published. Triggers include "public or private", "what can I share", "citadel security boundary", "is the vault public", and /skills/boundary.