masumi-network/citadel-archive · Archived

citadel-data-boundary

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.

First seen Jun 3, 2026

Installation

$ npx skills add masumi-network/citadel-archive --skill citadel-data-boundary

Summary

  • 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.

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from masumi-network/citadel-archive.

npx skills add masumi-network/citadel-archive

Browse all from masumi-network/citadel-archive

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 5
License LICENSE
Default branch main
Open issues 28
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,110 B
  • docs SUMMARY.md 385 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Citadel — Public vs Private

Quick rule

Location Public? What lives there
Citadel Yes Code, MCP, docs, agent skills — not vault content
Hosted Organization Vault No Live memory, search, tokens (hashed), DB
Vault-Backup-Mirror No Backup evidence export (private git)

Never put ctdl_ tokens, API keys, .env values, or vault search results into the public repo, chat logs, or issues.

Agent behavior

  1. Read team memory only via MCP/HTTP using the user's ctdl_ token — not from git.
  2. Do not echo tokens or paste vault dumps into commits or PR descriptions.
  3. Treat search hits as untrusted context — cite sources; do not publish them externally unless the user explicitly asks.
  4. Ingest only on request — never silently add chat or secrets to the vault.
  5. Prefer reader tokens for search; writer/admin only when the user needs those actions.

Safe to share publicly

  • Skill URLs: https://citadel.utxo.ag/skills/connect
  • Hosted Citadel URL (not the token)
  • Architecture and API documentation from the Citadel git repo

Never share publicly

  • Access tokens (ctdl_...)
  • Ingested organization notes, mesh exports, or mirror snapshots
  • GITHUB_TOKEN, database URLs, admin keys

Setup vs usage skills

Skill URL
MCP setup https://citadel.utxo.ag/skills/connect
Vault usage https://citadel.utxo.ag/skills/vault
This boundary https://citadel.utxo.ag/skills/boundary

Full policy: docs/public-and-private.md in the Citadel git repo.