Workflow
brianlovin/agent-config
Workflow orchestration for complex coding tasks. An agent skill from brianlovin/agent-config.
Hands coding work such as codebase questions, bug fixes, refactors and PR reviews to the Qwen Code CLI, driven through acpx instead of scraped terminal sessions.
Install Qwen Code Claw
$ npx skills add QwenLM/qwen-code --skill qwen-code-claw -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install QwenLM/qwen-code qwen-code-claw --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/QwenLM/qwen-code.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.qwen/skills/qwen-code-claw .claude/skills/qwen-code-claw && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "qwen-code-claw" agent skill from https://github.com/QwenLM/qwen-code/tree/main/.qwen/skills/qwen-code-claw into .claude/skills/qwen-code-claw/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qwen-code-claw", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/QwenLM/qwen-code/tree/main/.qwen/skills/qwen-code-clawType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add QwenLM/qwen-code --skill qwen-code-claw -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install QwenLM/qwen-code qwen-code-claw --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/QwenLM/qwen-code.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.qwen/skills/qwen-code-claw .agents/skills/qwen-code-claw && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "qwen-code-claw" agent skill from https://github.com/QwenLM/qwen-code/tree/main/.qwen/skills/qwen-code-claw into .agents/skills/qwen-code-claw/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qwen-code-claw", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add QwenLM/qwen-code --skill qwen-code-claw -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install QwenLM/qwen-code qwen-code-claw --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/QwenLM/qwen-code.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.qwen/skills/qwen-code-claw .cursor/skills/qwen-code-claw && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "qwen-code-claw" agent skill from https://github.com/QwenLM/qwen-code/tree/main/.qwen/skills/qwen-code-claw into .cursor/skills/qwen-code-claw/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qwen-code-claw", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/QwenLM/qwen-code.git --path .qwen/skills/qwen-code-claw--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add QwenLM/qwen-code --skill qwen-code-claw -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install QwenLM/qwen-code qwen-code-claw --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/QwenLM/qwen-code.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.qwen/skills/qwen-code-claw .gemini/skills/qwen-code-claw && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "qwen-code-claw" agent skill from https://github.com/QwenLM/qwen-code/tree/main/.qwen/skills/qwen-code-claw into .gemini/skills/qwen-code-claw/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qwen-code-claw", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install QwenLM/qwen-code qwen-code-clawInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add QwenLM/qwen-code --skill qwen-code-claw -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/QwenLM/qwen-code.git skills-src && mkdir -p .github/skills && cp -r skills-src/.qwen/skills/qwen-code-claw .github/skills/qwen-code-claw && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "qwen-code-claw" agent skill from https://github.com/QwenLM/qwen-code/tree/main/.qwen/skills/qwen-code-claw into .github/skills/qwen-code-claw/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qwen-code-claw", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add QwenLM/qwen-code --skill qwen-code-claw -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install QwenLM/qwen-code qwen-code-claw --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/QwenLM/qwen-code.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.qwen/skills/qwen-code-claw .opencode/skills/qwen-code-claw && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "qwen-code-claw" agent skill from https://github.com/QwenLM/qwen-code/tree/main/.qwen/skills/qwen-code-claw into .opencode/skills/qwen-code-claw/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qwen-code-claw", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
qwen-code-claw- GitHub stars
- 28k
- Token cost
- ~2k tokens
- SKILL.md length
- 607 words
- Files
- 1
- Skills in repo
- 41
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Hands coding work such as codebase questions, bug fixes, refactors and PR reviews to the Qwen Code CLI, driven through acpx instead of scraped terminal sessions.
- Works in 3 steps: Install the acpx skill for full reference → Read the acpx skill reference for every… → For complete CLI reference with all…
- Asking questions about an unfamiliar codebase through a separate Qwen Code session
- SKILL.md covers When to Use This Skill, Install, Authentication and ACPX Integration, plus 5 more sections
- Calls npx and npm; needs BAILIAN_CODING_PLAN_API_KEY and OPENAI_API_KEY
What it does
This skill sets up Qwen Code as a coding agent that your main agent can delegate to. It covers installing the CLI globally with npm, checking the login with `qwen auth status`, and signing in either from a `BAILIAN_CODING_PLAN_API_KEY` environment variable or through the interactive `qwen auth` flow, which the agent should hand back to you when no key exists.
Delegation goes through `acpx`, a client for the Agent Client Protocol, so commands look like `npx acpx@latest qwen "fix the failing tests"` and there is no pseudo-terminal scraping. The skill recommends `--approve-all` to avoid interrupted tasks and sketches a persistent repository assistant that first plans a fix for failing tests, then applies the smallest safe change and reruns them. A global install of Qwen Code is preferred over `npx` for session reuse.
When your agent uses it
- Asking questions about an unfamiliar codebase through a separate Qwen Code session
- Delegating a bug fix or refactor to Qwen Code while your main agent keeps working
- Having Qwen Code review a pull request or generate documentation
- Starting a new project or feature with Qwen Code writing the first version
Example prompts
- “Ask Qwen Code to inspect the failing tests in this repo and propose a fix plan.”
- “Delegate the auth module refactor to Qwen Code and run the tests afterward.”
- “Get a one-shot summary of this repository from Qwen Code.”
Requirements
- npm, to install `@qwen-code/qwen-code` and `acpx`
- A Qwen login or the `BAILIAN_CODING_PLAN_API_KEY` variable
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Install the acpx skill for full reference
- Read the acpx skill reference for every command, flag, and workflow
- For complete CLI reference with all options and examples
What it can do on your machine
Read from SKILL.md and the folder at commit 55ee50d. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npxnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
raw.githubusercontent.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
BAILIAN_CODING_PLAN_API_KEYOPENAI_API_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Qwen Code Claw loads about 2k tokens when it runs. Until then it costs about 38 tokens; SKILL.md has 607 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from QwenLM/qwen-code at commit 55ee50d, republished under its Apache-2.0 licence (© QwenLM). 607 words, ~1,956 tokens.
Download SKILL.mdSave it as
.claude/skills/qwen-code-claw/SKILL.md (or your agent's skills folder).- name
- qwen-code-claw
- description
- Use Qwen Code as a Code Agent for code understanding, project generation, features, bug fixes, refactoring, and various programming tasks
Qwen Code Claw
When to Use This Skill
Use this skill when you need to:
- Understand codebases or ask questions about source code
- Generate new projects or add new features
- Review pull requests in the codebase
- Fix bugs or refactor existing code
- Execute various programming tasks such as code review, testing, documentation generation, etc.
- Collaborate with other tools and agents to complete complex development tasks
Install
npm install -g @qwen-code/qwen-codeFor normal session reuse, prefer a global install over npx.
Authentication
Check if authentication is already configured:
qwen auth statusIf authentication exists, skip this section. If not authenticated, check if the
BAILIAN_CODING_PLAN_API_KEY environment variable exists:
echo $BAILIAN_CODING_PLAN_API_KEYIf BAILIAN_CODING_PLAN_API_KEY exists, authenticate directly:
qwen auth coding-plan --region china --key $BAILIAN_CODING_PLAN_API_KEYIf the environment variable does not exist, interrupt and prompt the user to
authenticate via qwen-oauth or coding-plan:
qwen authOr configure custom API after launching Qwen Code via /auth.
ACPX Integration
You should always use acpx to run Qwen Code over the Agent Client Protocol
(ACP) instead of scraping PTY sessions.
To use acpx:
- Install acpx globally (recommended) or use npx:
npm install -g acpx@latestOr without installing:
npx acpx@latest- Install the acpx skill for full reference:
npx acpx@latest --skill install acpxRead the acpx skill reference for every command, flag, and workflow pattern: See the ACPX Reference section below for details
For complete CLI reference with all options and examples: https://raw.githubusercontent.com/openclaw/acpx/main/docs/CLI.md
From now on, when you need to delegate work to Qwen Code, use acpx instead of
spawning raw terminal sessions. For example:
npx acpx@latest qwen "fix the failing tests"
npx acpx@latest qwen "refactor the auth module"
npx acpx@latest qwen exec "one-shot: summarize this repo"Tip: You should typically use the
--approve-allflag to prevent task interruptions.
Practical Workflows
Persistent Repository Assistant
acpx qwen 'inspect failing tests and propose a fix plan'
acpx qwen 'apply the smallest safe fix and run tests'One-Shot Script Steps
acpx qwen exec 'summarize repo purpose in 3 lines'Parallel Named Streams
acpx qwen -s backend 'fix API pagination bug'
acpx qwen -s docs 'draft changelog entry for release'Queue Follow-ups Without Waiting
acpx qwen 'run full test suite and investigate failures'
acpx qwen --no-wait 'after tests, summarize root causes and next steps'Machine-Readable Output for Orchestration
acpx --format json qwen 'review current branch changes' > events.ndjsonRepository-Wide Review with Permissive Mode
acpx --cwd ~/repos/my-project --approve-all qwen -s pr-123 \
'review PR #123 for regressions and propose minimal patch'Approval Modes
--approve-all: No interactive prompts--approve-reads(default): Auto-approve reads/searches, prompt for writes--deny-all: Deny all permission requests
If every permission request is denied/cancelled and none are approved, acpx
exits with permission denied.
Best Practices
- Use named sessions for organizing different types of development tasks
- Use
--no-waitfor long-running tasks to avoid blocking - Use
--approve-allfor non-interactive batch operations - Use
--format jsonfor automation and script integration - Use
--cwdto manage context across multiple projects
QwenCode Reference
CLI Commands
| Command | Description |
|---|---|
/help | Show available commands |
/clear | Clear conversation history |
/compress | Compress history to save tokens |
/stats | Show session info |
/auth | Configure authentication |
/exit | Exit Qwen Code |
Full reference: docs/users/features/commands.md.
Show full SKILL.md (227 more words)Show less
Configuration
Config files (highest priority first): CLI args > env vars > system > project
(.qwen/settings.json) > user (~/.qwen/settings.json) > defaults. Format:
JSONC with env var interpolation.
Key settings:
| Setting | Description |
|---|---|
model.name | Model to use (e.g. qwen-max) |
tools.approvalMode | plan / default / auto_edit / yolo |
permissions.allow/ask/deny | Tool permission rules |
mcpServers.* | MCP server configurations |
Full reference: docs/users/configuration/settings.md.
Authentication
Supports Alibaba Cloud Coding Plan, OpenAI-compatible API keys, and Qwen OAuth (free tier discontinued 2026-04-15).
Full reference: docs/users/configuration/auth.md.
Model Providers
Configure custom model providers via modelProviders in settings or environment
variables (OPENAI_API_KEY, OPENAI_BASE_URL, OPENAI_MODEL).
Full reference: docs/users/configuration/model-providers.md.
Key Features
- Approval Mode: control tool execution permissions.
See
docs/users/features/approval-mode.md. - MCP: Model Context Protocol server integration.
See
docs/users/features/mcp.md. - Skills: reusable skill system via
/skill. Seedocs/users/features/skills.md. - Sub-agents: delegate tasks to specialized agents.
See
docs/users/features/sub-agents.md. - Sandbox: secure code execution environment.
See
docs/users/features/sandbox.md. - Headless: non-interactive or CI mode.
See
docs/users/features/headless.md.
ACPX Reference
Built-in Agent Registry
Well-known agent names resolve to commands:
qwen→qwen --acp
Command Syntax
# Default (prompt mode, persistent session)
acpx [global options] [prompt text...]
acpx [global options] prompt [options] [prompt text...]
# One-shot execution
acpx [global options] exec [options] [prompt text...]
# Session management
acpx [global options] cancel [-s <name>]
acpx [global options] set-mode <mode> [-s <name>]
acpx [global options] set <key> <value> [-s <name>]
acpx [global options] status [-s <name>]
acpx [global options] sessions [
list | new [--name <name>] | close [name] | show [name] |
history [name] [--limit <count>]
]
acpx [global options] config [show | init]
# With explicit agent
acpx [global options] <agent> [options] [prompt text...]
acpx [global options] <agent> prompt [options] [prompt text...]
acpx [global options] <agent> exec [options] [prompt text...]Note: If prompt text is omitted and stdin is piped,
acpxreads prompt from stdin.
Global Options
--agent <command>: raw ACP agent command fallback.--cwd <directory>: session working directory.--approve-all: auto-approve all requests.--approve-reads: auto-approve reads/searches, prompt for writes.--deny-all: deny all requests.--format <format>: output format, one oftext,json, orquiet.--timeout <seconds>: maximum wait time.--ttl <seconds>: idle TTL for queue owners.--verbose: verbose ACP/debug logs to stderr.
Flags are mutually exclusive where applicable.
© QwenLM, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .qwen/skills/qwen-code-claw of QwenLM/qwen-code.
Open the folder on GitHubat commit 55ee50d
Compare with similar skills
Qwen Code Claw next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Qwen Code Claw this skillQwenLM/qwen-code | 28k | — | ~2k | Automated safety check: Pass | Apache-2.0 | |
| Workflowbrianlovin/agent-config | 377 | 1 repos | ~687 | Automated safety check: Pass | None | |
| Verdaccio Change Implementationverdaccio/verdaccio | 18k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Code ChangesJanDeDobbeleer/oh-my-posh | 24k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Octocode Code Researchbgauryy/octocode | 949 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Auto DevflowHuangPuStar/FenixAgent | 552 | — | ~3k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Verdaccio Change Implementation
verdaccio/verdaccio
A workflow for implementing a Verdaccio bug fix, feature or refactor: pick the release lines, check existing options, edit the owning layer, test and add a changeset.
Code Changes
JanDeDobbeleer/oh-my-posh
Orchestration workflow for any task that ends in code changes: issue analysis, pull request review, feature implementation, bug fixes, refactors, or fleshing out an idea.
Octocode Code Research
bgauryy/octocode
Researches code with evidence: traces callers, imports and cross-repo links, diagnoses failures and reports findings with exact file and line references and a confidence label.
Auto Devflow
HuangPuStar/FenixAgent
A skill your agent uses when starting an issue, bugfix, feature, or refactor that should be driven by multiple coordinated subagents: explore → plan → code → review, with the main agent acting as…
Ship
AgentSystemLabs/core
The single entry point for the AgentSystem engineering pipeline.
More from QwenLM/qwen-code
All 41 skills in this repoAgent Feature Reproduction
QwenLM/qwen-code
Reproduces a feature from Codex or Claude Code in Qwen Code by running the reference agent under capture, reading the traces, then implementing matching behavior.
Qwen Code E2E Testing
QwenLM/qwen-code
Guides end-to-end testing of the Qwen Code CLI in headless mode with real model calls, MCP test servers and inspection of raw API traffic.
Repo Hygiene Scan and Fix
QwenLM/qwen-code
Scheduled CI skill that scans a repository for small, certain docs, test and code hygiene issues and fixes them on one branch with a commit per finding.
Qwen Code Desktop Brand Builder
QwenLM/qwen-code
Builds a rebranded Qwen Code desktop package from the Tauri shell using only a brand id and a logo, with sensible derived defaults.
Qwen Code Memory Leak Debugger
QwenLM/qwen-code
Walks through capturing and comparing V8 heap snapshots to find memory leaks in the Qwen Code Node.js CLI, using tmux and the chrome-devtools CLI.
tmux Real User Testing
QwenLM/qwen-code
Drives Qwen Code in a real tmux session the way a user would and saves a readable step-by-step transcript of each screen for maintainers to review.
Related
Categories
Questions about Qwen Code Claw
What does Qwen Code Claw do?
Hands coding work such as codebase questions, bug fixes, refactors and PR reviews to the Qwen Code CLI, driven through acpx instead of scraped terminal sessions. This skill sets up Qwen Code as a coding agent that your main agent can delegate to. It covers installing the CLI globally with npm, checking the login with `qwen auth status`, and signing in either from a `BAILIAN_CODING_PLAN_API_KEY` environment variable or through the interactive `qwen auth` flow, which the agent should hand back to you when no key exists.
When should I use Qwen Code Claw?
Qwen Code Claw fits situations like: asking questions about an unfamiliar codebase through a separate Qwen Code session; delegating a bug fix or refactor to Qwen Code while your main agent keeps working; having Qwen Code review a pull request or generate documentation; starting a new project or feature with Qwen Code writing the first version.
How do I install Qwen Code Claw in Claude Code?
Run `npx skills add QwenLM/qwen-code --skill qwen-code-claw -a claude-code`. Or copy the skill folder (.qwen/skills/qwen-code-claw in QwenLM/qwen-code) into .claude/skills/qwen-code-claw in your project. Claude Code loads it when a task matches its description.
How do I install Qwen Code Claw in Codex?
Run `npx skills add QwenLM/qwen-code --skill qwen-code-claw -a codex`. Or copy the skill folder (.qwen/skills/qwen-code-claw in QwenLM/qwen-code) into .agents/skills/qwen-code-claw in your project. Codex loads it when a task matches its description.
Can I use Qwen Code Claw in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add QwenLM/qwen-code --skill qwen-code-claw -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/qwen-code-claw, .gemini/skills/qwen-code-claw, .github/skills/qwen-code-claw and .opencode/skills/qwen-code-claw in your project.
What does Qwen Code Claw need to run?
Going by SKILL.md and its folder, Qwen Code Claw needs the command-line tools its instructions call (npx and npm) and credentials named BAILIAN_CODING_PLAN_API_KEY and OPENAI_API_KEY. Our summary lists: npm, to install `@qwen-code/qwen-code` and `acpx`; A Qwen login or the `BAILIAN_CODING_PLAN_API_KEY` variable.
Does Qwen Code Claw access the network?
SKILL.md names 1 domain. As links in the text: raw.githubusercontent.com. This is read from the text; nothing was executed.
Is Qwen Code Claw safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Qwen Code Claw use?
Qwen Code Claw is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Qwen Code Claw use?
About 2k tokens (SKILL.md is roughly 7.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Qwen Code Claw?
Skills that share tags, products or a category with Qwen Code Claw: Workflow (brianlovin/agent-config, 377 stars), Verdaccio Change Implementation (verdaccio/verdaccio, 18k stars), Code Changes (JanDeDobbeleer/oh-my-posh, 24k stars) and Octocode Code Research (bgauryy/octocode, 949 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Qwen Code Claw?
QwenLM (a GitHub organization) maintains it in QwenLM/qwen-code, which has 28,370 GitHub stars. The repository holds 41 skills in this directory. The repository was last updated on October 9, 2026.
Source: QwenLM/qwen-code on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.