Author and submit a Narrative workflow from a natural-language intent. Picks the closest example, adapts it to the user's case, walks the YAML against the spec, resolves the data plane, and submits the workflow only after the user has approved the rendered spec.
| Argument | Required / Default | Description |
|---|---|---|
--spec <path> | Optional | Path to a YAML file containing the workflow specification. Skip the drafting phase and use this verbatim. |
--data-plane <id> | Optional | UUID of the data plane to target. Skips data-plane resolution. |
--trigger | Optional | Pass trigger_immediately: true on create — fires one run as soon as the workflow is registered. |
--schedule | Optional | Pass schedule_immediately: true on create — activates the schedule: cron. Requires the spec to contain a schedule: block. |
--tags <a,b,c> | Optional | Comma-separated tags to attach to the workflow. |
--dry-run | Optional | Render and display the full spec, the chosen data plane, and the create-call parameters — but do NOT call narrative_workflows_create. Implies --show-spec. |
--show-spec | Optional | Include the full rendered YAML in the approval preview. Off by default — most users only need the plain-English summary. |
<free-text tail> | Optional | The user's intent (e.g., /create-workflow daily refresh of active_users at midnight UTC). With no arguments and no tail, the skill asks via AskUserQuestion. |
| Prompt | When to use it |
|---|---|
Schedule a daily refresh of dataset 123 | Wrap a recurring materialized-view refresh as a managed, submitted workflow. |
Wrap this NQL as a workflow | Turn a validated query into a repeatable job after approving the rendered spec. |
Build a pipeline that creates an edges view then refreshes it | Compose a multi-step workflow (create → refresh) from a single intent. |
/create-workflow --schedule --tags etl,daily daily refresh of active_users at midnight UTC | Submit a tagged, scheduled workflow straight from a one-line intent, activating the cron on create. |
This skill builds on the skills listed below — each runs as a step in its workflow.
This skill calls tools from the MCP servers listed below — connect them so your agent has the tools the skill needs.