aliyun-qwen-generation
Use when generating or reasoning over text with Alibaba Cloud Model Studio Qwen flagship text models (`qwen3-max`, `qwen3.5-plus`, `qwen3.5-flash`, snapshots, and compatible open-source variants). Use when building chat, agent, tool-calling, or long-context text generation workflows on Model Studio.
What this skill does
Category: provider
# Model Studio Qwen Text Generation
## Validation
```bash
mkdir -p output/aliyun-qwen-generation
python -m py_compile skills/ai/text/aliyun-qwen-generation/scripts/prepare_generation_request.py && echo "py_compile_ok" > output/aliyun-qwen-generation/validate.txt
```
Pass criteria: command exits 0 and `output/aliyun-qwen-generation/validate.txt` is generated.
## Output And Evidence
- Save prompt templates, normalized request payloads, and response summaries under `output/aliyun-qwen-generation/`.
- Keep one reproducible request example with model name, region, and key parameters.
Use this skill for general text generation, reasoning, tool-calling, and long-context chat on Alibaba Cloud Model Studio.
## Critical model names
Prefer the current flagship families:
- `qwen3-max`
- `qwen3-max-2026-01-23`
- `qwen3.5-plus`
- `qwen3.5-plus-2026-02-15`
- `qwen3.5-flash`
- `qwen3.5-flash-2026-02-23`
Common related variants listed in the official model catalog:
- `qwen3.5-397b-a17b`
- `qwen3.5-122b-a10b`
- `qwen3.5-35b-a3b`
- `qwen3.5-27b`
## Prerequisites
- Install SDK in a virtual environment:
```bash
python3 -m venv .venv
. .venv/bin/activate
python -m pip install dashscope
```
- Set `DASHSCOPE_API_KEY` in your environment, or add `dashscope_api_key` to `~/.alibabacloud/credentials`.
## Normalized interface (text.generate)
### Request
- `messages` (array<object>, required): standard chat turns.
- `model` (string, optional): default `qwen3.5-plus`.
- `temperature` (number, optional)
- `top_p` (number, optional)
- `max_tokens` (int, optional)
- `enable_thinking` (bool, optional)
- `tools` (array<object>, optional)
- `response_format` (object, optional)
- `stream` (bool, optional)
### Response
- `text` (string): assistant output.
- `finish_reason` (string, optional)
- `usage` (object, optional)
- `raw` (object, optional)
## Quick start (OpenAI-compatible endpoint)
```bash
curl -sS https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions \
-H "Authorization: Bearer $DASHSCOPE_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "qwen3.5-plus",
"messages": [
{"role": "system", "content": "You are a concise assistant."},
{"role": "user", "content": "Summarize why object storage helps media pipelines."}
],
"stream": false
}'
```
## Local helper script
```bash
python skills/ai/text/aliyun-qwen-generation/scripts/prepare_generation_request.py \
--prompt "Draft a concise architecture summary for a media ingestion pipeline." \
--model qwen3.5-plus
```
## Operational guidance
- Use snapshot IDs when reproducibility matters.
- Prefer `qwen3.5-flash` for lower-latency simple tasks and `qwen3-max` for harder multi-step tasks.
- Keep tool schemas minimal and explicit when enabling tool calls.
- For multimodal input, route to dedicated VL or Omni skills unless the task is primarily text-centric.
## Output location
- Default output: `output/aliyun-qwen-generation/requests/`
- Override base dir with `OUTPUT_DIR`.
## References
- `references/sources.md`
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.