qc-helper

Answer any question about Qwen Code usage, features, configuration, and troubleshooting by referencing the official user documentation. Also helps users view or modify their settings.json. Invoke with `/qc-helper` followed by a question, e.g. `/qc-helper how do I configure MCP servers?` or `/qc-helper change approval mode to yolo`.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./packages/core/src/skills/bundled/qc-helper/SKILL.md

Quality

Content

65%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 well-structured, lean documentation-helper whose pointer architecture is sound but undermined in practice: the referenced docs/ bundle is absent, and the config-edit workflow lacks a validation step. Tightening validation and ensuring the referenced files ship with the skill would lift the weaker dimensions.

Suggestions

Add a validation/verification step to the config-change workflow (e.g., re-read the edited settings.json to confirm valid JSONC and the expected key is present) before the restart reminder.

Bundle the referenced docs/ directory (or ship stub/seed files) so the ~40 doc paths in the Documentation Index actually resolve, restoring the progressive-disclosure navigation.

Trim or collapse the inline Configuration Quick Reference to a pointer to docs/configuration/settings.md to reduce duplication and save context tokens.

Dimension	Reasoning	Score
Conciseness	The body is dominated by lean topic/path tables and terse workflow steps with almost no concept-explanation padding; the main trim opportunity is the Configuration Quick Reference, which duplicates content already in docs/configuration/settings.md.	4 / 5
Actionability	Gives concrete, executable guidance — specific read_file/edit_file tool calls, exact doc paths, and a worked MCP example — with only minor gaps such as no sample edit_file payload for a config change; absence of code is acceptable for this instruction-only skill.	4 / 5
Workflow Clarity	Both workflows are clearly numbered and sequenced, but the config-change workflow edits settings.json (JSON document manipulation) with no validate-after-edit checkpoint or feedback loop, so the missing-validation cap at 3 applies.	3 / 5
Progressive Disclosure	The in-skill structure is well organized with a categorized index and one-level-deep, clearly signaled references, but roughly 40 referenced docs/*.md files do not exist in the bundle, so the cross-file navigation the skill depends on is broken.	3 / 5
	Total	14 / 20 Passed

Description

87%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, third-person description that clearly conveys both capability and invocation triggers with concrete example questions. Its only weakness is that the core action ('answer any question') is broad rather than a fully enumerated action list.

Dimension	Reasoning	Score
Specificity	Names the domain (Qwen Code) and several concrete actions — answering questions across usage/features/config/troubleshooting and viewing/modifying settings.json — but 'answer any question' is a broad umbrella action rather than a fully enumerated action set, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly states WHAT (answer Qwen Code questions by referencing docs; view/modify settings.json) and WHEN with concrete trigger phrases ('Invoke with `/qc-helper` followed by a question, e.g.…'), satisfying the 'Use when' equivalent so the cap-at-3 does not apply.	5 / 5
Trigger Term Quality	Provides natural trigger phrases via concrete invocation examples ('how do I configure MCP servers?', 'change approval mode to yolo') plus category keywords, giving good coverage, though synonyms/extensions for the many other topics are not enumerated.	4 / 5
Distinctiveness Conflict Risk	Scoped tightly to one product's documentation and config with distinct triggers (/qc-helper, MCP servers, approval mode, settings.json), giving it a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	18 / 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/qc-helper/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.