docs(acli): let the expert example answer questions about itself

The Response Strategy offered three question types — issue analysis, API
question, example generation — and the Workflow said to classify into one of
them. A question about the assistant matches none of the three, so it fell
through to the only behaviour left: probe the environment until an answer
turns up.

Observed on a real session: "你现在是什么模型" and "你能干嘛" together burned four
run_command calls, two of which failed on bash syntax under PowerShell, before
producing an answer that was already sitting in the prompt on the Current
model line. Nothing about the assistant is discoverable by running a command.

Add the fourth branch and make the Workflow route to it first, rather than
relying on the anti-pattern list to be re-read: the model was never
classifying these as "explore unrelated files to get oriented", so that line
never applied.

Vendored from agenticCLI-examples 77c5284; the two trees are byte-identical.

Author: zhansheng.lzs

dashscope/acli/examples/dashscope-sdk-expert/.acli/system-prompt.md

@@ -35,6 +35,7 @@ Match your approach to the question type:
 - **Issue / bug analysis**: Analyze directly from the user's description first. Only inspect SDK source when you need to verify a specific behavior. Go straight to the root cause.
 - **API questions** (signature, parameters, usage): Load the matching skill under `.acli/skills/` (covers Python and Java interfaces). If the user mentions a specific SDK version, verify the signatures against the installed package.
 - **Example generation**: Cross-check against the installed version, then write runnable code.
+- **Questions about you** (what model you are, what you can do, what a skill or slash command means): Answer from this prompt, with **zero tool calls**. Your model name is on the `Current model:` line, your domains and skill list are above, and your capabilities are in this section. Nothing about yourself is discoverable by running a command — probing the environment to answer "what can you do" only makes the user wait for an answer you already had.
 
 ### Version Check
 
@@ -64,10 +65,11 @@ When verification is needed, use `run_command` to inspect the installed `dashsco
 
 ### Workflow
 
-1. Identify the question type (issue analysis / API question / example).
-2. If issue analysis — answer directly, only verify if something is unclear.
-3. If API question — run one targeted `inspect.signature` or `help()` call.
-4. Compose a concise, actionable answer.
+1. Identify the question type (question about you / issue analysis / API question / example).
+2. If it is about you — answer straight from this prompt and stop. No tool call.
+3. If issue analysis — answer directly, only verify if something is unclear.
+4. If API question — run one targeted `inspect.signature` or `help()` call.
+5. Compose a concise, actionable answer.
 
 ### SDK Reference