Update to Saleslumen

{
  "description": "Build and run Saleslumen workflows via MCP: create and update structural drafts, publish, activate, and manage executions. Use when the user wants a workflow graph, a version, or a workflow run. Do not use for inbox email, campaigns, or naming a script function or marketplace operation inside the graph.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 442
    }
  ],
  "name": "saleslumen-workflows",
  "skill_md_contents": "---\nname: saleslumen-workflows\ndescription: >-\n  Build and run Saleslumen workflows via MCP: create and update structural\n  drafts, publish, activate, and manage executions. Use when the user wants a\n  workflow graph, a version, or a workflow run. Do not use for inbox email,\n  campaigns, or naming a script function or marketplace operation inside the\n  graph.\n---\n\n# Saleslumen Workflows\n\nUse the Saleslumen MCP connector to define structural graphs and run workflows that already exist. Keep the conversation natural; push workflow JSON and manage executions with tools.\n\n## Concepts\n\nA workflow has metadata and append-only versions. Create seeds the first version. Update appends a draft. Publish makes a version current. Revert copies a past published definition into a new draft.\n\nExecutions pin a version and run asynchronously. Status is a number: `1` ACTIVE, `2` PAUSED, `3` COMPLETED, `4` ERROR, `5` CANCELLED.\n\n`workflows_create` and `workflows_update` accept structural nodes and connections. They reject a node that names a script function or a marketplace operation. Do not put either in the graph. Author those calls in Saleslumen, then start the saved workflow by id.\n\n`agent` and `wait` pause the run. Resume continues at the main-flow successor; it does not re-execute the pause node.\n\n## Workflow\n\n1. Clarify the goal (design, publish, activate, run, resume, cancel, or inspect).\n2. Read with `workflows_list` / `workflows_get` before you change a graph.\n3. Ship a structural draft with create or update, then publish, then activate, then `workflows_start_execution`.\n4. Confirm with the user before publish, activate/deactivate, start/resume/cancel, and delete.\n5. Poll with `workflows_get_execution` or `workflows_list_executions`. Resume only when status is `2`.\n\n## Tools\n\n| Task | Tools |\n| --- | --- |\n| Definitions | `workflows_list`, `workflows_get`, `workflows_create`, `workflows_update`, `workflows_delete` |\n| Versions | `workflows_publish`, `workflows_revert_version`, `workflows_get_history`, `workflows_get_version` |\n| Lifecycle | `workflows_activate`, `workflows_deactivate` |\n| Executions | `workflows_start_execution`, `workflows_resume_execution`, `workflows_cancel_execution`, `workflows_get_execution`, `workflows_list_executions` |\n\n## Guidance\n\n- Default start (no `version_id`) requires Publish then Activate. `version_id` is a preview and may run a draft while inactive.\n- Keep graphs acyclic and include `start` and `end`.\n- Edit Script source with the Apps Script skill. Do not name a script function or a marketplace operation in a workflow node.\n"
}