Search the C Brain trunk for notes relevant to a subject, and read the ones that matter. Use when the user asks what they already know about something, wants past decisions on a topic, says "did we solve this before", "what do I have on X", "check my notes", or when a task smells like something already worked out once.
Scanned 9/5/2026
Install to Claude Code
npx -y skills add Yuno15-bb/c-brain --skill recall --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Recall?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/yuno15-bb-recall)More formats (shields.io, HTML) on the badges page.
---
description: Search the C Brain trunk for notes relevant to a subject, and read the ones that matter. Use when the user asks what they already know about something, wants past decisions on a topic, says "did we solve this before", "what do I have on X", "check my notes", or when a task smells like something already worked out once.
---
# Recall from the trunk
Retrieve what is already known before working something out again.
## How
Run the recall, top 5, and read what comes back:
```bash
brain recall "$ARGUMENTS"
```
If `brain` is not on the PATH, the plugin ships it — call it directly:
`"${CLAUDE_PLUGIN_ROOT}/bin/brain" recall "$ARGUMENTS"`.
Each result gives a score, a note name and a path relative to the trunk
(`~/.c-brain/trunk`). **Open the ones above the noise floor and actually read
them** — the ranking is lexical, so it tells you where to look, never what is
true.
## Then
- Say what the notes establish, and cite each one by its path so the user can
check you.
- Say plainly when nothing relevant came back. A confident answer assembled
from three weakly-matching notes is worse than "the trunk has nothing on
this" — it looks like memory and is not.
- Never rewrite a note as a side effect of reading it.
## Scale
Recall holds well to about a thousand notes and degrades past that
(`tests/recall_benchmark.py` publishes the numbers). On a large trunk, prefer
several narrow queries over one broad one.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Recovers prior coding-agent session context by running `catchup <agent> --since-compact`, which extracts a clean summary of a previous Codex, Claude Code, Antigravity, OpenCode, or Pi Agent session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", or asks to recover/summarize a previous session before continuing. Do NOT use for the current conversation, git history, or any non-agent log.