Query HK Company Profiles by Trade Code with company-hk

Where this fits

A user asks your agent: "Tell me about Tencent, the company behind 00700.HK." Without a structured data source, the agent would scrape websites or guess. The company-hk skill solves this by exposing a clean API endpoint that returns official company profile fields—name, registration date, legal representative, business scope, employee count, and more—given a Hong Kong stock trade code. This fits directly into any agent that handles financial research, due diligence, or investor Q&A workflows.

Why agents benefit

• Zero scraping overhead: The skill wraps the /api/v1/market/data/hk/company-hk endpoint, so your agent gets structured JSON instead of parsing HTML.
• Precise field coverage: Returns 15+ fields including company_prof, business_main, staff_num, website, and reg_money—enough to answer most company-profile queries without chaining multiple tools.
• Code normalization: Enforces the .HK suffix (e.g., 00700.HK), reducing errors from ambiguous user inputs like "700" or "Tencent."
• Localization ready: Includes both Chinese and English company names, plus currency and address fields, making it suitable for multilingual agents.
• Deterministic output: The response schema is fixed, so your agent can reliably map fields to downstream logic or UI templates.

Practical scenarios

Investor chatbot answering "Tell me about Tencent"

The agent extracts the trade code from the query, calls the skill with 00700.HK, and formats a concise summary: founding date, legal representative, main business, and employee count—all from one request.

Pre-meeting due diligence for HK-listed companies

A research agent gathers profiles for a watchlist of 20 tickers. It loops through the skill, caches responses, and produces a comparison table with registration capital and website links, saving hours of manual lookup.

CRM enrichment for financial advisory tools

When a user enters a HK stock code, the agent automatically fetches the company profile and stores it in the CRM record, enriching client data without additional user input.

Add it to your agent workflow

Install the skill via npx:

npx skills add FTShare-Lab/FTShare-skill --skill company-hk

Then invoke it with a trade code. Here's a minimal example (pseudo-code for your agent's tool-calling layer):

result = call_skill("company-hk", {"trade_code": "00700.HK"})
print(result["company_name"], result["business_main"])

Ensure your agent validates that the user's input includes the .HK suffix; if not, append it before making the call.

Compare before adopting

Before committing, evaluate the skill against three criteria:

• Quality signals: Check the GitHub repo for recent commits, issue resolution, and whether the underlying API is stable. The skill has 58 stars—a modest but positive signal.
• Maintenance freshness: Look at the last update date. If the API endpoint changes, is the skill maintained? FTShare-Lab appears active, but verify.
• Alternatives: Other data sources like Yahoo Finance or official HKEX filings may offer more depth, but they require heavier parsing. This skill is a lightweight, focused option.

Also consider how well it fits your agent's existing tool schema—does it align with your error-handling and retry patterns?

Why it is worth tracking

company-hk is a pragmatic, single-purpose skill that solves a common data-access problem for agents dealing with Hong Kong equities. Its structured output and clear parameter contract make it easy to integrate, and the 58-star community signal suggests it has been tested by other developers. Track it if you frequently handle HK company queries; you can evaluate it side-by-side with other market-data skills on OpenAgentSkill to see which fits your stack best. Given its simplicity and direct value, it's worth a trial in any financial agent prototype.