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.
What this skill does
# Workato Recipe Analyzer 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. ## Workflow ### 1. Resolve the recipe path Determine the `.recipe.json` path from: - The argument (e.g., `/workato-recipe global-context/sources/workato/.../str_rec_001...recipe.json`) - A path mentioned in conversation context - If ambiguous, ask the user or use Glob to search: `global-context/sources/workato/**/*.recipe.json` ### 2. Run preprocessing Resolve `PLUGIN_ROOT` to the root of this plugin before running commands: - In Claude Code, use `CLAUDE_PLUGIN_ROOT` when it is available. - In Codex, infer it from this skill path: `workato-recipe/skills/workato-recipe/SKILL.md` lives two directories below the plugin root. - If neither is obvious, locate the directory containing `workato-recipe/cli.py`. Call the stable plugin CLI rather than internal scripts: ```bash 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. ### 3. Select analysis depth Based on the argument or question: **overview** (default — no depth specified): - Read `summary.json` from the views directory - Report: recipe name, version, trigger, connections, block/provider counts - For callable recipes, show parameters and results **deep** (argument contains "deep", a specific question, or a block reference): - Read `summary.json` and `unified_logic.md` from the views directory. - Answer the question by tracing block numbers, data pills, branches, and variable mutations. - In Claude Code, you may delegate to the `workato-recipe:recipe-analyzer` subagent if it is available. In Codex, analyze inline; Claude subagent definitions are not a Codex plugin interface. ## View Files | 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 - `references/recipe-schema.md` — Recipe JSON structure and datapill syntax - `references/view-formats.md` — View file formats and cross-referencing
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.