xqant daily gushouplus report

自动生成每日21:30发布的87只固收+产品全量表现及赛道前后3名归因分析复盘报告。

Before installing or enabling this skill, verify the following: 1) Authentication: how does Wind access occur? Ask whether the hosting platform supplies a Wind connector or whether you must provide Wind credentials—if credentials are required, they should be declared and scoped narrowly. 2) File access: confirm which workspace files the skill will read (STANDARD/... and MEMORY.md). If those paths map to personal or sensitive notes, restrict or sandbox the skill. 3) Scheduler behavior: the SKILL.md lists a cron job that triggers every 60 seconds and auto-publishes—confirm you want automatic publishing and change frequency to a single daily trigger at 21:30 (or require manual approval). 4) Publishing permissions: verify which chat channel the skill will post to and ensure the skill has only the minimal publishing rights needed. 5) Test in a sandbox: run the skill in a controlled environment (no real credentials, limited dataset) to confirm expected behavior and that it only queries Wind and local reference files you approve. 6) Documentation/owner: the skill has no homepage and unknown source; prefer skills with clear authorship or host-provided connectors. If any of the above are unclear or the platform cannot guarantee a dedicated Wind connector, treat the omission of credential requirements and the cron setup as a red flag and avoid enabling automatic runs.

Type: OpenClaw Skill Name: xqant-daily-gushouplus-report Version: 1.0.0 The skill bundle is a specialized financial analysis tool designed to generate daily performance reports for 87 'Fixed Income Plus' products. The instructions in SKILL.md and the supporting documentation in references/ provide detailed, domain-specific logic for querying the Wind API, performing attribution analysis, and formatting reports. While the cron job frequency is set to 60 seconds (which is unusually high for a daily report), it appears to be a configuration choice or testing artifact rather than a malicious attempt at resource exhaustion. No evidence of data exfiltration, unauthorized execution, or harmful prompt injection was found.