Menú
Use when configuring, validating, starting, stopping, or inspecting the packaged codex-task-watchdog background task watcher.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Use when requested work should first be converted into a project-scope Riela workflow and then executed through Riela. Applies to workflow-first implementation, review, refactoring, documentation, or maintenance tasks where no existing package workflow exactly fits, and to requests that explicitly say to work through a project-scope workflow.
Use when creating, modifying, reviewing, or validating riela workflow bundles. Applies to step-addressed workflow.json authoring, node payload files, prompt files, built-in node add-ons, cross-workflow transitions, manager/worker routing, and portable workflows under a workflow root.
Use when creating, validating, or running temporary riela workflows from inline JSON or JSON files without installing a project/user-scope workflow bundle. Applies to --workflow-json, --workflow-json-file, embedded prompt-only payloads, temp workflow payload logs, and dry-run smoke checks.
Use when creating, modifying, reviewing, or validating riela workflow bundles. Applies to step-addressed workflow.json authoring, node payload files, prompt files, built-in node add-ons, cross-workflow transitions, manager/worker routing, and portable workflows under a workflow root.
Use when maintaining the riela-packages registry for package updates, release preparation, publishing registry changes, refreshing riela-package.json checksum and integrity digests, validating packaged workflows, updating README package listings, or doing pre-push release checks for packages under packages/*.
Use when maintaining a riela-packages registry for package updates, release preparation, publishing registry changes, refreshing riela-package.json checksum and integrity digests, validating packaged workflows, updating README package listings, or doing pre-push release checks for packages under packages/*.
Basado en la clasificación ocupacional SOC
| name | codex-task-watchdog |
| description | Use when configuring, validating, starting, stopping, or inspecting the packaged codex-task-watchdog background task watcher. |
| user-invocable | true |
Use this skill to run the packaged codex-task-watchdog workflow as a background
task watcher. The event server stays alive, a cron source triggers polling
passes, and each pass claims at most one newly added active task. After a task
completes, the workflow reviews the completed Codex log for reusable lessons,
creates or updates project-scope skills under .agents/skills, reviews those
skill changes, and commits the accepted queue and skill updates.
This is not an OS service registration flow. Do not install systemd units, launchd plists, or login items unless the user explicitly asks for that.
In the project that should own the task queue:
.riela/workflows.riela-events./tasks/list.jsonlThe codex-task-watchdog workflow must be installed or checked out under the workflow
definition directory together with its dependency workflows:
codex-design-and-implement-review-loopcodex-deepdesigncodex-recent-change-quality-loopThe project should allow repository-local skills under .agents/skills; the
watchdog uses that directory for post-task skill extraction.
Create:
.riela-events/sources/codex-task-watchdog-cron.json
.riela-events/bindings/codex-task-watchdog-cron-to-workflow.json
Source example:
{
"id": "codex-task-watchdog-cron",
"kind": "cron",
"schedule": "*/30 * * * * *",
"timezone": "Asia/Tokyo"
}
Binding example:
{
"id": "codex-task-watchdog-cron-to-workflow",
"sourceId": "codex-task-watchdog-cron",
"workflowName": "codex-task-watchdog",
"match": {
"eventType": "cron.tick"
},
"inputMapping": {
"mode": "template",
"template": {
"taskListPath": "./tasks/list.jsonl",
"request": "Run one codex task watchdog polling pass.",
"scheduledAt": "{{event.input.scheduledAt}}",
"sourceId": "{{event.sourceId}}",
"scheduleId": "{{event.input.scheduleId}}",
"timezone": "{{event.input.timezone}}"
},
"mirrorToHumanInput": false
},
"execution": {
"async": true,
"dedupeWindowMs": 30000,
"maxConcurrentPerKey": 1,
"concurrencyKey": "codex-task-watchdog"
}
}
riela workflow validate codex-task-watchdog --workflow-definition-dir .riela/workflows
riela events validate --workflow-definition-dir .riela/workflows --event-root .riela-events
Start the riela event server with nohup from the project directory:
mkdir -p .riela/logs
nohup riela events serve \
--workflow-definition-dir .riela/workflows \
--event-root .riela-events \
> .riela/logs/codex-task-watchdog-events.log 2>&1 &
echo $! > .riela/logs/codex-task-watchdog-events.pid
Inspect:
tail -f .riela/logs/codex-task-watchdog-events.log
riela events list --event-root .riela-events --output json
Stop:
kill "$(cat .riela/logs/codex-task-watchdog-events.pid)"
rm .riela/logs/codex-task-watchdog-events.pid
Use an emitted cron payload when you want to test without waiting for the schedule:
riela events emit codex-task-watchdog-cron \
--workflow-definition-dir .riela/workflows \
--event-root .riela-events \
--event-file payload.json \
--output json