CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

difyctl

Operate a Dify server through difyctl: find and run any operation, and build, test, publish and change Workflow and Chatflow apps. Use when the task involves difyctl, a Dify server, or Dify apps.

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

90%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.

An exemplary lean overview: executable commands, explicit safety confirmation for destructive operations, and precise conditional pointers to a real reference bundle. The two sub-5 dimensions reflect structure choices rather than defects — run-level validation detail and the second-level build-workflow files live in the bundle instead of the body.

DimensionReasoningScore

Conciseness

Every sentence carries non-obvious information Claude could not know ("Business commands are not built in: the server publishes a catalog of operations", "Ids come from the server and can change"), with zero padding and no explanation of known concepts. Not 4: there is nothing that could be trimmed without losing instruction.

5 / 5

Actionability

Copy-paste-ready commands cover the common discovery cases: `difyctl help --json`, `difyctl help get`, `difyctl help upload file`, `difyctl run console_app chat`, plus the `DIFY_OUTPUT=json` alternative and `<command> --help` equivalence. Not 4: the executable examples fully cover the body's core task (finding and invoking operations).

5 / 5

Workflow Clarity

A numbered discovery sequence with an explicit entry point ("`difyctl help --json`: the map. Start here"), explicit checkpoints for risky operations ("Check effect in help and confirm with the human first", "Also confirm a server operation that shows no effect"), and recovery guidance ("Widen the words when nothing fits"). Not 5: the full run-verify-retry loop and complex-process checklists are deferred to reference files rather than present in the body; not 3: validation for destructive operations is explicit, not missing, so the destructive-cap does not apply.

4 / 5

Progressive Disclosure

The overview points to five real reference files, each with a clear when-to-read condition ("Read [`references/operations.md`] before running any operation"), and no content is inlined that belongs elsewhere. Not 5: the build-workflow subtree is two levels deep from SKILL.md (SKILL.md → build-workflow.md → build-workflow/*.md), violating the one-level-deep ideal even though each hop is well signaled; not 3: all references are clearly signaled and appropriately split.

4 / 5

Total

18

/

20

Passed

Description

92%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.

A strong description: concrete, third-person action list with an explicit 'Use when' trigger clause anchored to distinctive product terms. The only weakness is trigger coverage — capabilities the body supports (plugins, workspace skills) lack corresponding natural trigger phrases.

DimensionReasoningScore

Specificity

"find and run any operation, and build, test, publish and change Workflow and Chatflow apps" lists multiple concrete actions (find, run, build, test, publish, change) with comprehensive coverage framed by "any operation". Not 4: no minor coverage gap — every named action is specific and the "any operation" phrase closes the scope.

5 / 5

Completeness

Explicitly answers what ("Operate a Dify server through difyctl: find and run any operation, and build, test, publish and change Workflow and Chatflow apps") and when ("Use when the task involves difyctl, a Dify server, or Dify apps") — the same pattern as the anchor-5 example. Not 4: the when-clause is explicit and concrete, not merely present or imprecise.

5 / 5

Trigger Term Quality

"difyctl, a Dify server, or Dify apps" plus "Workflow and Chatflow apps" are the natural terms a Dify user would say, giving good keyword coverage. Not 5: a few natural trigger terms for covered capabilities are missing (e.g. plugin installation or workspace skills, which the skill body handles); not 3: multiple relevant natural keywords are present, not just some with common variations missing.

4 / 5

Distinctiveness Conflict Risk

"difyctl", "Dify server", and "Chatflow" are niche-specific terms no other plausible skill would trigger on, giving a clear niche with distinct triggers. Not 4: there is no meaningful overlap risk with closely related skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

langgenius/dify

Path

skills/difyctl/SKILL.md

Reviewed

Table of Contents

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.