capture

Save typed knowledge artifacts into the project Brain store.

20|2|Updated May 16, 2026
One-click install
npx skills add https://github.com/reddb-io/red-skills --skill capture-reddb-io
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: capture
Source: https://github.com/reddb-io/red-skills/tree/main/plugins/brain/skills/core/capture
Command: npx skills add https://github.com/reddb-io/red-skills --skill capture-reddb-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long-lived human and project knowledge — decisions, ideas, people, open questions — gets lost across chat sessions and context resets. This Skill routes that knowledge into the durable Brain store so it can be searched and referenced later. ## Core Features & Use Cases - Typed Artifact Capture: Maps user input to the correct Brain artifact kind (decision, question, idea, person, meeting, source, and more) before storing. - Brain-vs-Memory Routing: Distinguishes long-lived knowledge from short operational work facts, routing the latter to the memory store instead. - MCP or CLI Execution: Captures via the brain_capture MCP tool when available, falling back to the red-skills-brain CLI command. - Use Case: After a design discussion, tell the agent to "remember this decision" and it stores a typed decision artifact with full context, returning an artifact id you can retrieve later with search. ## Quick Start Ask the agent to capture the decision you just made about the database schema into Brain with tags for the backend topic.

Frequently Asked Questions about capture

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

FAQPage Schema
How do I save a decision or idea to Brain?▼

Tell the agent to capture, save, or remember the content. The skill maps it to the closest artifact kind such as decision, idea, or note, then calls brain_capture or the red-skills-brain CLI and returns the stored artifact id.

What is the difference between Brain and Memory storage?▼

Brain holds long-lived human and project knowledge like decisions, people, and plans. Memory holds short operational work facts like gotchas and code why-notes, which should be routed to the memory store skill instead.

What artifact kinds can I capture in Brain?▼

Brain supports kinds including decision, question, idea, note, concept, playbook, meeting, source, pattern, event, claim, rule, person, and organization. When unsure, the skill defaults to note rather than inventing new kinds.

Can I capture knowledge without the MCP tool installed?▼

Yes. When the brain_capture MCP tool is unavailable, the skill falls back to running the red-skills-brain capture CLI command with title, kind, content, and optional tags.

What should not be captured into Brain?▼

Do not capture secrets, credentials, API keys, or passwords. Short-lived operational work facts belong in Memory, and files under .red/brain should never be hand-written directly.