Wind Alice A-Share Short-Term Strategy Report

Problem to solve

A-share short-term analysis often breaks between natural-language requests and deliverable reports. An agent must know when to block, when the task is complete, whether to read downloaded attachments, and how to avoid GBK mojibake on Windows PowerShell and cross-host session contamination. This skill collapses those concerns into one CLI call and an execution contract.

How it works

• Fixed entrypoint: read AGENT.md, run check-conflict, then call aassr.ps1 --prompt ... --no-wait or the Node CLI.
• Blocking completion: the CLI polls tasks/get internally until stdout contains ALICE_A_SHARE_SHORT_TERM_STRATEGY_REPORT_DONE; if not done, the agent must not invent output.
• Delivery boundary: only return agentResult.value as-is; reportFullFile= is for local verification, not user-facing reading.
• Session control: each call starts a new session by default; use --continue-session for follow-up questions; use --session-scope to isolate hosts such as Cursor and Trae.
• Config security: WIND_API_KEY is stored only in ~/.wind-alice/config.env, not from environment variables or skill-local config, reducing key leakage.

Boundaries and caveats

• Requires Node.js 18+ and a valid WIND_API_KEY.
• On Windows, prefer the PowerShell script for UTF-8 handling; if live output looks like GBK mojibake, do not retry repeatedly or manually poll tasks.json.
• --new and --continue-session control taskId and contextId separately; run conflict checks before creating parallel tasks and let the user choose.