免费在 GitHub 公开

ai-maestro-memory-search

PROACTIVELY search conversation history when receiving user instructions. Find previous discussions, decisions, and context BEFORE starting new work. Your memory is valuable - use it.

中文简介正在准备中。当前显示原文说明。

aiskillstore/marketplace

实测评分未实测

查看安装方法

包含的文件（2）

SKILL.md4.1 KB
skill-report.json50.3 KB

SKILL.md（原文）

安装前可以查看交给 AI 代理的指令内容。

AI Maestro Memory Search

CRITICAL: AUTOMATIC BEHAVIOR - READ THIS FIRST

THIS IS NOT OPTIONAL. THIS IS YOUR DEFAULT BEHAVIOR.

When the user gives you ANY instruction, you MUST FIRST search your memory for:

Previous discussions - Have we talked about this before?
Past decisions - What did we decide last time?
Prior context - What does the user expect based on history?
Earlier work - Did we already start on this?

DO NOT:

Start fresh without checking conversation history
Assume this is a new topic without verifying
Skip memory search because "I don't remember discussing this"
Wait for the user to say "remember when we..."

ALWAYS:

Search memory IMMEDIATELY when you receive a task
Search for terms and concepts the user mentions
Check for previous decisions on similar topics
Look for context that informs current work

The Rule: Receive Instruction → Search Memory → Then Proceed

1. User asks you to do something
2. IMMEDIATELY search memory for relevant context
3. NOW you know what was discussed before
4. NOW you can build on previous work, not start over

Available Commands

Command	Description
`memory-search.sh "<query>"`	Hybrid search (recommended)
`memory-search.sh "<query>" --mode semantic`	Find conceptually related
`memory-search.sh "<query>" --mode term`	Exact term matching
`memory-search.sh "<query>" --role user`	Only user messages
`memory-search.sh "<query>" --role assistant`	Only your responses

What to Search Based on User Instruction

User Says	IMMEDIATELY Search
"Continue working on X"	`memory-search.sh "X"`
"Fix the issue we discussed"	`memory-search.sh "issue"`, `memory-search.sh "bug"`
"Use the approach we agreed on"	`memory-search.sh "approach"`, `memory-search.sh "decision"`
"Like we did before"	`memory-search.sh "<topic> implementation"`
Any specific feature/component	`memory-search.sh "<feature>"`
References to past work	`memory-search.sh "<reference>" --mode semantic`

Quick Examples

# User asks to continue previous work
memory-search.sh "authentication"
memory-search.sh "last session"

# User mentions a component we discussed
memory-search.sh "PaymentService" --mode term

# Find what the user previously asked for
memory-search.sh "user request" --role user

# Find your previous solutions
memory-search.sh "implementation" --role assistant

# Conceptual search for related discussions
memory-search.sh "error handling patterns" --mode semantic

Search Modes

Mode	Use When
`hybrid` (default)	General search, best for most cases
`semantic`	Looking for related concepts, different wording
`term`	Looking for exact function/class names
`symbol`	Looking for code symbols mentioned

Why This Matters

Without searching memory first, you will:

Repeat explanations the user already heard
Contradict previous decisions
Miss context that changes the approach
Start over instead of continuing

Memory search takes 1 second. Frustrating the user is much worse.

Combining with Doc Search

For complete context, use BOTH:

# User asks about creating a new feature
memory-search.sh "feature"       # What did we discuss?
doc-search.sh "feature"          # What do docs say?

Error Handling

If no results found, that's valuable information too: "No previous discussions found about X - this appears to be a new topic. Let me search the documentation..."

Then search docs as fallback.

Script not found:

Check PATH: which memory-search.sh
Verify scripts installed: ls -la ~/.local/bin/memory-*.sh
Scripts are installed to ~/.local/bin/ which should be in your PATH

Installation

If commands are not found:

./install-memory-tools.sh

This installs scripts to ~/.local/bin/.

评价

还没有评价。欢迎分享你的使用感受。

无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

同一仓库的技能

academy-guide

免费

Stop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.

中文简介正在准备中。当前显示原文说明。