OpenClaw, stock analysis skill, AI stock copilot, China A-shares, Hong Kong stocks, US stocks, quantitative analysis, fundamental analysis, technical analysis, sentiment analysis, industry radar, morning evening brief, watchlist, portfolio monitoring, QVeris API, THS iFinD, Caidazi, Alpha Vantage, Finnhub, X sentiment, investment research assistant
Fundamentals path prioritizes THS financial statements endpoints, and always calls THS company basics for profile backfill:
revenue
netProfit
totalAssets
totalLiabilities
operatingCashflow
industry
mainBusiness
tags
Output Modes
markdown
(default): human-readable report
json
machine-readable merged payload
chat
segmented chat-friendly output for messaging apps
summary-first
compact output style via
--summary-only
Preference & Event Options
Preference flags:
--horizon short|mid|long
--risk low|mid|high
--style value|balanced|growth|trading
--actionable
(include execution-oriented rules)
--skip-questionnaire
(force analysis without preference Q&A)
Event radar flags:
--event-window-days 7|14|30
--event-universe global|same_market
--event-view timeline|theme
Dynamic Evolution
Runtime learning state is stored in
.evolution/tool-evolution.json
.
One successful execution can update tool parameter templates.
Evolution stores
param_templates
and
sample_successful_params
for reuse.
Evolution does not decide tool priority; tool priority is controlled by
tool-chains.json
.
Use
--no-evolution
to disable loading/saving runtime learning state.
Safety and Disclosure
Uses only
QVERIS_API_KEY
.
Calls only QVeris APIs over HTTPS.
full_content_file_url
fetching is kept enabled for data completeness, but only HTTPS URLs under
qveris.ai
are allowed.
Does not store API keys in logs, reports, or evolution state.
Runtime persistence is limited to
.evolution/tool-evolution.json
(metadata + parameter templates only).
Watchlist state is stored at
config/watchlist.json
(bootstrap from
config/watchlist.example.json
).
OpenClaw scheduled tasks: see
config/openclaw-cron.example.json
. Create jobs with the official format (
schedule.kind
,
payload.kind
,
sessionTarget
, etc.) via
openclaw cron add
or the Gateway cron tool; do not paste or merge the example JSON into
~/.openclaw/cron/jobs.json
(schema mismatch can cause Gateway parse failure or crash). Set
delivery.channel
and
delivery.to
for your channel (e.g. feishu).
External source URLs remain hidden by default; only shown when
--include-source-urls
is explicitly enabled.
No package installation or arbitrary command execution is performed by this skill script.
Research-only output. Not investment advice.
Single Stock Analysis Guide
When analyzing
analyze
output, act as a senior buy-side analyst and deliver a
professional but not overlong
report.
Required Output (7 Sections)
Data Snapshot (required)
Start with a compact metrics table built from
data
fields.
Include at least: price/change, marketCap, PE/PB, profitMargin, revenue, netProfit, RSI, 52W range.
Example format:
|
Metric
|
Value
|
|
Avoid data dumping; each key number must include interpretation.
Every numeric claim must be grounded in actual payload values; do not fabricate numbers.
Keep concise but complete (target 250-500 characters for narrative).
Must include actionable guidance and time window.
Ticker and technical terms in English.
Daily Brief Analysis Guide
When analyzing
brief
output, generate an actionable morning/evening briefing for OpenClaw conversation.
Morning Brief
Market overview
risk-on/off + key overnight move + today's tone, plus an index snapshot table from
marketOverview.indices
(index name, price, % change, timestamp)
Holdings check
holdings that need action first, with per-holding price/% change/grade when available
Radar relevance
which radar themes impact holdings
Today's plan (required)
specific watch levels / event / execution plan
Data Sources (required)
one-line QVeris attribution and channels used in this brief
Evening Brief
Session recap
index + sector + portfolio one-line recap, with key index close/% change
Holdings change
biggest winners/losers and why, with quantized move (%) where available
Thesis check
whether thesis changed
Tomorrow's plan (required)
explicit conditions and actions
Data Sources (required)
one-line QVeris attribution and channels used in this brief
Quality Bar
Prioritize user holdings, not generic market commentary.
Quantify changes when possible (%, levels, counts).
Keep concise and decision-oriented.
Include a short source disclosure line at the end to improve traceability and credibility.
Hot Topic Analysis Guide
When analyzing
radar
output, cluster signals into investable themes and provide concise actionable conclusions.
Required Output (per theme)
Theme
clear, investable label
Driver
what changed and why now
Impact
beneficiaries/losers + magnitude + duration
Recommendation (required)
concrete trigger or level
Risk note
key invalidation or monitoring signal
Source tag (required)
include
source
label for each theme (for example:
caidazi_report
,
alpha_news_sentiment
,
x_hot_topics
)
Execution Rules
Cluster into 3-5 themes max.
Cross-verify sources; lower confidence for social-only signals.
Distinguish short-term trade vs mid-term allocation.
Keep each theme concise (<200 characters preferred).
End with a QVeris source disclosure line listing channels that contributed to this radar run.