Wrapper for the Dify workflow DSL CLI. Create, inspect, validate, edit, and export Dify workflow files through a CLI-Anything harness.
80%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./dify-workflow/agent-harness/cli_anything/dify_workflow/skills/SKILL.mdInstall the upstream Dify workflow CLI first:
python -m pip install "dify-ai-workflow-tools @ git+https://github.com/Akabane71/dify-workflow-cli.git@main"Then install the CLI-Anything harness:
pip install git+https://github.com/HKUDS/CLI-Anything.git#subdirectory=dify-workflow/agent-harnessThe harness forwards to the upstream dify-workflow CLI.
cli-anything-dify-workflow guide
cli-anything-dify-workflow list-node-types
cli-anything-dify-workflow create -o workflow.yaml --mode workflow --template llm
cli-anything-dify-workflow inspect workflow.yaml -j
cli-anything-dify-workflow validate workflow.yaml -j
cli-anything-dify-workflow edit add-node -f workflow.yaml --type code --title "Process"
cli-anything-dify-workflow config set-model -f app.yaml --provider openai --name gpt-4oguidelist-node-typescreateinspectvalidatechecklistedit add-node|remove-node|update-node|add-edge|remove-edge|set-titleconfig set-model|set-prompt|add-variable|set-opening|add-question|add-tool|remove-toolexportimportdifflayout-j / --json-output on upstream commands when available.dify-workflow is not on PATH but the dify_workflow Python package is installed, the wrapper falls back to python -m dify_workflow.cli.HKUDS/CLI-Anything
34f5195
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.