Recall and save insights using sage_recall_knowledge and sage_save_knowledge MCP tools. INVOKE WHEN: user asks "what do we know about", "recall", "remember this"; starting research on a topic that may have prior knowledge; user wants to save an insight for future use. DO NOT INVOKE: for general questions without stored context.
Recalls stored insights and saves new knowledge using keyword-triggered injection.
/plugin marketplace add b17z/sage/plugin install b17z-sage@b17z/sageThis skill inherits all available tools. When active, it can use any tool Claude has access to.
You have access to a knowledge base of stored insights, decisions, and research findings. When a query relates to stored knowledge, relevant items are automatically injected into your context.
Knowledge items are stored in ~/.sage/knowledge/ with keyword triggers. When your query matches those triggers, the relevant knowledge is automatically recalled and injected.
You'll see a notification like:
π Knowledge recalled (2)
ββ gdpr-summary (~450 tokens)
ββ consent-patterns (~280 tokens)
Knowledge items capture durable insights that are useful across sessions:
| Type | Example |
|---|---|
| Research conclusions | "GDPR Article 6 requires explicit consent for AI training" |
| Validated decisions | "We chose PostgreSQL over MongoDB because..." |
| Domain expertise | API patterns, regulatory summaries, technical constraints |
| User preferences | "Prefers academic sources", "Wants concise answers" |
| Project context | Tech stack, architecture decisions, constraints |
~/.sage/knowledge/
βββ index.yaml # Registry with triggers
βββ global/ # Available to all skills
β βββ api-patterns.md
βββ skills/ # Skill-scoped knowledge
βββ privacy/
βββ gdpr-summary.md
Each item has:
sage knowledge add notes.md --id gdpr-summary --keywords "gdpr,privacy,consent"
sage knowledge add api-guide.md --id api-patterns --keywords "api,rest" --skill web-dev
Say "save this as knowledge" or "remember this" after discovering something worth preserving:
You: That's really useful about GDPR consent. Remember this.
Claude: [Extracts key insight and saves to knowledge base]
Saved knowledge: gdpr-consent-requirements
Keywords: gdpr, consent, legal basis
Just ask questions. If your query matches stored knowledge, it's injected automatically.
You: What do we know about GDPR?
Claude: [Recalls and presents relevant stored knowledge]
sage knowledge match "How does GDPR affect our API?"
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.