一键导入
recall-before-asking
Use before asking the user about infrastructure, preferences, conventions, prior decisions, or past incidents.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Use before asking the user about infrastructure, preferences, conventions, prior decisions, or past incidents.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when waiting for servers, jobs, files, tests, queues, or external processes.
Use when a bounded subtask is summarization, mechanical review, fixture inspection, proposal triage, verification, or boilerplate.
Use when locating where a symbol, function, type, command, or constant is defined or referenced, instead of grep/find/read chains.
Use when tempted to add broad abstractions, future-proofing, or extra product surface beyond the requested change.
Use when evaluating reviewer feedback, review delegates, or suggested code changes.
Use when you need a project fact, document, relationship, investigation note, or prior finding that may already be captured.
| name | recall-before-asking |
| description | Use before asking the user about infrastructure, preferences, conventions, prior decisions, or past incidents. |
| source | bundled |
| triggers | {"user_pattern":["do you remember","what did we decide","which host","what is my preference"]} |
Search Aimee memory before spending a turn asking the user for information that may already be known.
Preferred route:
search_memory / memory_recall, or run aimee memory search <terms>, with the concrete host, repo, service, person, convention, or incident name.This is especially important for homelab endpoints, repo conventions, operator preferences, and recurring operational fixes.