复制安装命令
用 Codex 或 Claude 安装复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它先审查 Skill 页面再帮你安装。
复制前请先查看来源、License 和安全提示。
This is the open-source content repository behind
用 Codex 或 Claude 安装复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它先审查 Skill 页面再帮你安装。
复制前请先查看来源、License 和安全提示。
来源文件:README.md
This is the open-source content repository behind Skill Store. It stores every approved Agent Skill, the records that go with it, and the automated security audits published with each skill.
This repo is a companion to the Skill Store platform, not the place to submit skills. Skills are added through skillstore.io — its review pipeline writes to this repo automatically. Please do not open a pull request here to add a skill; PRs adding skills will be closed. See Contributing a skill below.
The recommended way to install any skill is the skillstore CLI — one command works for both Claude Code and Codex:
npx skillstore add author/skill-name
For example:
npx skillstore add aiskillstore/code-review
It downloads the skill and drops it into the right skills/ directory for your tool. Claude Code auto-discovers it; for Codex, restart the session.
Prefer to do it by hand, or installing via Claude Web? See the full Installation Guides for every method (CLI, manual, and ZIP upload) and the scope directories (~/.agents/skills/, .claude/skills/, ~/.claude/skills/, .codex/skills/, …).
Submit through the platform — not through a pull request:
SKILL.md.SKILL.md — the skill definition (required, per the Agent Skills spec)LICENSE (recommended)Every submission is scanned automatically before it can be published. The audit flags things like:
eval, exec, raw system commands)Security analysis is report-only: findings inform maintainers and users, but a risk result does not automatically block an otherwise approved skill from being published. See our Security Trust Center for the methodology, limitations, and risk-level definitions.
Live Security Passport example:
.
├── skills/ # Approved, published skills (one folder each, with SKILL.md)
├── pending/ # Submissions awaiting review
├── packages/
│ ├── cli/ # The `skillstore` CLI (npx skillstore add …)
│ └── skillstore/
├── schemas/ # JSON schemas for skill records
├── scripts/ # Maintenance & scoring scripts
└── .github/workflows/ # Submission, audit, and sync automation
The contents of this repo are maintained by Skill Store's automated pipeline. Manual changes are limited to maintainers.
The marketplace catalog is MIT-licensed. Individual skills carry their own licenses — check each skill's LICENSE file.
name: ai-maestro-memory-search
description: PROACTIVELY search conversation history when receiving user instructions. Find previous discussions, decisions, and context BEFORE starting new work. Your memory is valuable - use it.
allowed-tools: BashTHIS IS NOT OPTIONAL. THIS IS YOUR DEFAULT BEHAVIOR.
When the user gives you ANY instruction, you MUST FIRST search your memory for:
DO NOT:
ALWAYS:
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
| 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 |
| 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 |
# 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
| 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 |
Without searching memory first, you will:
Memory search takes 1 second. Frustrating the user is much worse.
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?
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:
which memory-search.shls -la ~/.local/bin/memory-*.sh~/.local/bin/ which should be in your PATHIf commands are not found:
./install-memory-tools.sh
This installs scripts to ~/.local/bin/.
评论 (0)
暂无评论,成为第一个评论者吧!