ckl-knowledge

Capture decisions and patterns into an auditable knowledge graph with JTB+S envelopes.

Updated May 5, 2026
One-click install
npx skills add https://github.com/Alex980102/ckl-skill --skill ckl-knowledge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ckl-knowledge
Source: https://github.com/Alex980102/ckl-skill/tree/main/skills/ckl-knowledge
Command: npx skills add https://github.com/Alex980102/ckl-skill --skill ckl-knowledge

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

CKL Knowledge enables users to capture decisions, patterns, and lessons via the Capture/Intent Protocol (CIP), lifting them into an auditable knowledge graph with an explicit envelope (JTB+S) and Toulmin edges.

Core Features & Use Cases

  • CIP capture and auto-relate with JTB+S envelope to attach holder, container, and provenance to each knowledge atom.
  • Distill blocks into structured atoms (claim, proof, code) and relate them via Toulmin edges (GROUNDS, WARRANT, SUPPORTS, REBUTTAL) for robust reasoning traces.
  • Export/import and graph backup/restore capabilities to share and evolve knowledge across projects and teams.

Quick Start

Capture a decision block with CIP to seed the knowledge graph.

Frequently Asked Questions about ckl-knowledge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I capture decisions and lessons into a queryable knowledge graph?

You can capture decisions, patterns, and lessons into a queryable knowledge graph by using the Capture/Intent Protocol to lift blocks into an auditable structure with typed atoms, provenance envelopes, and Toulmin edges.

What is the best way to structure reasoning traces using Toulmin edges?

To structure reasoning traces with Toulmin edges, you distill knowledge blocks into typed atoms and relate them using GROUNDS, WARRANT, SUPPORTS, and REBUTTAL connections to map robust argumentation flows.

How do I manage the lifecycle of knowledge atoms from capture to archive?

You manage the knowledge atom lifecycle by using specific commands to capture, observe, promote, resolve, archive, deprecate, export, and import blocks while enforcing holder, container, and lineage constraints.

Does this knowledge graph approach support backup and export across projects?

The knowledge graph supports backup and export across projects by providing graph backup, restore, export, and import capabilities to share and evolve structured knowledge atoms between different teams.

How does the JTB+S envelope attach provenance to a knowledge atom?

The JTB+S envelope attaches provenance to a knowledge atom by binding specific holder, container, and lineage constraints to each captured block during the distillation process.

When do I need to distill blocks into typed atoms for my knowledge graph?

You need to distill blocks into typed atoms when you want to separate claims, proofs, and code snippets, enabling structured querying and explicit reasoning relationships within your knowledge graph.