Workflows
Authors and operates Workflows v2 definitions through the `workflow` CLI: scaffold a...
Install
npx skills add danielmiessler/LifeOS --skill Workflows -g -a claude-code -y- Repository
- danielmiessler/LifeOS19.7k
- Category
- DevOps
- Updated
- 8d ago
- License
- MIT
- Context cost
- Mediumabout 2,497 tokens
- Runs scripts
- Yes, review before use
What it does
Authors and operates Workflows v2 definitions through the `workflow` CLI: scaffold a definition, validate it until clean, graph it, run it locally, put a schedule on it, link workflows with after triggers or workflow steps, and inspect definitions and runs. USE WHEN new workflow, create a workflow, make a workflow, I want a workflow for, workflow for doing this, define a workflow, remind me, set a reminder, follow up on, check back on, scheduled task, recurring job, schedule this, run this every, run it nightly, run workflow, run the workflow, link these workflows, chain workflows, run after, when this finishes run, validate workflow, workflow graph, list workflows, what workflows do I have, did the workflow run, pause workflow. NOT FOR the inventory of everything LifeOS runs, missing or orphaned jobs and acknowledgements (use Workflows.ts in LIFEOS/WORKFLOWS), Cloudflare Worker deploys (Cloudflare), or building a whole skill (CreateSkill).
Workflows
The principal says "I want a new workflow for doing this." This skill turns that into a definition in the definitions home, validated by the workflow CLI, and visible on the Workflows page in Pulse.
The CLI is the source of truth: bun LIFEOS/WORKFLOWS/workflow.ts help --json lists the commands that exist, their usage strings and exit codes. The format and the system doctrine are in LIFEOS/DOCUMENTATION/Workflows/WorkflowsSystem.md. This skill names only commands that help --json lists, plus LIFEOS/WORKFLOWS/engine/schedule-install.ts, which after a hand edit checks the schedule compiles and the dispatcher is loaded, and is not in that catalog.
Ideal State
- Every definition passes
workflow validate(exit 0) before it is reported done, and any deploy, send or pay step declares itsside_effectsand sits under ahumanapproval upstream. - A scheduled or reminder request becomes a
<name>.workflow.yamldefinition with its trigger enabled for the dispatcher, never an issue alone, and shows inworkflow listand Pulse. - Every report states the validate-vs-run distinction that applies:
validatechecks shape,runexecutes for real and may spend money or park on a human gate.
