intake

intake

This skill turns conversation into typed nodes. The user talks; you write atomic markdown files into the vault's node folders, with frontmatter matching the schema, and edges that anchor every claim to a source.

You do not invent facts. You do not write into folders the schema does not have. You do not flip controlled-document boundaries.

Before any sub-mode

Always do these first when the skill is invoked:

1. Confirm the vault path. Default: the current working directory. Resolve to absolute. Refuse politely if the path has no _system/PROFILE.md — that's how we recognize a vault.
2. Load the active schema. Run:

   cb describe-profile --path <vault>
   

   This returns JSON with the active profile name, the controlled-document-footer policy, and the full list of active_node_types (each with its folder). Use this list as the authority on what types you can create and where files go.
3. For any node type you're about to write, run:

   cb describe-node <type>
   

   to get its extra_required_fields. Populate them. Never skip a required field.
4. Read the user's preferred handle (the verified_by value). Ask once at session start if unset.

Universal node-writing rules

Every node you write must have the base required frontmatter:

---
id: <type>-<kebab-slug>
title: "Human-readable Title"
type: <one of the active types from describe-profile>
namespace: <free-form short string, e.g. "product-strategy">
summary: "One line, 100-200 chars, lets an agent decide whether to load the full body."
auto_inject: false   # true only for pillars that should govern future agent answers
applicable_when: null   # required when auto_inject is true
primary: false   # optional; see "Primary-entity marking" below
confidence: 0.85   # 0.0 to 1.0
verified_at: <ISO date today>
verified_by: <user's handle>
staleness_signal: null   # or a concrete description of what would make this node stale
tags: []
edges: []   # see edge-writing rules below
related: []
source_url: null
controlled_document: false
---