toolkit-recall
Search past decisions, prior research, conversation history, monorepo docs, and fetched web pages. Use toolkit recall search to find context from previous work, and toolkit fetch to save web pages for future search.
Best use case
toolkit-recall is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Search past decisions, prior research, conversation history, monorepo docs, and fetched web pages. Use toolkit recall search to find context from previous work, and toolkit fetch to save web pages for future search.
Teams using toolkit-recall should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/recall/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How toolkit-recall Compares
| Feature / Agent | toolkit-recall | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Search past decisions, prior research, conversation history, monorepo docs, and fetched web pages. Use toolkit recall search to find context from previous work, and toolkit fetch to save web pages for future search.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Toolkit Recall Skill Local RAG system for searching across Claude plans, research, memories, fetched docs, and monorepo docs. ## When to Use - **Before answering knowledge questions**: run `toolkit recall search "<query>"` to check if relevant context exists in plans, research, or previously fetched docs - **When fetching docs or web pages**: use `toolkit fetch <url>` instead of raw `lightpanda fetch` — it saves and indexes the content for future search - **When the user creates an important document**: run `toolkit recall add <path>` to index it - **Periodically**: run `toolkit recall reindex` to pick up new files in watched directories ## Commands ### Fetch Web Pages ```bash # Fetch a page (lightpanda, fast, handles SPAs) toolkit fetch <url> # Fetch with PinchTab (real Chrome, for sites that block lightpanda) toolkit fetch <url> --browser # Verbose output (shows timing, engine, save path) toolkit fetch <url> --verbose # Crawl a docs site (coming soon) toolkit fetch <url> --crawl --depth 2 ``` Fetched pages are saved to `~/.recall/fetched/<domain>/<slug>.md` with YAML frontmatter. ### Search ```bash # Hybrid semantic + keyword search toolkit recall search "vector database embedding" # Limit results toolkit recall search "deployment" --limit 5 # Search mode: hybrid (default), semantic, keyword toolkit recall search "query" --mode keyword ``` ### Index Management ```bash # Index a file or directory toolkit recall add ~/Documents/notes/ # Remove from index toolkit recall remove ~/Documents/notes/old-file.md # Re-scan all watched directories toolkit recall reindex # Full re-index (re-embed everything, ignore content hashes) toolkit recall reindex --full ``` ### Status & Debugging ```bash # Full dashboard: index stats, daemon health, performance toolkit recall status # Performance deep-dive (latency histograms, throughput) toolkit recall status --perf # Full diagnostic check toolkit recall debug # View logs toolkit recall logs toolkit recall logs --follow toolkit recall logs --level error --since 1h ``` ### Daemon ```bash # Manage background watcher (auto-indexes on file changes) toolkit recall daemon start toolkit recall daemon stop toolkit recall daemon status # Run watcher in foreground (for testing) toolkit recall watch ``` ## Watched Directories These are automatically indexed by the daemon and `toolkit recall reindex`: | Directory | Source | | ---------------------------------- | ------------------- | | `~/.claude/plans/` | claude-plan | | `~/.claude-extra/**` | claude-extra | | `~/.claude-extra/research/` | claude-research | | `~/.claude/projects/*/memory/` | claude-memory | | `~/.recall/fetched/**` | fetched | | `~/.claude/projects/**` (\*.jsonl) | claude-conversation | | `~/git/monorepo/packages/docs/` | monorepo-docs | ## Troubleshooting ### "toolkit: command not found" Install the binary: ```bash cd ~/git/monorepo/packages/toolkit && ./install.sh ``` ### Search returns no results Check if the index has been built: ```bash toolkit recall status toolkit recall reindex ``` ### Fetch returns empty content Try PinchTab for sites that block lightpanda: ```bash toolkit fetch <url> --browser ```
Related Skills
zod-patterns
Zod schema validation, type-safe development, and strict TypeScript patterns. When user works with Zod, validates data, creates schemas, handles form validation, mentions z.object/z.string patterns, needs runtime validation, type-safe code, or strict TypeScript configuration.
zellij-helper
Zellij terminal multiplexer for session management, layouts, and pane operations When user mentions Zellij, terminal multiplexer, zellij commands, sessions, panes, layouts, or tabs
worktree-workflow
Git worktree workflow for isolated feature development and PR creation When user starts new work, needs to switch contexts, or wants parallel development
vite-react-helper
Vite + React for fast modern web development - build config, HMR, hooks, state management, and performance patterns When user works with Vite, React, creates components, manages state, uses hooks, or configures Vite builds
version-management
Use when asking about version management, Renovate annotations, versions.ts patterns, or pinning image/chart versions.
typst-authoring
This skill should be used when the user asks to "write Typst", "create a Typst document", "format in Typst", "convert to Typst", "Typst syntax", "Typst template", "Typst math", "Typst table", or works with .typ files. Provides comprehensive Typst markup, scripting, math, layout, and styling reference for authoring documents. Also use proactively when generating .typ output files (e.g., in deep-research reports).
typescript-helper
TypeScript development guidance for type systems and tooling When user works with .ts or .tsx files, mentions TypeScript, or encounters type errors
torvalds-deployment
Use when asking about adding services, createXxxDeployment patterns, or homelab deployment conventions. Services use per-namespace charts.
terraform-helper
Terraform and OpenTofu infrastructure as code - HCL, providers, modules, state management, and CLI operations When user works with .tf files, mentions Terraform, OpenTofu, tofu, HCL, infrastructure as code, or tf commands
terminal-concepts
Comprehensive guide for building CLI and TUI applications - terminal internals, design principles, and battle-tested patterns When building CLI/TUI apps, implementing argument parsing, handling terminal input/output, escape codes, buffering, signals, or asking about terminal development concepts
talos-helper
Talos Linux cluster administration using talosctl When user mentions Talos, talosctl, or Talos cluster operations
tailscale-helper
Tailscale VPN and networking - CLI operations, MagicDNS, ACLs, SSH, funnel, serve, and network administration When user mentions Tailscale, tailscale commands, VPN, MagicDNS, tailnet, or Tailscale networking