{"id":57787,"plugin_id":"plugin_asdk_app_6981ec32565481919b1c5a1627b1e330","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-27T00:14:50.587Z","digest":"df267791891416d8ae616eec227c8da71a5e1606cd88ed6952a9dc4fe1393532","against":null,"payload":{"description":"Run a Norman workflow (month-end close, monthly reconciliation, VAT-return readiness, invoice to payment, client document requests) on Norman's servers, answer the questions it asks, and schedule it to run by itself. Use when the user asks Norman to close a month, reconcile the bank, get ready for the VAT return, or \"do it every month\".","included_files":[],"name":"run-workflow","skill_md_contents":"---\nname: run-workflow\ndescription: Run a Norman workflow (month-end close, monthly reconciliation, VAT-return readiness, invoice to payment, client document requests) on Norman's servers, answer the questions it asks, and schedule it to run by itself. Use when the user asks Norman to close a month, reconcile the bank, get ready for the VAT return, or \"do it every month\".\nversion: 1.0.1\nargument-hint: \"[workflow, e.g. 'close August' or 'VAT return']\"\nmetadata:\n  openclaw:\n    emoji: \"\\U0001F501\"\n    homepage: https://norman.finance\n    requires:\n      mcp:\n        - norman-finance\n---\n\nNorman runs its workflows on its own servers. You start one, relay the user's answers, and report the result. You do not do the steps yourself.\n\n## Step 1: Pick the workflow\n- Call `list_workflows`. Match `$ARGUMENTS` or the user's words to a workflow key:\n  - \"close the month\" → `month-end-close`\n  - \"reconcile\" → `monthly-reconciliation`\n  - \"VAT return\", the German \"UStVA\", the Polish \"JPK_V7\" → `vat-readiness`\n- If a run of that workflow is already active, continue with it (Step 3) instead of starting another.\n- Tell the user which steps it will take (the `steps` of the workflow) and for which period (`defaultScope`, or the month they named).\n\n## Step 2: Start it\n- Call `start_workflow` with the key. Pass `period_start`/`period_end` only if the user named a different period.\n- Say that Norman is now working on it and will stop only if it needs them.\n\n## Step 3: Follow the run\n- Call `get_workflow_run` when the user asks how it is going. Do not poll in a loop.\n- Act on `blockedReason`:\n  - `user_input`: show the question from `blockedDetail`. Send the user's own answer with `answer_workflow_question`. Never answer on their behalf.\n  - `manual_step`: explain the step's instruction. Once the user did it, or wants to skip it, call `complete_workflow_step`.\n  - `source_required`: ask them to connect the bank or source in Norman, then `continue_workflow`.\n  - `step_failed`: say what stopped it (from `blockedDetail`). Offer `continue_workflow` to try again.\n  - `ai_limit` or `chat_limit_reached`: this month's AI messages are used up. The workflow can continue when the messages renew next month.\n\n## Step 4: Report and offer the schedule\n- When `state` is `done` or `done_with_warnings`, summarize each step's `summary` in plain words.\n- If the workflow has no `schedule`, offer to run it by itself: month-end close on day 3, reconciliation on day 5, VAT readiness 5 days before the deadline (`before_vat_deadline` follows the German UStVA only: for a Polish company schedule it on a day of the month before the JPK_V7 is due on the 25th). Only after the user agrees, call `schedule_workflow`.\n- A refusal with code `automation_paid_feature` means automatic runs need a paid plan. Say so; running by hand stays free.\n\nImportant:\n- Start, answer, schedule and stop only when the user asked.\n- Invoice to payment and client document requests send to clients only when the user asked for sending. Confirm before you relay a \"yes, send it\".\n- For \"what did Norman do this week?\", call `get_agent_week` and quote its numbers.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}