القائمة
Use when the user types @pensyve, asks for an @-mention workflow, wants mention-style Pensyve memory access in Codex, or asks whether Pensyve supports Codex mentions.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when the user explicitly invokes Pensyve, asks what the agent remembers, wants Codex to recall or store project memory, requests memory health review, or wants memory grounded work.
Pre-refactor context loading -- queries Pensyve memory for past decisions, failures, and patterns related to a refactoring target, then compiles a briefing. Use when starting a refactor to avoid repeating past mistakes.
End-of-session memory capture -- analyzes session for decisions, outcomes, and patterns worth remembering, then stores confirmed items via Pensyve. Use when ending a work session or when the user wants to capture what was learned.
Session start context priming -- loads relevant memories from Pensyve at the beginning of a session to provide continuity across sessions. Use when switching projects or needing historical context.
Long-running multi-session work (research, eval loops, iterative benchmarks) with continuity -- resume prior lessons, capture per-run outcomes, build up stable truths over time. Use for eval/research/benchmark work that spans sessions.
Debug with working memory -- before diagnosing, recall prior root causes and known-good diagnostic procedures; when a root cause is confirmed, capture it immediately. Use whenever debugging a non-trivial failure.
| name | mention-workflow |
| description | Use when the user types @pensyve, asks for an @-mention workflow, wants mention-style Pensyve memory access in Codex, or asks whether Pensyve supports Codex mentions. |
Use this skill to translate mention-style Pensyve requests into the current Codex plugin surfaces.
Codex does not currently expose true @-mention dispatch for local plugin bundles. Treat a literal
@pensyve in user text as explicit user intent, then route the request through the same Pensyve MCP
tools used by $pensyve, /skills, and /pensyve.
Recommended explicit invocations today:
$pensyve what do you remember about this repo?/pensyve recall release workflow decisions@pensyve recall release workflow decisionsThe third form is a compatibility convention: Codex can follow it when the text reaches the model,
but the platform does not provide @pensyve autocomplete, selection, or guaranteed dispatcher
routing yet.
Parse the text after @pensyve.
Route read requests through existing MCP tools.
pensyve_recall(query, entity?, types?, limit?, min_confidence?).pensyve_inspect(entity, limit?).pensyve_status.Route write requests through existing MCP tools.
For durable facts, decisions, preferences, and constraints, call
pensyve_remember(entity, fact, confidence?).
For session outcomes or procedures, ensure an episode exists with
pensyve_episode_start(participants), then call:
pensyve_observe(
episode_id: <working episode_id>,
content: "[proactive/in-flight/tier-1] <observation>",
source_entity: "codex",
about_entity: "<entity>",
content_type: "text"
)
Require confirmation before destructive actions.
pensyve_forget(entity).@pensyve is a native Codex composer primitive.