Delegate repository analysis or coding tasks to Qwen Code without opening its interactive interface. Run within a specified project and time limit, then check the JSON response and exit status before summarizing the result.
Runs Qwen Code headlessly for repository analysis and coding tasks. Use when the user asks to delegate work to Qwen Code or obtain a Qwen-based coding-agent result.
Review the instructions the agent will receive before you install.
command -v qwen. If it is missing, stop and ask the user to install Qwen Code in Code Mate.qwen -p "<prompt>" --output-format json
Pass the prompt as one quoted argument. Parse the JSON result and treat a structured error or nonzero exit as failure. Never start the interactive UI or OAuth flow from the agent task.
If Qwen reports missing login, API key, model, or provider configuration, stop and ask the user to configure Qwen Code in Code Mate. Never request, read, print, or copy credentials.
Use the default restricted approval behavior for analysis. Add bounded turn or tool-call limits for large tasks. Only allow modification tools when the user explicitly requests workspace changes, and never use --yolo: it grants approval without providing a sandbox.
Example: ask Qwen to identify the cause of a failing test without editing, run the command above, then summarize the parsed result within the chosen timeout.
No reviews yet. Tell others what you thought.
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.
Record durable Cherry Studio engineering decisions in Agent Notes. Determine which changes need a note, prepare specifications with verifiable acceptance criteria, and manage approval, implementation, rejection, and replacement while preserving the reasoning behind decisions.
Get answers about Cherry Studio from the installed version’s product information. The skill explains features, settings locations, and shortcuts, provides clickable navigation entries, and helps diagnose connection failures, configuration problems, and runtime errors.
Operate the visible browser pane in a Cherry Studio conversation to navigate pages, click controls, fill forms, capture screenshots, and investigate browser issues. It can work with authenticated websites while checking page state and action outcomes.
Operates native desktop apps through Cherry Studio Computer Use. It reads interface information, types, clicks, and captures windows, using fresh observations to choose actions and verify results within the permissions and capabilities available.
Develop and verify changes in a tracked Cherry Studio Electron instance, a running desktop app. Use real UI behavior, logs, and performance measurements to investigate problems, compare fixes, or test a pull request and report the results.
Run repeatable tests of Cherry Studio’s key workflows with Playwright, which checks application behavior through automated interactions. Collect results on macOS and Windows and produce English reports for release acceptance or development validation.