{"id":101481,"plugin_id":"plugins_6af4333b6f008191806d76e5f43ec5f9","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-17T12:11:35.987Z","digest":"e6d5e2368a602d39cf30437ce831647157ae085edf8f2543b5866f8d3144913f","against":null,"payload":{"description":"Add production operating behavior to a workflow. Use for schedules and event triggers, completion or failure notifications, targeted retries, operational logging, and follow-on automation.","included_files":[],"name":"workflow-operations","skill_md_contents":"---\nname: workflow-operations\ndescription: Add production operating behavior to a workflow. Use for schedules and event triggers, completion or failure notifications, targeted retries, operational logging, and follow-on automation.\nlicense: Apache-2.0\ncompatibility: Tines 3B\n---\n\n# Workflow operations\n\nAdd operating behavior from the workflow’s real reliability requirements:\n\n- Choose a schedule or event trigger that matches when the source data becomes ready.\n- Notify only people who can act, and include the workflow, run, outcome, and next action.\n- Retry transient operations with bounded attempts; surface permanent or exhausted failures.\n- Log stable identifiers and decisions needed to trace a run without recording secrets or redundant payloads.\n- Build follow-on automation as another composable workflow when it has an independent trigger, owner, or lifecycle.\n\nFor scheduled work on named volumes, use `workflow-volume-design`. Keep each run bounded, keep input until the change that applied it is published, and verify that pending work drains faster than it arrives. A completed run alone does not establish that the schedule is keeping up.\n\nRun the workflow with representative input after changing its operating behavior.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}