メニュー
Use paxm as Codex's active and passive memory layer. Trigger for prior decisions, project context, user preferences, memory recall, memory writes, or paxm diagnostics.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/pax-beehive/paxm --skill paxmコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Guide a user through first-time paxm setup for the Codex memory plugin, including binary installation, provider configuration, hook trust, and a real smoke test.
Use paxm as an active agent memory layer. Trigger when the user asks to recall prior context, search or inspect memory, remember working state or a durable fact, debug paxm history/metrics, or when a task would benefit from active memory recall before answering, especially repo, project, preference, architecture, or previous-decision questions.
Configure paxm for the Claude Code plugin.
SOC 職業分類に基づく
SKILL.md を表示中
| name | paxm |
| description | Use paxm as Codex's active and passive memory layer. Trigger for prior decisions, project context, user preferences, memory recall, memory writes, or paxm diagnostics. |
Use paxm as a supporting memory layer, not as a replacement for current source verification. Keep setup, credentials, provider selection, and passive hook policy under the user's control.
Check the local installation only when the task needs memory:
paxm version
paxm config doctor
If the binary is missing, ask the user before running the bundled installer. If the config is missing or invalid, ask whether to start the interactive setup flow. Do not edit paxm YAML by hand.
Use a short, concrete query and a small result limit:
paxm recall --query "repo decision about hook ownership" --limit 3 --json
For a custom config, pass --config before the subcommand. Read scores and
provider metadata, then verify facts that may have changed in the current repo.
If a result exposes a precise lead, do at most two or three focused follow-up
queries rather than running an open-ended search loop.
When the host exposes paxm MCP tools, prefer paxm_recall, paxm_remember,
paxm_history, and paxm_config_doctor over shelling out.
Use STM for task-local working state:
paxm remember --profile stm --text "Working note: ..."
Use LTM only for durable decisions, preferences, recurring fixes, or stable project conventions:
paxm remember --profile ltm --text "Decision: ..."
Never store secrets, API keys, access tokens, raw private logs, or large pasted transcripts. Ask before storing sensitive personal or business information.
Passive Codex hooks are installed by this plugin only after the user completes
the plugin-aware setup flow. Do not run a second paxm setup without the
--integration codex-plugin mode, because that would change hook ownership.
When debugging, use bounded local history and logs:
paxm history --days 7 --json
paxm logs --tail 50
Treat memory as supporting evidence. Current repository files, current tool output, and explicit user instructions take precedence over recalled content.