scheduler-validation

Validate cron schedules, job configurations, and latest run statuses.

1.5k|222|Updated Jul 4, 2025
One-click install
npx skills add https://github.com/Datus-ai/Datus-agent --skill scheduler-validation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scheduler-validation
Source: https://github.com/Datus-ai/Datus-agent/tree/main/datus/resources/skills/scheduler-validation
Command: npx skills add https://github.com/Datus-ai/Datus-agent --skill scheduler-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually auditing scheduled data engineering jobs for misconfigured cron schedules, incorrect job settings, or unaddressed failed runs is time-consuming and risks missing issues that break downstream data pipelines before their next scheduled execution. This Skill automates read-only validation of all scheduled jobs in a session to catch these issues early.

Core Features & Use Cases

  • Schedule Correctness Checks: Verifies cron expressions match intended schedules (e.g. confirming a "daily" job uses the correct daily cron instead of an hourly one) to avoid unexpected job timing.
  • Configuration Validation: Confirms job settings including SQL paths, connection IDs, and job types match intended deployments to catch misconfigurations before they cause runtime failures.
  • Runtime Status Inspection: Reviews the latest job run status and logs to surface failures without triggering new test runs, letting teams resolve issues before the next scheduled window. Use Case: A data engineering team deploying 30 new scheduled orchestration jobs can use this Skill to automatically validate all jobs post-deployment, catching misconfigured schedules or failed runs that would otherwise delay daily business reporting.

Quick Start

Use the scheduler-validation skill to audit all scheduled jobs in your current scheduler session for configuration errors and failed run history.

Frequently Asked Questions about scheduler-validation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate cron schedules and job configurations without triggering a test run?

You can validate scheduled jobs by performing read-only static verification of cron expressions, configuration fields, and latest run status, ensuring correctness without triggering new test executions.

What is the best way to audit scheduled data engineering jobs for misconfigurations post-deployment?

Auditing scheduled data engineering jobs post-deployment involves verifying that cron schedules, SQL paths, and connection IDs match intended configurations to catch misconfigurations before they cause runtime failures.

Can I check the latest run status and logs of orchestration jobs without executing them?

Yes, runtime status inspection reviews the latest job run status and surfaces failed run logs without triggering new runs, letting teams resolve blocking issues before the next scheduled window.

How do I catch incorrect cron timing in deployed data pipelines before the next scheduled execution?

Schedule correctness checks verify cron expressions match intended frequencies, like confirming a daily job uses a daily cron instead of an hourly one, preventing unexpected job timing in data pipelines.

Does scheduler validation work for read-only auditing across all jobs in an orchestration session?

Yes, read-only static verification applies to orchestration platforms where teams need to audit all deployed scheduled jobs in a session for misconfigurations, incorrect timing, or unaddressed runtime failures.