Menu
Use this skill when Codex is executing a stored scheduled Prism task prompt through task-runner.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
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.
Use this skill when Codex is asked to create, update, install, or manage custom Prism/Codex skills for an instance.
| name | prism-scheduled-task-runner |
| description | Use this skill when Codex is executing a stored scheduled Prism task prompt through task-runner. |
You are running as a scheduled task. Execute the stored prompt directly and return a concise run summary.
Scheduled execution rules:
metadata.outputConfig.outputDestinations is present, return the exact content that should be delivered. The task-runner handles adapter delivery after Codex returns.Useful environment variables may include:
PRISM_API_BASEPRISM_API_KEYPRISM_API_READ_KEYPRISM_AGENT_API_BASE_URLPRISM_AGENT_SERVICE_TOKENAPP_API_BASE_URLAPP_API_SERVICE_TOKENOUTPUT_ADAPTER_BASE_URLOUTPUT_ADAPTER_TOKENIn deployed Prism instances, Codex Runtime usually receives APP_API_BASE_URL and APP_API_SERVICE_TOKEN, then exposes them to Codex as PRISM_AGENT_API_BASE_URL and PRISM_AGENT_SERVICE_TOKEN. If the PRISM_* names are missing, check the APP_* names before concluding the site API is unavailable.
If the stored task has metadata.outputConfig.outputDestinations, do not call the adapter directly. Return the final message body and let task-runner deliver it.
If the prompt explicitly asks you to send a one-off message through Discord now, first resolve the channel from the adapter:
curl -fsSL \
-H "X-Adapter-Token: $OUTPUT_ADAPTER_TOKEN" \
"$OUTPUT_ADAPTER_BASE_URL/destinations"
Then send to the resolved destination id:
curl -fsSL \
-X POST \
-H "content-type: application/json" \
-H "X-Adapter-Token: $OUTPUT_ADAPTER_TOKEN" \
"$OUTPUT_ADAPTER_BASE_URL/messages" \
-d '{"destinationId":"<channel-id>","content":"Test message"}'
If OUTPUT_ADAPTER_TOKEN is missing, report that direct adapter delivery is not wired into Codex Runtime. Do not use APP_API_SERVICE_TOKEN or PRISM_AGENT_SERVICE_TOKEN against adapter /messages.
For Prism Memory reads, use:
curl -fsSL \
-H "X-Prism-Api-Key: ${PRISM_API_READ_KEY:-$PRISM_API_KEY}" \
"$PRISM_API_BASE/memory/latest"
For Prism Knowledge search, use:
curl -fsSL \
-H "X-Prism-Api-Key: ${PRISM_API_READ_KEY:-$PRISM_API_KEY}" \
"$PRISM_API_BASE/knowledge/search?q=QUERY"
Return only the scheduled task result summary.