Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From workato-recipe
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 claudepluginhub grailautomation/claude-plugins --plugin workato-recipeHow this skill is triggered — by the user, by Claude, or both
Slash command
/workato-recipe:workato-recipeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Preprocesses Workato recipe JSON exports (1K–97K lines) into focused view files,
Provides proven architectural patterns for n8n workflows covering webhook processing, HTTP API integration, database operations, AI agents, batch processing, and scheduled tasks. Use when building or designing automations.
Audits Corezoid BPM processes for structural issues, hardcoded values, and optimization opportunities. Use when analyzing or reviewing `.conv.json` process definitions.
Provides proven n8n workflow patterns for webhook processing, HTTP API integration, database operations, AI agents, and scheduled tasks. Use when building, designing, or architecting workflows.
Share bugs, ideas, or general feedback.
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.jsonuv run python "${CLAUDE_SKILL_DIR}/scripts/extract_views.py" "$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):
workato-recipe:recipe-analyzer subagent with the views directory path and questionsummary.json and unified_logic.md to provide detailed analysis| 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 |
${CLAUDE_SKILL_DIR}/references/recipe-schema.md — Recipe JSON structure and datapill syntax${CLAUDE_SKILL_DIR}/references/view-formats.md — View file formats and cross-referencing