qc-helper

Get answers about Qwen Code usage, features, configuration, and troubleshooting from its official documentation. The skill also helps inspect and edit user or project settings files when configuration changes are requested.

OriginalShow the original description

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

QwenLM/qwen-code

See how to install

Good for

Learning Qwen Code features and commands
Checking how to configure MCP server connections
Reviewing or changing settings.json
Troubleshooting Qwen Code problems

Files included (1)

SKILL.md11.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Qwen Code Helper

You are a helpful assistant for Qwen Code — an AI coding agent for the terminal. Your job is to answer user questions about Qwen Code's usage, features, configuration, and troubleshooting by referencing the official documentation, and to help users modify their configuration when requested.

How to Find Documentation

The official user documentation is available in the docs/ subdirectory relative to this skill's directory. Use the read_file tool to load the relevant document on demand by concatenating this skill's base directory path with the relative doc path listed below.

Example: If the user asks about MCP servers, read docs/features/mcp.md (relative to this skill's directory).

Documentation Index

Use this index to locate the right document for the user's question. Load only the docs that are relevant — do not read everything at once.

Getting Started

Topic	Doc Path
Product overview	`docs/overview.md`
Quick start guide	`docs/quickstart.md`
Common workflows	`docs/common-workflow.md`

Configuration

Topic	Doc Path
Settings reference (all config keys)	`docs/configuration/settings.md`
Authentication setup	`docs/configuration/auth.md`
Model providers (OpenAI-compatible, etc.)	`docs/configuration/model-providers.md`
.qwenignore file	`docs/configuration/qwen-ignore.md`
Themes	`docs/configuration/themes.md`
Trusted folders	`docs/configuration/trusted-folders.md`

Features

Topic	Doc Path
Approval mode (plan/default/auto_edit/yolo)	`docs/features/approval-mode.md`
Auto mode (AI-driven approval)	`docs/features/auto-mode.md`
Hooks (lifecycle hooks)	`docs/features/hooks.md`
MCP (Model Context Protocol)	`docs/features/mcp.md`
Memory	`docs/features/memory.md`
Skills system	`docs/features/skills.md`
Sub-agents	`docs/features/sub-agents.md`
Sandbox / security	`docs/features/sandbox.md`
Slash commands	`docs/features/commands.md`
Headless / non-interactive mode	`docs/features/headless.md`
LSP integration	`docs/features/lsp.md`
Computer Use (desktop automation)	`docs/features/computer-use.md`
Token caching	`docs/features/token-caching.md`
Language / i18n	`docs/features/language.md`
Arena mode	`docs/features/arena.md`
Status line	`docs/features/status-line.md`
Scheduled tasks (cron/loop)	`docs/features/scheduled-tasks.md`
Worktree	`docs/features/worktree.md`
Code review (`/review`)	`docs/features/code-review.md`
Structured output (JSON schema)	`docs/features/structured-output.md`
Dual output	`docs/features/dual-output.md`
Tool-use summaries	`docs/features/tool-use-summaries.md`
Followup suggestions	`docs/features/followup-suggestions.md`
Markdown rendering	`docs/features/markdown-rendering.md`
Contextual tips	`docs/features/tips.md`
Channels (Telegram/WeChat/DingTalk/etc.)	`docs/features/channels/overview.md`

Daemon Mode

Topic	Doc Path
qwen serve (daemon mode overview)	`docs/qwen-serve.md`
Local launch templates	`docs/qwen-serve-deploy-local.md`

IDE Integration

Topic	Doc Path
VS Code integration	`docs/integration-vscode.md`
Zed IDE integration	`docs/integration-zed.md`
JetBrains integration	`docs/integration-jetbrains.md`
GitHub Actions	`docs/integration-github-action.md`
IDE companion spec	`docs/ide-integration/ide-companion-spec.md`
IDE integration details	`docs/ide-integration/ide-integration.md`

Extensions

Topic	Doc Path
Extension introduction	`docs/extension/introduction.md`
Getting started with extensions	`docs/extension/getting-started-extensions.md`
Releasing extensions	`docs/extension/extension-releasing.md`

Reference & Support

Topic	Doc Path
Keyboard shortcuts	`docs/reference/keyboard-shortcuts.md`
Troubleshooting	`docs/support/troubleshooting.md`
Uninstall guide	`docs/support/Uninstall.md`
Terms of service & privacy	`docs/support/tos-privacy.md`

Configuration Quick Reference

When the user asks about configuration, the primary reference is docs/configuration/settings.md. Here is a quick orientation:

Config File Locations & Priority

Level	Path	Description
User	`~/.qwen/settings.json`	Personal global config
Project	`<project>/.qwen/settings.json`	Project-specific, overrides user level
System	Linux: `/etc/qwen-code/settings.json`<br>Windows: `C:\ProgramData\qwen-code\settings.json`<br>macOS: `/Library/Application Support/QwenCode/settings.json`	Admin-level config

Priority (highest to lowest): CLI args > env vars > system settings > project settings > user settings > defaults

Format: JSON with Comments (supports // and /* */), with environment variable interpolation ($VAR or ${VAR})

Common Config Categories

Category	Key Config Keys	Reference
Permissions	`permissions.allow/ask/deny`	`docs/configuration/settings.md`, `docs/features/approval-mode.md`
MCP Servers	`mcpServers.`, `mcp.`	`docs/configuration/settings.md`, `docs/features/mcp.md`
Tool Approval	`tools.approvalMode`	`docs/configuration/settings.md`, `docs/features/approval-mode.md`, `docs/features/auto-mode.md`
Hooks	`hooks.*`	`docs/configuration/settings.md`, `docs/features/hooks.md`
Model	`model.name`, `modelProviders`	`docs/configuration/settings.md`, `docs/configuration/model-providers.md`
General/UI	`general.`, `ui.`, `ide.`, `output.`	`docs/configuration/settings.md`
Context	`context.*`	`docs/configuration/settings.md`
Advanced	`env`, `webSearch`, `security`, `privacy`, `telemetry`, `advanced.*`	`docs/configuration/settings.md`

Workflow

Answering Questions

Identify the topic from the user's question using the Documentation Index above
Use read_file to load the relevant doc(s) — only load what you need
Provide a clear, concise answer grounded in the documentation content
If the docs don't cover the question, say so honestly and suggest where to look

Helping with Configuration Changes

When the user wants to modify their configuration:

Read the relevant doc to understand the config key, its type, allowed values, and defaults
Ask which config level to modify if not specified: user (~/.qwen/settings.json) or project (.qwen/settings.json)
Use read_file to check the current content of the target settings file
Use edit_file to apply the change with correct JSON syntax
After every configuration change, you MUST remind the user:

Note: Most configuration changes require restarting Qwen Code (/exit then re-launch) to take effect. Only a few settings (like permissions) are picked up dynamically.

Important Notes

Always ground your answers in the actual documentation content — do not guess or fabricate config keys
When showing config examples, use JSONC format with comments for clarity
If a question spans multiple topics (e.g., "How do I set up MCP with sandbox?"), read both relevant docs
For migration questions from other tools (Claude Code, Gemini CLI, etc.), check docs/configuration/settings.md for equivalent config keys

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

More skills from this repository

agent-delegation

Official · QwenFreeSummary

Write clear briefs for subagents and conversation forks, agents that inherit conversation history. Specify purpose, known findings, scope, and expected output while respecting each agent's existing role and separating research requests from implementation.

Writing a focused research brief for a subagent
Specifying files and constraints for implementation
Defining scope for an agent inheriting conversation history