{"id":78917,"plugin_id":"plugin_asdk_app_6abfd534c9748191a82015401cbe3e01","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-03T19:07:04.906Z","digest":"bb1bd2e784a25aecbdc725eb0d15efa016e0ea6e2c915aadbd7269e5d31cedca","against":null,"payload":{"description":"Choose an automation pilot, estimate illustrative capacity savings, or turn a supplied workflow into a practical prompt and acceptance plan.","included_files":[],"name":"soxoa-automation-planning","skill_md_contents":"---\nname: soxoa-automation-planning\ndescription: \"Choose an automation pilot, estimate illustrative capacity savings, or turn a supplied workflow into a practical prompt and acceptance plan.\"\n---\n\nUse the connected Soxoa tools at https://soxoa.com/mcp. This public workflow needs no account. If the tools are unavailable, provide the connection/documentation handoff at https://soxoa.com/mcp-guide; a skill installation alone does not connect the service.\n\n\n\n# Plan an automation pilot\n\nStart with the outcome, trigger, actual inputs, current steps, systems and reviewer. Ask for missing facts; do not invent operating costs, process reliability or system capabilities. No account connection is needed.\n\nUse `estimate_automation_roi` with user-supplied or approved assumptions. Omit missing automatableShare and workingWeeks so the server applies its documented defaults of 0.6 and 48. Label savings and payback as illustrative capacity estimates. Use `prioritize_automation_workflows` to compare one to twelve workflows only after obtaining its required facts.\n\nUse `build_workflow_pilot` for a chosen workflow with supplied success checks, risk, sensitivity and review owner. Return its steps, ready-to-use prompt, review gates and acceptance checks as a usable pilot. A proposed tool is a candidate to verify; it is not a connected integration. The generated plan does not deploy or run automation.\n\nIf this is the first visit, gather one real workflow instead of a long company survey. With no process facts, explain the few missing inputs and offer a fill-in outline. On return visits, compare actual supplied outcomes with the saved conversation's acceptance checks, mark missing measurements and revise the next pilot step. There is no server-side saved pilot history, background monitoring or scheduling.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}