yaw

Schedule and manage recurring cron-based workflows via the yaw CLI.

2|Updated Mar 2, 2026

Search Tags:#automation #workflow #agent #scheduling #cron #dag #yaw

Ready to run

npx skills add https://github.com/tizee/skills --skill yaw

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: yaw
Source: https://github.com/tizee/skills/tree/main/skills/yaw
Command: npx skills add https://github.com/tizee/skills --skill yaw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Yaw provides a declarative, CLI-driven engine to schedule, orchestrate, and monitor recurring tasks and multi-step workflows, eliminating ad-hoc cron setups and manual run-requests.

Core Features & Use Cases

Declarative workflow definitions with steps, dependencies, and conditions to model complex pipelines.
DAG-based execution with cron and manual triggers, auto-sync to system crontab.
Clear visibility: list, show, status, and logs for workflows; supports headless agent tasks and multi-step workflows.

Quick Start

Create a YAML workflow definition, validate it with yaw validate, and register it with yaw add.

Frequently Asked Questions about yaw

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

FAQPage Schema

How do I schedule recurring tasks with multi-step workflows instead of ad-hoc cron setups?▼

To schedule recurring tasks with multi-step workflows, you define declarative YAML files containing steps and dependencies, then register them via the CLI to auto-sync with the system crontab.

Can I model complex pipelines using DAG-based execution for scheduled commands?▼

Yes, you can model complex pipelines using DAG-based execution by defining conditional steps and dependencies in YAML frontmatter, validating the graph structure, and triggering it via cron or manual commands.

What is the best way to monitor headless agent tasks and scheduled workflows locally?▼

The best way to monitor headless agent tasks and scheduled workflows locally is using CLI commands to list active workflows, show their current status, and inspect execution logs.

Do I need YAML frontmatter to define declarative workflows for task scheduling?▼

Yes, YAML frontmatter with name and description fields is strictly enforced to define declarative workflows, ensuring the CLI can properly validate triggers and manage the task graph structure.

How do I validate triggers and graph structure before registering a DAG-style workflow?▼

You validate triggers and graph structure by running a dedicated CLI validation command against your YAML workflow definition, ensuring dependencies and steps are correctly formed before adding it to the schedule.

Are there limitations when auto-syncing declarative workflows to the system crontab?▼

Limitations apply when auto-syncing declarative workflows to the system crontab, as execution is confined to local environments and requires valid YAML frontmatter to enforce graph structure and triggers.