From qwen-stack
Manage the qwen-stack supervisor's session-default extension list — show current value with source priority, set a new comma-separated list, set explicit-empty (suppresses CLI defaults), or clear (CLI defaults apply). Operates on the `default_extensions` field in `~/.qwen-coprocessor-stack/config.json` and hot-reloads in the running supervisor without restart. Use when the user types `/qwen-stack:defaults ...`.
How this skill is triggered — by the user, by Claude, or both
Slash command
/qwen-stack:defaults list | set <a,b,c> | set --none | clearlist | set <a,b,c> | set --none | clearThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Lifecycle for the supervisor's **session-default extension list** — the base set every spawn starts with when the orchestrator doesn't specify `opts.extensions.only`.
Lifecycle for the supervisor's session-default extension list — the base set every spawn starts with when the orchestrator doesn't specify opts.extensions.only.
QWEN_DEFAULT_EXTENSIONS env var — comma list. Overrides the file. Tell the user to edit shell rc instead of the file if this is set.~/.qwen-coprocessor-stack/config.json default_extensions: ["a", "b"] — the file you read/write here."leave-defaults" sentinel. The wrapper drops --extensions; CLI defaults from extension-enablement.json apply.Parse the first positional arg as the subcommand. If absent or list, run list. Otherwise dispatch on set or clear.
$QWEN_DEFAULT_EXTENSIONS env (echo "${QWEN_DEFAULT_EXTENSIONS:-}"). If non-empty, the env wins.~/.qwen-coprocessor-stack/config.json if present and look for default_extensions.(QWEN_DEFAULT_EXTENSIONS env), (config.json), or (unset → CLI defaults apply).Args:
<comma-list> — comma-separated extension names, kebab-case, no spaces required (whitespace is trimmed). Example: serena,context7,web-fetch.--none flag in lieu of a list — explicitly empty set (renders as --extensions none at spawn time, suppresses all CLI defaults). Reserve no-args as an error.Steps:
QWEN_DEFAULT_EXTENSIONS env is set. It would silently override the file edit. Tell the user to either unset QWEN_DEFAULT_EXTENSIONS in their shell or edit it there directly.[a-z0-9_-].qwen_extensions MCP tool, build a Set of installed names. For each name in the requested list, check membership. If any are unknown, abort with the same error shape as ExtensionResolutionError: unknown extension(s): X, Y. List the installed names so the user can correct.~/.qwen-coprocessor-stack/config.json (treat as {} if missing). Validate JSON shape.default_extensions to the validated list (or [] for --none). Preserve other fields (e.g., backends).mkdir -p ~/.qwen-coprocessor-stack, write back with 2-space indent.qwen_reload_extensions MCP tool to refresh the supervisor's installed-extensions cache (defensive — operator may have edited extensions on disk recently).list would, plus a one-liner about drain semantics: "applies to new spawns; running sessions keep their current loadout (RDR-001 §Q3)".QWEN_DEFAULT_EXTENSIONS env is set (same reasoning).default_extensions is absent, say "already unset" and stop.null or [] — actually delete). Preserve other fields. Write back.qwen_extensions returns [] (no installed extensions): allow set --none and clear. Reject set <list> with "no extensions installed on the supervisor host; run qwen extensions install <source> first."set and clear.list: 2-3 lines max — active value, source, optional override-note.npx claudepluginhub hellblazer/qwen-coprocessor-stack --plugin qwen-stackCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.