القائمة
Use when deciding whether a memory belongs in private or team scope, or when validating that team memory paths and keys stay inside the project team-memory directory
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when verifying implementation work and the failure mode is superficial approval, code-reading in place of execution, or over-trusting a passing test suite without trying to break the change
Use when coordinating multi-step work across workers or subagents, especially when research, implementation, and verification should be split while the main agent stays responsible for synthesis and user communication
Use when the task is codebase exploration rather than modification, and you need a fast, read-only search pattern that starts broad when location is unknown, narrows when location is known, and parallelizes independent searches
Use when deciding what information belongs in memory, how to classify it, and what must not be saved because it is derivable from the repo, git history, or current task context
Use when deciding whether shell commands are truly read-only, safe for concurrent execution, and free of path, git, redirection, or command-shape risks that should force a stricter permission path
Use when the real risk is not lack of knowledge but self-justifying shortcuts such as explaining instead of running commands, skipping the hard part first, or deciding on your own that verification would take too long
| name | team-memory-routing |
| description | Use when deciding whether a memory belongs in private or team scope, or when validating that team memory paths and keys stay inside the project team-memory directory |
This skill covers two linked problems:
It is grounded in src/memdir/memoryTypes.ts, src/services/extractMemories/prompts.ts, and src/memdir/teamMemPaths.ts.
Use private memory for:
Use team memory for:
If the information sounds like a personal preference rather than a project rule, do not promote it to team scope.
Ask:
If the answer to the last question is yes, keep it private or do not save it at all.
Never store secrets, credentials, or private user data in shared team memory.
Team memory paths must stay inside the team-memory directory.
Reject:
..If containment cannot be proven, fail closed.
You have applied this skill correctly when shared knowledge is routed to team scope, personal knowledge stays private, and every team-memory write is validated against traversal and symlink escape risks.