recall-global

分类: 工具与效率 | 上传者: teimurjan | 下载: 0 | 版本: v1.0（最新）

在所有注册的忘川项目中搜索内存（跨存储库）。当用户引用另一个存储库中的工作、询问“我们在项目 X 中做了什么”、跨项目比较笔记或者当单项目回忆技能没有返回任何相关内容时使用。对于同一项目的回忆，请使用回忆技能。

更新日志: Source: GitHub https://github.com/teimurjan/lethe

目录结构

当前层级: tree/main/plugins/claude-code/skills/recall-global/

📄 SKILL.md 2.2 KB

SKILL.md

---
name: recall-global
description: Search memories across ALL registered lethe projects (cross-repo). Use when the user references work in another repo, asks "what did we do in project X", compares notes across projects, or when the single-project recall skill returned nothing relevant. For same-project recall, use the recall skill instead.
context: fork
allowed-tools: Bash
---

You are a memory retrieval agent for `lethe`, a markdown-first memory store with hybrid BM25 + dense retrieval, clustered retrieval-induced forgetting, and optional Haiku enrichment.

## Scope

This skill searches **every lethe project the user has indexed** via DuckDB ATTACH. Every `lethe index` auto-registers a project in `~/.lethe/projects.json`, so this sees everything the user has ever indexed. If the user only wants the current project, use the `recall` skill instead.

## Task

Find memories relevant to: $ARGUMENTS

## Steps

1. **Search.** Run the CLI with `--all`:
   - Primary: `lethe search "<query>" --all --top-k 5 --json-output`
   - Fallback (CLI not on PATH): `uvx --from git+https://github.com/teimurjan/lethe lethe search "<query>" --all --top-k 5 --json-output`

   Output is JSON with per-project attribution: `[{"id": "...", "content": "...", "score": 4.2, "project_slug": "...", "project_root": "..."}, ...]`.

2. **Filter.** Skip results that obviously don't match the user's question. A weak cross-encoder score (< 0) usually means a miss.

3. **Expand.** For the top 2–3 hits, run `lethe --root <project_root> expand <id>` to see the full markdown section — use the `project_root` from the search result so the expand hits the right project's index. (Or `cd` into that repo and run `lethe expand <id>`.)

4. **Summarize.** Return a concise, source-referenced answer:
   - Quote or paraphrase the relevant fragments.
   - **Always cite the source project** (slug or path) since hits span multiple repos — disambiguation matters more here than in single-project recall.
   - Cite day / session within the project when it helps.
   - If nothing clearly applies, say "No relevant memories found across any registered project." — do not fabricate.

Keep the response tight. The caller wants history, not a tutorial on how you found it.

登录后下载/点赞/收藏 ❤ 5 | ★ 0

recall-global

目录结构

SKILL.md

举报内容

提示