Back to list
astrosteveo

search

by astrosteveo

Semantic memory for Claude Code - persistent context across sessions

0🍴 0📅 Jan 17, 2026

SKILL.md


name: search description: This skill should be used when the user asks to "search memory", "find in past sessions", "what did we decide about", "look up previous work on", or needs to retrieve specific information from project memory. context: fork hooks: Stop: - hooks: - type: command command: "${CLAUDE_PLUGIN_ROOT}/scripts/validate-search.sh" timeout: 10

Search - Query Project Memory

Search engram semantic memory for past context, decisions, and lessons.

Execution

Step 1: Parse Search Intent

From $ARGUMENTS, identify:

  • Query: What the user wants to find
  • Scope: Project-only or cross-project
  • Type: General search or insights (decisions/lessons)

Step 2: Select Search Strategy

User IntentTool to Use
General context, past workmemory_search
Past decisions or architecture choicesmemory_insights with insight_type: "decision"
Past bugs, gotchas, patternsmemory_insights with insight_type: "lesson"

General search:

mcp__plugin_engram-mcp_engram__memory_search
  query: "{semantic query}"
  n_results: 10

Search with type filter:

mcp__plugin_engram-mcp_engram__memory_search
  query: "{semantic query}"
  filter_type: "decision"  # or: remembered, exchange, tool_use, lesson
  n_results: 10

Insights search:

mcp__plugin_engram-mcp_engram__memory_insights
  query: "{topic}"
  insight_type: "decision"  # or: lesson, all
  n_results: 5

Step 4: Present Results

Organize results by relevance and type:

## Search Results: "{query}"

### Most Relevant

**[{type}] {date}**
{content snippet}
*Relevance: {score}*

---

### Decisions Found
| Date | Decision | Rationale |
|------|----------|-----------|
| {date} | {choice} | {why} |

### Lessons Found
| Date | Lesson | Category |
|------|--------|----------|
| {date} | {content} | {category} |

### Related Exchanges
{Summary of relevant past conversations}

---

{N} results found. Refine search with more specific terms if needed.

Step 5: Offer Follow-up Actions

Based on results, suggest:

  • More specific search queries
  • Related topics to explore
  • Actions to take based on findings

Query Crafting Tips

Effective Queries

Engram uses semantic search. Write queries as natural language:

Good:

  • "how did we implement user authentication"
  • "decisions about database schema for orders"
  • "bugs related to async state updates"

Poor:

  • "auth" (too vague)
  • "SELECT * FROM" (not semantic)
  • "file.ts line 42" (not indexed)

Using Filters

Filter by type to narrow results:

FilterBest For
rememberedExplicit saves, preferences
decisionArchitecture choices
lessonBugs, patterns, gotchas
exchangePast conversations
tool_useCode changes, commands run

Exact Matching

Wrap query in quotes for exact phrase matching:

mcp__plugin_engram-mcp_engram__memory_search
  query: "\"PostgreSQL JSONB\""

Examples

User: "What did we decide about caching?"

mcp__plugin_engram-mcp_engram__memory_insights
  query: "caching"
  insight_type: "decision"
  n_results: 5

User: "Find any gotchas about React hooks"

mcp__plugin_engram-mcp_engram__memory_insights
  query: "React hooks"
  insight_type: "lesson"
  n_results: 5

No Results?

If search returns empty:

  1. Broaden the query - Use more general terms
  2. Check memory stats - Run memory_stats to verify index health
  3. Try different filters - Remove type filter for broader results
  4. Sync memory - Run memory_sync if recent work isn't indexed

Score

Total Score

50/100

Based on repository quality metrics

SKILL.md

SKILL.mdファイルが含まれている

+20
LICENSE

ライセンスが設定されている

0/10
説明文

100文字以上の説明がある

0/10
人気

GitHub Stars 100以上

0/15
最近の活動

3ヶ月以内に更新がある

0/10
フォーク

10回以上フォークされている

0/5
Issue管理

オープンIssueが50未満

+5
言語

プログラミング言語が設定されている

+5
タグ

1つ以上のタグが設定されている

0/5

Reviews

💬

Reviews coming soon