CtrlK
BlogDocsLog inGet started
Tessl Logo

workflow-creator

Create or update reusable Dynamic Workflow JavaScript files under .qwen/workflows. Use when the user asks to create, save, edit, or reuse a Dynamic Workflow, including requests started from the Web Shell Workflows page.

69

Quality

84%

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

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

A tight, actionable skill body that defers depth appropriately and sequences its workflow with a validation checkpoint. Adding a small end-to-end worked example and an explicit re-verify loop would push it to full marks.

DimensionReasoningScore

Conciseness

Lean, well-organized sections that assume Claude's competence and defer full API detail to the workflow-authoring skill; every line earns its place.

5 / 5

Actionability

Concrete naming rules, a copy-paste meta block, listed sandbox globals, and explicit do/don'ts, but no complete worked end-to-end script example covering a common case.

4 / 5

Workflow Clarity

A clear five-step sequence with an explicit read-back verification checkpoint (step 4), but no fix-and-retry feedback loop for cases where verification fails.

4 / 5

Progressive Disclosure

Under 50 lines with no bundle files, well-organized into Boundary/Workflow/Script contract/Updates sections and a single clearly-signaled one-level external reference (workflow-authoring).

5 / 5

Total

18

/

20

Passed

Description

82%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, specific description with explicit 'what' and 'when' guidance and low conflict risk. The only soft spot is the limited enumeration of concrete actions on the 'what' side.

Suggestions

Broaden the 'what' clause beyond 'create or update' to enumerate the concrete actions (e.g., create, edit, reuse, and remove saved workflows) for fuller capability coverage.

Consider mentioning the .js file extension or 'slash command' in the trigger clause to add a natural synonym users might say.

DimensionReasoningScore

Specificity

Names the domain and concrete file location ('reusable Dynamic Workflow JavaScript files under .qwen/workflows') with two concrete actions (create, update), but the action list is not comprehensive enough for the 4-anchor.

3 / 5

Completeness

Clearly states what it does and gives an explicit 'Use when the user asks to create, save, edit, or reuse a Dynamic Workflow...' trigger clause with concrete phrases.

5 / 5

Trigger Term Quality

Covers natural verbs users would say ('create, save, edit, or reuse a Dynamic Workflow') plus 'Web Shell Workflows page', but omits synonyms and the .js file extension, falling just short of comprehensive.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (Dynamic Workflow .js files exposed as slash commands) with distinct triggers and minimal overlap with other skills.

5 / 5

Total

17

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
QwenLM/qwen-code
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.