workflow-scheduler

Prioritize and schedule eligible workflows under capacity, budget, and fairness constraints.

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/QuyDu/Skills-Orchestrator --skill workflow-scheduler-quydu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-scheduler
Source: https://github.com/QuyDu/Skills-Orchestrator/tree/main/.github/skills/workflow-scheduler
Command: npx skills add https://github.com/QuyDu/Skills-Orchestrator --skill workflow-scheduler-quydu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When multiple eligible workflows compete for limited execution capacity or budget, ad-hoc scheduling leads to starvation, policy violations, and uncontrolled resource consumption. This Skill provides deterministic admission control, prioritization, and throttling so every scheduling decision is fair, auditable, and within declared limits. ## Core Features & Use Cases - Admission Control: Applies capacity, budget, and policy constraints before admitting any workflow into the execution queue. - Fair Prioritization: Computes priority scores from urgency, impact, fairness debt, and starvation risk, then allocates execution slots deterministically. - Auditable Outputs: Publishes scheduler state snapshots as reports/scheduler-state.json and reports/scheduler-state.md for orchestration and telemetry consumers. - Use Case: A platform team needs to prioritize an urgent security remediation workflow while preventing starvation of queued governance tasks and deferring non-critical work when budget thresholds are reached. ## Quick Start Ask the agent to schedule the current backlog of eligible workflows under the defined capacity and budget limits and produce the scheduler state report.

Frequently Asked Questions about workflow-scheduler

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

FAQPage Schema
How do I prioritize multiple workflows competing for limited capacity?

Build a candidate queue from eligible workflows, then compute priority scores using urgency, impact, fairness debt, and starvation risk. Execution slots are allocated deterministically, and deferred workflows receive an explicit reason and next eligibility condition.

How does workflow admission control enforce budget and policy limits?

Admission controls check capacity, budget caps, and policy-engine decisions before any workflow enters the queue. Policy-denied workflows are never admitted, and overriding a denial requires explicit approval.

When should I not use a workflow scheduler?

Do not use it for a single sequential workflow, since there is no contention to resolve. It is designed for cases where multiple eligible workflows compete for limited capacity or budget.

What happens when scheduling inputs are stale or contradictory?

The scheduler fails closed: it preserves the last valid schedule, marks new admission decisions as blocked, and never admits work under unknown capacity or policy conditions.

How is workflow starvation prevented in queue scheduling?

Starvation risk is an explicit input to the priority score alongside fairness debt. Fairness and starvation controls are observable in queue ordering decisions recorded in the scheduler state reports.