Docs and skills

Use Knowledge → Docs as your main curation workflow, and prefer Skill delivery for reusable agent guidance. Evaluations can retain many individual facts. Docs assemble related facts into a document you can review as a whole, so you can improve a coherent set of instructions without promoting every finding separately.

A doc is the guidance you review and approve in Capacitor. A skill is a delivery option for that approved document: it installs instructions that an agent can load when the task calls for them. Keep automatic injection for short guidance that needs to be present from the start of a session.

Review a document and its member facts

Choose the repository in Scope, open Knowledge → Docs, and select Agent when the Agent/Human selector is shown. Each topic lists its state, member-fact count, and any approved version or pending draft.

Open a topic and review three parts:

1. Pending draft is the proposed guidance. Check that it gives useful, specific instructions, preserves important exceptions, and applies to the work you intend it to guide.
2. Serving is the currently approved version, if one exists. Compare the draft with it: a new draft should retain useful guidance while incorporating the new lessons.
3. Members lists the facts behind the topic. Check that the draft represents them accurately and does not turn a one-off incident into a universal rule.

If a member fact needs more investigation, switch to Facts, search for a distinctive phrase from it, and open its detail. Inspect the source sessions, sightings, related work, and curation history. You can then return to the document with the evidence you need to make a decision.

Edit the draft to remove duplication, resolve contradictions, and explain when the instructions apply. Choose Save edit to keep your changes. Editing the document does not rewrite its underlying facts; use Facts and curation to correct an individual finding when needed.

Approve as a skill

For a document you are ready to use:

1. Under Approve as, select Skill.
2. Leave Injection off unless this guidance also needs to be included automatically at every applicable session start.
3. Choose Approve. The approved version becomes the one available for delivery.
4. Sync the skill on the machines where you use your agents.

You need curation permission at the document’s scope to edit or approve it. If Skill is disabled, the document is restricted to particular session kinds or flow roles. Those documents are injection-only: an installed skill cannot enforce those per-session restrictions.

Human guidance has a separate Human view and Publish digest action. Digests are for people; they are not delivered as agent skills or injected instructions.

Why injection is capped

Session-start injection adds guidance to the agent’s context before the task begins. Sending every retained fact or an entire library of documents would consume that context on every session. Capacitor selects a bounded set instead.

The v1.1.1 server defaults are:

Limit	Default
One document approved for injection	4,000 characters
Documents included at session start	Up to 3
Individual facts selected across repository, project, and organization scopes	Up to 8
Combined document bodies and individual fact text	16,000 characters

These limits are configurable by the server operator. The approval dialog displays the current per-document limit. If a body exceeds it, Injection is unavailable; approve it as a Skill, or shorten it if the guidance really needs to be present at session start.

Approval for injection does not guarantee that a document appears in every session. Audience and applicability still matter, as do the count and character budgets. If the combined text exceeds the budget, lower-weight documents are omitted first, followed by lower-ranked individual facts if necessary. Whole entries are omitted rather than cutting instructions partway through.

Skills avoid placing the full document body into every session’s startup context. The agent loads the instructions when needed. Prefer this for procedures, detailed conventions, and guidance that applies to particular kinds of work. Keep injection small and deliberate.

Install and refresh skills

After approval, run inside the relevant repository:

kcap skills sync --dry-run
kcap skills sync

Sync installs the approved versions into the detected supported agents’ user skill directories. It updates previously installed Capacitor skills and removes ones no longer served. Your own skills are left alone, and nothing is committed to the repository.

For example, after syncing a deployment skill, ask your agent:

Use our deployment skill to prepare this release and check the rollback procedure.

Run sync again after approving an update or revoking a document. To enable periodic refresh at Claude Code session start:

kcap config set skills.auto_sync true

Automatic sync is off by default and refreshes at most once every six hours per repository and target directory. Use manual sync when you want an approved change immediately. Make lasting edits in Knowledge → Docs, then sync; the installed files are managed copies of the approved version.

Keep guidance current

A new draft does not silently replace the approved version. Review the new wording and member facts, then Approve it or Reject draft to keep the serving version. Use Dismiss for an unapproved candidate you do not want to turn into guidance.

Revoke stops serving an approved document. Choose whether its members stay suppressed from individual guidance or return to leftovers, where they can become eligible again. Keep them suppressed when the topic itself is unsuitable; release them when you want to reconsider the facts individually. Restore brings a revoked document back into the review workflow.

Use Facts and curation for a specific incorrect or misplaced lesson, and Curation write-back when a short rule should live in version-controlled instruction files. Neither requires you to work through the entire fact list before approving useful skills.