Qianwen Ops Auth

What it does

When your agent uses it

• : setting up QIANWENAPIKEY
• Troubleshooting 401/auth errors
• Another skill reports missing credentials
• User explicitly invokes this skill by name (e.g

Example prompts

• “/qianwen-ops-auth”

Requirements

• Python 3
• Node.js
• A credential in QIANWEN_API_KEY
• A credential in DASHSCOPE_API_KEY
• Compatibility (from SKILL.md): Requires curl for verification. Cursor: auto-loaded. Claude Code: read this skill's SKILL.md before first use.

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

1. 1NEVER ask the user to provide their API key directly. Do not prompt "please paste your API key" or similar. Do not request the key value…
2. 2Help create a .env file with a placeholder, then instruct the user to fill in their own key
3. 3Or explain how to configure the environment variable: export DASHSCOPE_API_KEY='sk-...' + provide the console URL.
4. 4Only write the actual key value into .env if the user explicitly insists on having the agent do it for them.

What it can do on your machine

Read from SKILL.md and the folder at commit 11b1805. 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:

  • python3
  • curl
  • npx

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  Hosts in commands or code, which the agent is likely to contact:

  • dashscope.aliyuncs.com

  Also links to:

  • platform.qianwenai.com
  • alioth.alicdn.com

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names these keys or tokens, usually read from environment variables:

  • DASHSCOPE_API_KEY
  • QIANWEN_API_KEY
  • AK_SECRET
  • OSS_ACCESS_KEY_ID
  • OSS_ACCESS_KEY_SECRET

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

• Compatibility

  Requires curl for verification. Cursor: auto-loaded. Claude Code: read this skill's SKILL.md before first use.

  From compatibility in the SKILL.md frontmatter.

Context cost

Qianwen Ops Auth loads about 3k tokens when it runs, and up to ~6.6k if it reads all its reference files. Until then it costs about 83 tokens; SKILL.md has 1,179 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~83

When it runs · the whole SKILL.md, loaded when a task matches

~3k

With references · SKILL.md plus every file in references/, read only if the agent opens them

~6.6k

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

• NoteMentions a .env fileSKILL.md:32

  2. **Help create a `.env` file** with a placeholder, then instruct the user to fill in their own key:

• NoteMentions a .env fileSKILL.md:33

  'DASHSCOPE_API_KEY=sk-your-key-here' >> .env`

• NoteMentions a .env fileSKILL.md:36

  *Only** write the actual key value into `.env` if the user **explicitly insists** on having the agent do it for them.

• NoteMentions a .env fileSKILL.md:43

  2. **`.env` file** — in current working directory, then repo root (detected via `.git` or `skills/` directory). Existing

• NoteMentions a .env fileSKILL.md:105

  - **Use environment variables** or `.env` files (and add `.env` to `.gitignore`)

• NoteMentions a .env fileSKILL.md:109

  ### Setting up `.env`

• NoteMentions a .env fileSKILL.md:111

  Create a `.env` file in your project root or current working directory:

• NoteMentions a .env fileSKILL.md:114

  'DASHSCOPE_API_KEY=sk-your-key-here' >> .env

• NoteMentions a .env fileSKILL.md:117

  The script automatically loads `.env` from the current working directory and the project root (detected via `.git` or `s

• NoteMentions a .env fileSKILL.md:122

  .env

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 QianWen-AI/qianwen-ai at commit 11b1805, republished under its Apache-2.0 licence (© QianWen-AI). 1,179 words, ~2,965 tokens.

name

qianwen-ops-auth

description

Configure authentication (API keys, endpoints). TRIGGER when: setting up QIANWEN_API_KEY, troubleshooting 401/auth errors, when another skill reports missing credentials, or user explicitly invokes this skill by name (e.g. use qianwen-ops-auth). DO NOT TRIGGER when: non-auth Qwen tasks, general API usage questions.

compatibility

Requires curl for verification. Cursor: auto-loaded. Claude Code: read this skill's SKILL.md before first use.

echo ${DASHSCOPE_API_KEY:0:6}

echo 'DASHSCOPE_API_KEY=sk-your-key-here' >> .env

.env
.env.local
*.env

curl -sS -X POST "https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions" \
  -H "Authorization: Bearer $DASHSCOPE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"qwen-turbo","messages":[{"role":"user","content":"Hi"}]}'

curl -sS -o /dev/null -w "%{http_code}" \
  -X POST "https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions" \
  -H "Authorization: Bearer $DASHSCOPE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"qwen-turbo","messages":[{"role":"user","content":"hi"}]}'

Your API key failed authentication.

Please confirm:
1. Your key was created at platform.qianwenai.com/home (QianWen console) → re-verify the key
2. My key may be invalid → create a new one at platform.qianwenai.com/home/api-keys

© QianWen-AI, 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

SKILL.md and 4 other files (references) in skills/ops/qianwen-ops-auth of QianWen-AI/qianwen-ai.

• SKILL.md
• cdn/references/qianwen-token-plan-models.md
• references/custom-oss.md
• references/sources.md
• references/tokenplan.md

Open the folder on GitHubat commit 11b1805