shareholder-manager

Cache and manage historical shareholder counts for A-share stocks using DuckDB and Akshare APIs.

Updated Jan 12, 2026
One-click install
npx skills add https://github.com/chinawrj/agent-skills-stock --skill shareholder-manager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shareholder-manager
Source: https://github.com/chinawrj/agent-skills-stock/tree/main/.github/skills/shareholder-manager
Command: npx skills add https://github.com/chinawrj/agent-skills-stock --skill shareholder-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires duckdb, pandas, akshare, and includes scripts (resource) components.

What problem does it solve?

Cache and manage historical shareholder counts for A-share stocks to enable fast queries and trend analysis.

Core Features & Use Cases

  • Local caching of shareholder history with read and write APIs.
  • Query single-stock history, observe trends, and perform incremental or full data updates.
  • Rebuild or synchronize the full dataset from online sources when needed.

Quick Start

Ask the system to fetch the latest shareholder counts for a given stock and cache them locally.

Frequently Asked Questions about shareholder-manager

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I cache historical shareholder counts for A-share stocks locally?

To fetch and cache shareholder counts, ask the system to retrieve the latest data for a given stock. It fetches online data via akshare and stores it in a local DuckDB cache for fast queries.

How do I incrementally update stock shareholder data without downloading everything again?

Incremental updates fetch only missing recent records via akshare and append them to the local DuckDB cache, avoiding a full dataset rebuild while keeping shareholder trend data current.

Can I use DuckDB to query historical shareholder trends for A-share stocks?

Yes, DuckDB stores the cached shareholder history locally, enabling fast SQL queries and trend observation for single A-share stocks without hitting online APIs repeatedly.

Does akshare work with DuckDB for caching A-share shareholder history?

Yes, this Skill fetches A-share shareholder data via akshare and persists it into a local DuckDB database, combining online data retrieval with fast local cache reads.

What is the best way to rebuild the entire stock shareholder dataset from scratch?

The best way is to trigger a full dataset rebuild, which synchronizes the entire shareholder history from online akshare sources into the local DuckDB cache, replacing stale records.

Why does querying shareholder counts online every time slow down my trend analysis?

Fetching shareholder counts online repeatedly introduces network latency and rate limits. Caching them locally in DuckDB eliminates this overhead, enabling fast trend analysis and batch updates.