OpenParable
Skip to content
← Back to skills

Scheduler Validation

Testing & Quality
scheduler-validation

Scheduler Validation is an Agent Skill for testing & quality published in the Datus-ai/Datus-agent repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Scheduler validator driven by ValidationHook — read-only static verification of scheduled jobs (schedule correctness, configuration, runtime context already collected by deterministic hook). Does not trigger test runs.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/Datus-ai/Datus-agent/blob/HEAD/datus/resources/skills/scheduler-validation/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/scheduler-validation, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Scheduler Validation

Driven by ValidationHook.on_end for scheduler runs. The hook passes a SessionTarget containing every SchedulerJobTarget the run delivered. Iterate each target and run the checks below.

Target shape

You receive SessionTarget.targets — loop over SchedulerJobTarget entries. Each carries platform + job_id + optional job_name.

Layer A (the builtin hook) has already confirmed each job exists and is not in a failed status. When the scheduler profile exposes runtime tools, ValidationHook has also deterministically triggered the job once, polled list_job_runs, and attached a scheduler_job_trigger_run precheck before this skill runs. Your job is to verify schedule correctness, configuration, and any runtime context already present.

Core workflow

Read-only static verification. Never trigger a test run from this LLM validator. Runtime triggering is deterministic ValidationHook code, not a model decision.

For every SchedulerJobTarget in the session:

  1. Verify schedule — call get_scheduler_job(job_id) and confirm the schedule expression matches the intended cron (e.g. user asked for "daily" but job submitted 0 * * * *).
  2. Verify configuration — check other fields returned by get_scheduler_job (description, SQL path, job_type, connection id) match the intended setup.
  3. Inspect most recent run, if any — call list_job_runs(job_id, limit=1).
    • No runs yet → advisory note "no runtime history; user-initiated trigger required to verify runtime health". Not a blocking failure.
    • Latest run success → report the success.
    • Latest run failed → call get_run_log(job_id, run_id), surface the error as a blocking finding so the user can fix before the next schedule window hits.
    • Latest run running → advisory (in-progress; can't judge yet).

Validation checklist (per job)

CheckToolWhat to verify
Job existsget_scheduler_jobStatus is active, schedule is correct
Latest run inspectedlist_job_runsLatest run status is success, or no run history is advisory
Run log cleanget_run_logNo errors in output (only check on failure)

Output format

Report a table with these columns:

ColumnDescription
Job IDThe scheduler job identifier
ScheduleCron expression
Latest RunPASS if latest run succeeded, FAIL + error summary if it failed, ADVISORY if absent/running
OverallPASS or FAIL

If the latest run failed, include the error message from get_run_log so the user can diagnose the issue. Never call trigger_scheduler_job.