extension-creator

Create, scaffold, customize, validate, and locally test Qwen Code extensions. Use when the user wants a new Qwen Code extension, needs help choosing an extension template, wants to add QWEN.md context, commands, skills, agents, MCP servers, settings, hooks, channels, or LSP servers, or asks how to link and test an extension locally. Invoke with `/extension-creator` followed by an extension path and optional template name.

Quality

94%

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

Quality

Content

88%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 thorough, highly actionable skill with excellent workflow sequencing and validation checkpoints for a security-sensitive task. The main weaknesses are repeated security mantras across sections and a large inlined reference catalog that could be split out for better progressive disclosure.

Suggestions

Consolidate the repeated path-traversal / untrusted-content rules (absolute paths, '..' traversal, '$'-prefixed env vars) into one stated rule in Extension Shape and reference it from Local Test Flow and Before Handoff to trim repetition.

Move the detailed Extension Shape field catalog into a references/ file (e.g. EXTENSION_SHAPE.md) and keep a short summary inline with a clearly signaled link, improving progressive disclosure for the ~350-line body.

Extract the Local Test Flow audit checklist into a concise bullet list at the top of that section so the per-field details read as a reference rather than narrative prose.

Dimension	Reasoning	Score
Conciseness	The body is dense and mostly efficient with copy-paste commands, but the same path-traversal and untrusted-content mantras (reject absolute paths, '..' traversal, '$'-prefixed env vars) recur across Extension Shape, Local Test Flow, and Before Handoff, adding tokens that could be consolidated.	4 / 5
Actionability	Fully executable guidance throughout: concrete commands (`qwen extensions new`, `printf 'y\n' \| qwen extensions link`, `npm install --ignore-scripts`, `npm run build`, `node -e "JSON.parse(...)"`) and concrete field examples cover the common cases copy-paste ready.	5 / 5
Workflow Clarity	Clear sequenced workflow with explicit validation checkpoints and feedback loops ('If any command fails, stop and report', 'fix the issue and re-check before proceeding'), a Linking Approval Procedure with approval gates, and a Before Handoff checklist for a complex, security-sensitive process.	5 / 5
Progressive Disclosure	Well-organized into clearly signaled sections (Workflow, Template Selection, Extension Shape, Local Test Flow, After Linking, Iterating, Before Handoff) with easy header navigation, but the long inlined Extension Shape field reference (~40 lines of catalog) could live in a separate file given the body is ~350 lines.	4 / 5
	Total	18 / 20 Passed

Description

100%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 exemplary: it states concrete actions, provides a rich 'Use when' trigger clause enumerating natural user requests, names the niche clearly, and includes invocation guidance. No vague fluff or over-claims are present.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Create, scaffold, customize, validate, and locally test Qwen Code extensions') plus a comprehensive enumeration of capability areas, matching the comprehensive-coverage anchor.	5 / 5
Completeness	Explicitly answers both 'what' (create/scaffold/customize/validate/test extensions) and 'when' (a detailed 'Use when the user wants...' clause with concrete trigger phrases), plus an invocation hint.	5 / 5
Trigger Term Quality	Covers natural user phrasing ('wants a new Qwen Code extension', 'extension template', 'link and test an extension locally') alongside the full component vocabulary (QWEN.md, commands, skills, agents, MCP servers, settings, hooks, channels, LSP servers), with synonyms and concrete terms.	5 / 5
Distinctiveness Conflict Risk	Scoped to a clear niche (Qwen Code extension creation) with distinct, specific triggers, minimizing overlap with other skills.	5 / 5
	Total	20 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: QwenLM/qwen-code
Path: packages/core/src/skills/bundled/extension-creator/SKILL.md
Commit: 054eabb

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.