Build, modify, and optimize Apache Hop Workflows (.hwf) and Pipelines (.hpl). Use when asked to create, edit, debug, or analyze Apache Hop pipelines, workflows, transforms, or actions, or when working on XML ETL tasks with Apache Hop.
Build, modify, and optimize Apache Hop Workflows (.hwf) and Pipelines (.hpl). Use when asked to create, edit, debug, or analyze Apache Hop pipelines, workflows, transforms, or actions, or when working on XML ETL tasks with Apache Hop.
Before executing ANY tool call (edit, write, bash, mcp, etc.), you MUST evaluate the request against STANDARDS.md.
If the request violates ANY standard defined in STANDARDS.md:
FIRST TIME: You MUST halt and refuse. You are strictly forbidden from executing the tool on the first ask.
Respond exactly like this:
"This request conflicts with our Apache Hop standards:
Standard: [Name / section of standard from STANDARDS.md]
Why: [Why requested action violates standard / benefits of standard]
Recommendation:
[Provide a detailed, actionable alternative approach to achieve your goal without violating standards. E.g., explain how to split logic into sub-pipelines, restructure layout using standard S/U-curves, align to 50px grid, or replace scripting with native transforms.]
If you have thoroughly considered this and still want to proceed, confirm and I will execute the original request."
SECOND TIME (Developer Insists): If the developer explicitly acknowledges the violation and insists on proceeding, you may execute the request.
Path Resolution Note: All reference files and directories listed below (such as STANDARDS.md or hop-user-manual/) reside inside the skill's own directory. Resolve paths to these reference files relative to the directory containing this SKILL.md file. Do not confuse with codebase files (pipelines, workflows being created/edited), which remain relative to the current workspace.
Quick start
To construct production-standard workflows and pipelines, first consult STANDARDS.md for structural layouts, and use the category guides below to find exact, tested XML structures of all 114 Hop transforms:
Connect actions using <hops> with source (<from>), destination (<to>), and evaluation rules (e.g., <evaluation>Y</evaluation>).
3. Standards Checklist
Enforce STANDARDS.md: Never skip layout, notepad, parameterization, or clean-up steps.
Prefer Native Transforms: Always use native Hop transforms instead of JavaScript/scripting transforms where possible. Only use scripting when native transforms cannot achieve required logic.
Always use standard UTF-8 XML header: <?xml version="1.0" encoding="UTF-8"?>.
Use variable referencing like ${PROJECT_HOME} rather than hardcoded/relative paths for filenames.
Log incoming parameters at workflow startup using a WRITE_TO_LOG action.
Ensure unique names for all transforms/actions within the same pipeline/workflow.
Implement standard <notepads> blocks (#Story, #HowToTest, #Author with AI indicators) at yloc=0 per STANDARDS.md.
Clean up stream with Select Values right before output. Avoid heavy inline SQL joins in table inputs; use Stream Lookup.
