stock-query

What This Skill Does

The stock-query skill provides OpenClaw users with real-time access to global financial market data directly from their terminal or agent interface. Designed to streamline investment tracking, it retrieves up-to-date pricing for A-shares, Hong Kong stocks, US stocks, various ETFs, mutual funds, and major market indices. By leveraging robust data sources like Tencent Finance and Sina Finance, the skill delivers accurate snapshots of market performance, eliminating the need to manually browse financial portals for quick updates.

Installation

You can install this skill globally through the OpenClaw skill registry using the following command: clawhub install openclaw/skills/skills/asfamilybank/stock-query

Ensure that you have curl and iconv installed on your system path, as the skill requires these dependencies for fetching and decoding market data, ensuring compatibility across different character encodings.

Use Cases

• Investment Monitoring: Quickly check current share prices for holdings in your portfolio.
• Portfolio Valuation: Retrieve the latest net asset values (NAV) for ETFs or mutual funds to calculate total asset value.
• Market Sentiment Analysis: Instantly fetch indices like the Shanghai Composite, HSI, or the S&P 500 to gauge broader market trends.
• Pre-trade Research: Verify the real-time pricing of specific assets before executing or planning trade strategies.

Example Prompts

1. "/stock-query AAPL TSLA 00700"
2. "/stock-query 510300 000001"
3. "/stock-query 沪深300ETF 腾讯"

Tips & Limitations

• Precision: Ensure ticker codes are correct (e.g., 6 digits for A-shares/ETFs, 5 digits for HK stocks). If a ticker is ambiguous, the skill is designed to prompt for clarification.
• Scope: This skill is strictly for traditional equities, funds, and indices. It does not support cryptocurrency, futures, options, or foreign exchange markets.
• Meta Commands: Use /stock-query help or /stock-query version to access built-in utility commands for documentation and maintenance. Always ensure your environment supports character conversion from GBK to UTF-8 to prevent garbled text output in specific API responses.