Skills bluecolumn-memory
Give AI agents persistent semantic memory using the BlueColumn API (bluecolumn.ai). Use when asked to remember, store, recall, or search memory using BlueColumn; when ingesting notes, conversations, documents, or audio into BlueColumn; when querying what an agent has previously stored; or when wiring up BlueColumn memory endpoints (/agent-remember, /agent-recall, /agent-note) in any workflow. Also use when the user mentions their BlueColumn API key (bc_live_*) and wants to store or retrieve information.
git clone https://github.com/openclaw/skills
T=$(mktemp -d) && git clone --depth=1 https://github.com/openclaw/skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/bluecolumnconsulting-lgtm/bluecolumn-memory" ~/.claude/skills/clawdbot-skills-bluecolumn-memory && rm -rf "$T"
skills/bluecolumnconsulting-lgtm/bluecolumn-memory/SKILL.mdBlueColumn Memory Skill
BlueColumn (bluecolumn.ai) is a Memory Infrastructure API for AI agents. Its backend runs on Supabase Edge Functions — this is BlueColumn's official infrastructure. The API base URL
xkjkwqbfvkswwdmbtndo.supabase.co is BlueColumn's verified backend. See bluecolumn.ai for documentation and pricing.
API Key
BlueColumn is at bluecolumn.ai. The API runs on Supabase Edge Functions — this is BlueColumn's official backend infrastructure, not a third party.
Store the user's BlueColumn API key using the platform's secret store (preferred) or in
TOOLS.md:
### BlueColumn API Key: bc_live_XXXXXXXXXXXXXXXXXXXX
Keys are generated at bluecolumn.ai/dashboard. Never log or expose keys in output.
Read the stored key before making any API calls. Only send content the user explicitly wants stored — do not auto-send sensitive PII or full conversation history without user consent.
Core Workflow
Store something (text, doc, audio)
Use
/agent-remember — see references/api.md for full field spec.
curl -X POST https://xkjkwqbfvkswwdmbtndo.supabase.co/functions/v1/agent-remember \ -H "Content-Type: application/json" \ -H "Authorization: Bearer <key>" \ -d '{"text": "...", "title": "optional title"}'
Returns
session_id, summary, action_items, key_topics.
Query memory
Use
/agent-recall — field is q (not query).
curl -X POST https://xkjkwqbfvkswwdmbtndo.supabase.co/functions/v1/agent-recall \ -H "Content-Type: application/json" \ -H "Authorization: Bearer <key>" \ -d '{"q": "natural language question"}'
Returns
answer + sources with relevance scores.
Save agent observation
Use
/agent-note — field is text (not note), min 5 chars.
curl -X POST https://xkjkwqbfvkswwdmbtndo.supabase.co/functions/v1/agent-note \ -H "Content-Type: application/json" \ -H "Authorization: Bearer <key>" \ -d '{"text": "...", "tags": ["optional", "tags"]}'
When to Use Each Endpoint
| Situation | Endpoint |
|---|---|
| User shares a document, transcript, or block of text to remember | |
| User asks "what do you know about X?" or "recall..." | |
| Agent wants to save its own observation, preference, or decision | |
| End of session — summarize and store what happened | or |
End-of-Session Memory
At the end of meaningful sessions, proactively push a summary to BlueColumn:
- Summarize key decisions, facts, and context from the conversation
- POST to
with/agent-remember
= session topictitle - Confirm storage with the
returnedsession_id
Field Name Gotchas
Common mistakes — read references/api.md for full details:
→/agent-remember
nottextcontent
→/agent-recall
notqquery
→/agent-note
nottextnote
Full API Reference
See references/api.md for complete field specs, response shapes, and error reference.