본문으로 건너뛰기
cccskills
무료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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

실행 점수 미검증

설치 방법 보기

포함된 파일(2)

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

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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

CommandDescription
memory-search.sh "<query>"Hybrid search (recommended)
memory-search.sh "<query>" --mode semanticFind conceptually related
memory-search.sh "<query>" --mode termExact term matching
memory-search.sh "<query>" --role userOnly user messages
memory-search.sh "<query>" --role assistantOnly your responses

What to Search Based on User Instruction

User SaysIMMEDIATELY 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/componentmemory-search.sh "<feature>"
References to past workmemory-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

ModeUse When
hybrid (default)General search, best for most cases
semanticLooking for related concepts, different wording
termLooking for exact function/class names
symbolLooking 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/.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

aiskillstore/marketplace4432026년 10월 23일 업데이트

Trigger for: explaining current FAR, DFARS, or agency-supplement text; determining documented acquisition-policy status for an agency and FAR part; comparing codified text, RFO model text, and agency deviations; tracing acquisition rulemaking; finding procurement comment periods; analyzing public comments; refreshing prior policy analysis; or producing an Acquisition Policy Impact Brief. Use published federal sources and supplied policy documents without making legal or procurement-specific applicability determinations. Do not use for clause selection, market research execution, opportunities, pricing, grants, or cooperative agreements.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

aiskillstore/marketplace4432026년 10월 23일 업데이트

Systematic framework for extracting actionable items from documents and organizing them into prioritized, trackable checklists. Use when converting reports, meeting notes, audits, or any document with embedded action items into structured TODO lists.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

aiskillstore/marketplace4432026년 10월 23일 업데이트

Browser automation for AI agents via inference.sh. Navigate web pages, interact with elements using @e refs, take screenshots, record video. Capabilities: web scraping, form filling, clicking, typing, drag-drop, file upload, JavaScript execution. Use for: web automation, data extraction, testing, agent browsing, research. Triggers: browser, web automation, scrape, navigate, click, fill form, screenshot, browse web, playwright, headless browser, web agent, surf internet, record video

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

aiskillstore/marketplace4432026년 10월 23일 업데이트

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

aiskillstore/marketplace4432026년 10월 23일 업데이트

Run AI apps via inference.sh CLI - image generation, video creation, LLMs, search, 3D, Twitter automation. Models: FLUX, Veo, Gemini, Grok, Claude, Seedance, OmniHuman, Tavily, Exa, OpenRouter, and many more. Use when running AI apps, generating images/videos, calling LLMs, web search, or automating Twitter. Triggers: inference.sh, infsh, ai model, run ai, serverless ai, ai api, flux, veo, claude api, image generation, video generation, openrouter, tavily, exa search, twitter api, grok

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

aiskillstore/marketplace4432026년 10월 23일 업데이트

aiskillstore의 스킬 모두 보기

이 스킬의 문제 신고