# In interactive mode/skills# From command lineqwen --list-skills
Example output:
Available skills: code-review Review code for quality and security debug-assistant Help debug issues systematically doc-writer Generate comprehensive documentation refactor-guide Guide through safe refactoring test-generator Create thorough test suites api-designer Design REST APIs following best practices
# Use slash command/skills code-review# With additional context/skills code-review Focus on the auth module
# Invoke skill with promptqwen --skill code-review --prompt "Review src/auth.ts"# Skill with additional filesqwen --skill doc-writer --prompt "Document @include(src/api.ts)"
The AI can automatically recognize and use skills:
> Help me debug why authentication is failingI'll use the debug-assistant skill to help systematically...[Skill: debug-assistant activated]Let's gather information:1. What error are you seeing?2. When did it start failing?...
# Code ReviewerA specialized skill for reviewing code quality, security, and best practices.## DescriptionReviews code systematically, checking for:- Security vulnerabilities- Performance issues - Code style and conventions- Error handling- Test coverage## InstructionsWhen reviewing code:1. Read the entire file or module first2. Check for security issues (SQL injection, XSS, auth bugs)3. Look for performance problems (N+1 queries, unnecessary loops)4. Verify error handling is comprehensive5. Check test coverage6. Suggest specific improvements with examplesBe thorough but constructive. Prioritize critical issues.## Tools- `read`: Read source files- `grep`: Search for patterns- `glob`: Find files- `web_fetch`: Look up best practices## Examples### Example 1: Security ReviewUser: Review this authentication codeAssistant: I'll review the authentication code for security issues...[reviews code, finds issues]Found 3 security concerns:1. Password comparison uses == instead of constant-time compare2. JWT secret is hardcoded3. No rate limiting on login endpoint[provides specific fixes]## Configuration```json{ "approvalMode": "plan", "temperature": 0.3}
## Skill LocationsSkills can be stored at multiple levels:<Tabs> <Tab title="User-Level"> **Location:** `~/.qwen/skills/` Personal skills available in all projects:
<Tip> Commit project skills to git so your team uses the same workflows.</Tip></Tab><Tab title="Extension-Level">**Location:** Extension packagesSkills provided by installed extensions:
</Tab></Tabs>**Priority:** Project > User > Extension## Creating Skills### Basic SkillCreate `.qwen/skills/my-skill/SKILL.md`:```markdown# My Custom SkillBrief description of what this skill does.## InstructionsDetailed instructions for the AI:1. First, do X2. Then, check Y3. Finally, output ZBe specific and thorough.## Tools- `read`- `write_file`- `bash`
## Skill Features### Template VariablesUse variables in skill instructions:```markdown## InstructionsReview the {{file_path}} file for:- {{focus_area}}- {{additional_checks}}Using {{coding_standard}} as the standard.
# Comprehensive Review## Instructions1. First, run the `code-review` skill2. Then, run the `test-coverage` skill 3. Finally, run the `security-audit` skill4. Synthesize all findings into a report
# Complex Workflow## Phase 1: Planning[Instructions for planning phase]**Deliverable:** Project plan in `plan.md`## Phase 2: Implementation[Instructions for implementation phase]**Deliverable:** Working code in `src/`## Phase 3: Testing[Instructions for testing phase]**Deliverable:** Test suite in `tests/`## Phase 4: Documentation[Instructions for documentation phase]**Deliverable:** Docs in `docs/`
# Parallel Development## Instructions1. Analyze the requirements2. Break into independent modules3. For each module: - Delegate to a specialized subagent - Provide module-specific context - Set appropriate approval mode4. Integrate results5. Run integration tests## Subagent TemplateFor each module, create a subagent with:- Name: module name- Task: implement the module- Tools: read, write_file, edit, bash- Approval: auto-edit
# Guided Refactoring## Instructions1. Ask: "What do you want to refactor?"2. Ask: "What's the goal? (readability, performance, maintainability)"3. Ask: "Any constraints?"4. Analyze the code5. Propose refactoring plan6. Ask: "Approve this plan?"7. Execute the refactoring8. Run tests9. Show summary of changes