workato-recipe/skills/workato-recipe/SKILL.md
Parse and analyze Workato recipe JSON exports. Use when the user asks about a Workato recipe's logic, data flow, field mappings, error handling, or control flow. Also use when the user references a .recipe.json file or asks to debug a Workato integration.
npx skillsauth add grailautomation/claude-plugins workato-recipeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Preprocesses Workato recipe JSON exports (1K–97K lines) into focused view files, stripping ~90–98% of UI/schema bloat to expose the actual recipe logic.
Determine the .recipe.json path from:
/workato-recipe global-context/sources/workato/.../str_rec_001...recipe.json)global-context/sources/workato/**/*.recipe.jsonResolve PLUGIN_ROOT to the root of this plugin before running commands:
CLAUDE_PLUGIN_ROOT when it is available.workato-recipe/skills/workato-recipe/SKILL.md lives two directories below the plugin root.workato-recipe/cli.py.Call the stable plugin CLI rather than internal scripts:
uv run --project "$PLUGIN_ROOT" python "$PLUGIN_ROOT/cli.py" extract --recipe "$RECIPE_PATH"
The script outputs the views directory path to stdout. Views are cached in
.scratch/workato-views/ (invalidated by source mtime or extractor version change).
Use --force to regenerate. Use --all to process all non-archived recipes.
Developer utilities live at the plugin root cli.py entry point. Consumers
should call that stable CLI rather than depending on internal script paths.
Based on the argument or question:
overview (default — no depth specified):
summary.json from the views directorydeep (argument contains "deep", a specific question, or a block reference):
summary.json and unified_logic.md from the views directory.workato-recipe:recipe-analyzer subagent if it is available. In Codex, analyze inline; Claude subagent definitions are not a Codex plugin interface.| File | Content | Size (typical) |
|------|---------|----------------|
| summary.json | Metadata plus structured control-flow and error-handling contract | ~4-8KB |
| unified_logic.md | Single unified document with control flow, mappings, variables, and error handling | ~20-30KB |
references/recipe-schema.md — Recipe JSON structure and datapill syntaxreferences/view-formats.md — View file formats and cross-referencingdatabases
Review implementation plans as a staff software engineer. Use when the user asks for staff engineer feedback, senior engineering review, plan review, architecture review, implementation-plan critique, approval before proceeding, risk review, or feedback on a proposed technical plan.
tools
Use when the user invokes $spec-kit:tasks or /spec-kit:tasks, or asks to generate dependency-ordered tasks from the plan and repo context.
testing
Use when the user invokes $spec-kit:specify or /spec-kit:specify, or asks to create a brownfield-aware feature specification from a natural language description.
tools
Use when the user asks how to use the spec-kit plugin, wants advice on spec-driven development, needs help choosing the next spec-kit workflow step, or asks for review of existing .specify specs, plans, tasks, constitution, or project context.