القائمة
Before answering a substantive question, quietly check whether the user has already resolved this question in the past.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
List the agent's current skills, memory files, plugins, subagents, hooks, and a settings summary plus dashboard URLs. The user-facing discovery path for everything the operator can edit.
List the Claude Code plugins currently enabled for the agent, read straight from settings.json.
Weekly self-audit playback. Surface patterns from the user's past week that they probably cannot see themselves.
Find commitments the user made in the last two weeks and did not follow through on. A promises audit.
Discover recurring behaviors from memory and offer to formalize them as scheduled jobs.
Show how the user's thinking on a specific topic has evolved over time. A chronological narrative with turning-point callouts.
| name | echo |
| x-phantom-source | built-in |
| description | Before answering a substantive question, quietly check whether the user has already resolved this question in the past. |
| when_to_use | Use when the user asks a substantive question that might have been asked and resolved before. Substantive questions are things like "how should I do X", "what is the right way to Y", "which approach is better", "what did we decide about Z". Do NOT fire on greetings, small talk, status checks, or operational queries like "what time is it" or "are you online". Before deriving a new answer, run a memory similarity check. If a strong prior match exists, surface it inline and ask whether anything has changed. |
| allowed-tools | ["mcp__phantom-reflective__phantom_memory_search"] |
| context | inline |
Respect the user's past thinking. Before deriving a new answer to a substantive question, check whether the user already resolved this question weeks or months ago. If yes, surface the prior answer inline and ask whether anything has changed. If no, proceed to answer normally without mentioning that you looked.
The user should feel like you remember what they already decided, not like you are doing paperwork.
Determine whether the question is substantive. Skip if:
Proceed if:
Success criteria: you have a yes or no on whether to run the echo check. If no, do not call the search tool at all.
Call mcp__phantom-reflective__phantom_memory_search with query: "<the user's question in your own words>", memory_type: "all", limit: 5. The query should be a restatement of the semantic intent, not a literal copy of the user's words.
Success criteria: you have a list of 0-5 hits with similarity scores.
Examine the top hit. It is a strong match if all of these hold:
If the top hit is NOT a strong match, proceed to answer the question normally from scratch. Do not mention the echo check to the user.
Success criteria: you have a clear yes or no on the match.
If there is a strong match, respond BEFORE deriving a new answer:
You asked something very similar on [date] and you landed on [paraphrase of the prior conclusion]. Has anything changed since then, or is that still your view?
Wait for the user's response.
If the user says "no, things are different now" or explains what changed, proceed to derive a new answer informed by the new context.
If the user says "yes, that is still my view", acknowledge and ask what they want to do with that. Sometimes they just needed the reminder.
Success criteria: the user is aware of their prior thinking, and you have their explicit signal on whether to rebuild from scratch or honor the prior answer.
