Skip to content

Agent KnowledgeA portable standard for agent-readable knowledge packs.

Give agents facts, source trails, constraints, and maintained context without confusing knowledge with procedural skills.

Why this standard exists

Agent Skills gave agents a simple way to load procedural capability: instructions, scripts, references, and assets. Agent Knowledge applies the same file-first philosophy to durable knowledge assets.

The goal is not to replace RAG, wikis, notebooks, or skills. The goal is to define a small portable package format that lets agents answer these questions reliably:

  • What knowledge exists?
  • What sources does it come from?
  • Which parts are confirmed, draft, stale, or disputed?
  • What context should be loaded for this task?
  • Which claims can be traced back to source material?
  • Which indexes are acceleration layers rather than facts?

Core shape

text
customer-onboarding/
├── KNOWLEDGE.md      # Required: metadata + usage guide
├── sources/          # Raw source files, treated as read-only evidence
├── wiki/             # Maintained pages, decisions, entities, concepts
├── compiled/         # Runtime views: facts, playbooks, boundaries
├── indexes/          # Optional, rebuildable search/vector/graph indexes
├── runs/             # Ingest, lint, review, query logs
└── assets/           # Optional diagrams, templates, examples

Design rule

Knowledge packs are facts and context. Skills are methods and workflows.

Use Agent Skills to build, update, lint, and query Agent Knowledge packs. Do not hide real customer or domain knowledge inside a global skill when it needs its own source trail, status, ownership, and review lifecycle.

AI-friendly docs

Every document page includes a Copy Markdown button. Use it to copy the current source page into an AI session with frontmatter, diagrams, examples, and tables intact.

Draft open standard. Inspired by Agent Skills, LLM Wiki, source-grounded notebooks, and production RAG systems.