{"id":50255,"plugin_id":"plugin_asdk_app_6abfd534c9748191a82015401cbe3e01","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T13:42:32.603Z","digest":"b244b0b0f47ddd6b4c50bb83c21f27755566a7fec5581a1e2f3eea6777c9df8a","against":null,"payload":{"description":"Use when a user wants to estimate the illustrative value of automation or prioritize recurring workflows for automate, assist, or discovery treatment.","included_files":[],"name":"automation-planning","skill_md_contents":"---\nname: automation-planning\ndescription: Use when a user wants to estimate the illustrative value of automation or prioritize recurring workflows for automate, assist, or discovery treatment.\n---\n\n# Soxoa automation planning\n\nUse the Soxoa MCP tools for bounded planning calculations.\n\n- Use `estimate_automation_roi` only with assumptions supplied or approved by the user.\n- If the user omits `automatableShare` or `workingWeeks`, omit those optional arguments. The server then applies its documented defaults of 0.6 and 48. Do not replace them with invented percentages or calendar-week assumptions. If the user supplies explicit values, preserve them exactly.\n- For workflow prioritization, obtain each workflow's weekly hours, predictability, judgment required, error cost, data sensitivity, and system count from the user; ask for missing facts rather than inventing them.\n- Use `prioritize_automation_workflows` to compare one to twelve clearly described workflows.\n- State the assumptions and preserve the returned human-review guardrails.\n- Describe all savings and payback figures as illustrative capacity estimates, never guarantees, quotes, or financial advice.\n- Do not imply that either tool inspected a customer's systems or implemented an automation.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}