RKiding/Awesome-finance-skills / skills/alphaear-stock
alphaear-stock
VerifiedSearch A-Share/HK/US finance stock tickers and retrieve finance stock price history. Use when user asks about finance stock codes, recent price changes, or specific company finance stock info.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.5 KB |
| scripts/__init__.py | script | 0 B |
| scripts/database_manager.py | script | 4.1 KB |
| scripts/stock_tools.py | script | 19.4 KB |
| tests/test_stock.py | script | 634 B |
SKILL.md
View on GitHub---
name: alphaear-stock
description: Search A-Share/HK/US finance stock tickers and retrieve finance stock price history. Use when user asks about finance stock codes, recent price changes, or specific company finance stock info.
---
# AlphaEar Stock Skill
## Overview
Search A-Share/HK/US stock tickers and retrieve historical price data (OHLCV).
## Capabilities
### 1. Stock Search & Data
Use `scripts/stock_tools.py` via `StockTools`.
- **Search**: `search_ticker(query)`
- Fuzzy search by code or name (e.g., "Moutai", "600519").
- Returns: List of `{code, name}`.
- **Get Price**: `get_stock_price(ticker, start_date, end_date)`
- Returns DataFrame with OHLCV data.
- Dates format: "YYYY-MM-DD".
- **Get Fundamentals**: `get_stock_fundamentals(ticker)`
- Returns dict with sector, industry, market cap, PE ratio, and summary.
- Supports A-Share/HK/US stocks.
## Dependencies
- `pandas`, `requests`, `akshare`, `yfinance`
- `scripts/database_manager.py` (stock tables)
## Notes
- **Proxy**: For US stock data (via `yfinance`), you may need to set environment variables if your network cannot reach Yahoo Finance directly:
```bash
export HTTP_PROXY="http://<proxy_ip>:<port>"
export HTTPS_PROXY="http://<proxy_ip>:<port>"
```
- **A-Share/HK**: Data is primarily fetched via `akshare` (EastMoney), which usually works best with a direct connection in China. The tool automatically detects proxy issues and attempts direct connection for these markets.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |