メニュー
Run privileged Prism Memory ops endpoints using an ops-scoped API key. Use when an agent is explicitly authorized to trigger memory or knowledge processing, backfills, or other maintenance actions against the live Prism deployment.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use this skill when Codex is executing a stored scheduled Prism task prompt through task-runner.
Use this skill when Codex needs to pull the next or current Prism request, inspect request/workflow state, create requests, attach external refs, or create and update execution records through the Prism Agent API.
Use this skill when Codex is asked to create, update, test, or delete Prism workflow hooks that trigger workflow-backed requests from external events or on-demand calls.
Use this skill when Codex is asked to design or create a scheduled Prism task from a user's natural-language request.
Use this skill when Codex is asked to create, update, or reason about Prism request workflows, workflow steps, gates, manifests, or workflow instruction files.
Use this skill when Codex is asked to view or update Prism instance settings such as platform branding, logo, title, workspace label, or site content.
| name | prism-api-ops |
| description | Run privileged Prism Memory ops endpoints using an ops-scoped API key. Use when an agent is explicitly authorized to trigger memory or knowledge processing, backfills, or other maintenance actions against the live Prism deployment. |
Use this skill only with an ops-capable Prism Memory API key and explicit authorization.
This skill triggers existing pipeline operations through the API. It does not reimplement the pipeline inside the agent runtime.
Send:
X-Prism-Api-Key: <ops-key>
POST /ops/memory/runPOST /ops/memory/backfill?days=30&force=truePOST /ops/knowledge/promotePOST /ops/knowledge/validatePOST /ops/knowledge/indexPOST /ops/knowledge/runmemory.run for normal collection, digest, memory, and seed processing.memory.backfill only when explicitly asked to recompute historical windows.knowledge.run after writing new knowledge inbox docs that should become searchable now.operation, exit_code, and any stdout summary.