cli-anything-dify-workflow

Wrapper for the Dify workflow DSL CLI. Create, inspect, validate, edit, and export Dify workflow files through a CLI-Anything harness.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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.md

Quality

Content

80%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is compact, executable, and well-sectioned, with copy-paste install and usage commands. Its principal gap is the lack of an edit-then-validate feedback loop for destructive DSL edits, and it never explains or exemplifies the checklist, export, import, diff, and layout commands it lists.

Suggestions

Add a validation checkpoint after edit operations, e.g. "After any edit or remove operation, run `cli-anything-dify-workflow validate <file> -j` and fix issues before proceeding."

Merge the duplicate wrapper statements in Usage and Agent Guidance into a single line.

Give one-line examples or purposes for the unexemplified commands (checklist, export, import, diff, layout).

Dimension	Reasoning	Score
Conciseness	The body is lean with no concept over-explanation and assumes Claude's competence, but "The harness forwards to the upstream dify-workflow CLI" and "The harness itself is a wrapper. Real workflow logic is provided by the upstream project" state nearly the same thing twice — a minor trimmable redundancy.	4 / 5
Actionability	Two copy-paste-ready install commands plus seven concrete CLI invocations (create, inspect, validate, edit add-node, config set-model) cover the common cases exactly as the anchor requires.	5 / 5
Workflow Clarity	There is no sequenced workflow and, despite destructive edit operations (remove-node, remove-edge, remove-tool) on local Dify YAML/JSON DSL files, no instruction to run `validate workflow.yaml -j` as a checkpoint after edits — the rubric's destructive/batch-operation cap holds this at 3.	3 / 5
Progressive Disclosure	No bundle files exist and the ~50-line body is cleanly organized into Installation, Usage, Command Groups, and Agent Guidance sections with nothing that belongs in a separate file, satisfying the short-skill exception for a 5.	5 / 5
	Total	17 / 20 Passed

Description

70%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise, concrete, and clearly distinct within the Dify-workflow niche, listing five specific operations. Its main weakness is the absence of any 'Use when...' trigger guidance and missing natural terms such as file extensions, which cap completeness and trigger quality.

Suggestions

Append a trigger clause, e.g. "Use when the user asks to create, inspect, validate, edit, or export Dify workflow DSL files (workflow.yaml, app.yaml)."

Include natural synonyms and file extensions such as ".yaml", ".yml", and "Dify DSL" to improve trigger term coverage.

Mention the import, diff, and layout operations to close the coverage gaps against the body's command list.

Dimension	Reasoning	Score
Specificity	The phrase "Create, inspect, validate, edit, and export Dify workflow files" lists five concrete actions, but omits import, diff, layout, and checklist capabilities documented in the body — minor gaps in coverage rather than the comprehensive listing a 5 requires.	4 / 5
Completeness	The description has a clear 'what' ("Create, inspect, validate, edit, and export Dify workflow files through a CLI-Anything harness") but no 'Use when...' clause or any trigger guidance for when to invoke it, which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Natural terms like "Dify workflow", "workflow files", "validate", and "export" are present, but common variations and file extensions users would say (".yaml", ".yml", "Dify DSL", "workflow YAML") are missing.	4 / 5
Distinctiveness Conflict Risk	"Dify workflow DSL CLI" names a clear niche with distinct triggers; no other plausible skill overlaps with Dify workflow DSL file manipulation, giving minimal conflict risk.	5 / 5
	Total	16 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: HKUDS/CLI-Anything
Path: dify-workflow/agent-harness/cli_anything/dify_workflow/skills/SKILL.md
Commit: 34f5195

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

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.