{"id":96439,"plugin_id":"plugins_6af5e009db54819185da35c5a7441bc2","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-14T06:08:51.067Z","digest":"e9d55a661fa623a750f73adb01986e4499fc6a648a6e453f65630f5342d0ce89","against":null,"payload":{"description":"Inspect, build, edit, run, repair, and validate Alteryx workflows, macros, and analytic apps, including `.yxmd`, `.yxmc`, and `.yxwz` artifacts. Use for data preparation, reconciliation, compliance reporting, operational analytics, governed calculations, file transformations, joins, filters, summaries, formulas, macro/app interfaces, execution failures, or output validation. Prefer the Alteryx MCP workflow tools and fall back to workflow XML, Designer samples, bundled scripts, and `AlteryxEngineCmd.exe` only when the required MCP capabilities are unavailable.","included_files":[{"relative_path":"references/building-with-fallback.md","size_in_bytes":7287},{"relative_path":"references/building-with-mcp.md","size_in_bytes":2090},{"relative_path":"references/designer-tool-reference.yaml","size_in_bytes":75428},{"relative_path":"references/formula-syntax.md","size_in_bytes":15638},{"relative_path":"references/workflow-xml.md","size_in_bytes":18388},{"relative_path":"scripts/AlteryxDiscoveryUtils.ps1","size_in_bytes":7060},{"relative_path":"scripts/Find-DesignerSampleWorkflows.ps1","size_in_bytes":5834},{"relative_path":"scripts/Get-DesignerVersion.ps1","size_in_bytes":2788},{"relative_path":"scripts/Invoke-AlteryxWorkflow.ps1","size_in_bytes":9322}],"name":"alteryx-designer","skill_md_contents":"---\nname: alteryx-designer\ndescription: Inspect, build, edit, run, repair, and validate Alteryx workflows, macros, and analytic apps, including `.yxmd`, `.yxmc`, and `.yxwz` artifacts. Use for data preparation, reconciliation, compliance reporting, operational analytics, governed calculations, file transformations, joins, filters, summaries, formulas, macro/app interfaces, execution failures, or output validation. Prefer the Alteryx MCP workflow tools and fall back to workflow XML, Designer samples, bundled scripts, and `AlteryxEngineCmd.exe` only when the required MCP capabilities are unavailable.\n---\n\n# Alteryx Designer\n\nUse this skill to build and validate Alteryx workflows locally or in the cloud. The build loop, safety rules, and completion bar are the same everywhere; only the target identifier, tool namespace, and available operations change.\n\n## Select One Execution Path\n\n1. Establish the target, its inputs, expected outputs, and artifact type.\n2. Identify the target's environment from the user's request. If the request is unclear, try in this order:\n   1. Local mode if `alteryx_local__*` or `designer_local__*` tools available\n   2. Cloud mode if `designer__*` tools available\n   3. Local fallback mode ONLY if neither MCP toolsets are available and functional\n3. Read the build-mode specific guidance. Both Local and cloud mode are documented at `references/building-with-mcp.md`. Fallback mode is documented at `references/building-with-fallback.md`.\n\nYou may also use fallback mode for `.yxwz` or custom constructs when MCP does not explicitly support them.\n\n## Mode Contract\n\n| Concern            | Local mode                                 | Cloud mode                   |\n|--------------------|--------------------------------------------|------------------------------|\n| Target identifier  | `file_path` (absolute)                     | `workflow_id`                |\n| Workflow tools     | `alteryx_local__*` / `designer_local__*`   | `designer__*`                |\n| Durable state      | The local `.yxmd` / `.yxmc` / `.yxwz` file | Alteryx One workflow storage |\n| Input/output data  | Direct reference or governed datasets      | Governed datasets only       |\n| MCP server         | `alteryx-local` (Designer 2026.2+)         | `alteryx`                    |\n| Fallback available | Yes — XML and `AlteryxEngineCmd.exe`       | No                           |\n\nClient prefixes vary. Use the exact tool names the active client exposes rather than inventing names.\n\n## Build With Native Designer Tools\n\nCompose workflows from native Designer tools. When the native approach is unclear, use tool discovery and knowledge search, or ask.\n\nUse a code tool (Python, R, or Run Command) ONLY when the requirement cannot be met natively: state the specific gap, get user approval, and scope the code to that gap with native tools on both sides of it.\n\n## Ground The Build Before Building\n\nWhen the request depends on assets or data that may already exist — reusable logic, a canonical dataset, an example of an unsupported tool's XML — use `alteryx-asset-discovery` to find and verify them before designing the workflow. Do not duplicate business logic that already exists.\n\nAlways discover the Designer tools available in the environment before making any modifications.\n\n## Build Loop\n\n1. Decompose the problem into an ordered list of named Designer tools.\n2. Discover configuration evidence for the tools as needed.\n3. Apply a batch of related mutations.\n4. Run the workflow or refresh metadata.\n5. Inspect run messages, get metadata, or sample data as required.\n6. Repair any errors. If there are more mutations required, restart the loop.\n\n## Build Rules\n\n- Do not claim success based only on a mutation. Completion requires a successful run and evidence that relevant outputs satisfy the request.\n- For formulas, read `references/formula-syntax.md`. Validate complex formulas before use when formula validation is available.\n- Never expose or embed credentials, connection strings, DCM payloads, or sensitive values unless the user explicitly provides and approves them.\n\n## Completion And Response\n\nVerify all applicable evidence:\n\n- The workflow is composed of native Designer tools. Any code tool present was approved by the user.\n- The requested workflow structure contains the expected changes.\n- The workflow run succeeded and produced substantive diagnostics.\n- Expected files, databases, metadata, or sampled anchor results were created or updated.\n- The inspected output evidence supports the requested business logic.\n\nSummarize the selected execution path, the target identifier, what changed, the run result, the evidence checked, and any remaining user action."},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}