Skills

Uzi

A-share, Hong Kong, and US stock analysis skill for deep research, quick scans...

Install

npx skills add wbh604/UZI-Skill --skill uzi -g -a claude-code -y
Repository
wbh604/UZI-Skill7.5k
Category
Writing
Updated
18d ago
License
MIT
Context cost
Lightabout 483 tokens
Runs scripts
No, instructions only

What it does

A-share, Hong Kong, and US stock analysis skill for deep research, quick scans, investor panel review, hot-money/LHB analysis, trap detection, valuation, IC memos, and Bloomberg-style HTML reports.

UZI Skill Root

This root file is the top-level entry for agents that expect a SKILL.md at the repository root.

Use the narrowest matching workflow:

  • Full stock research, valuation, IC memo, initiation, catalysts, earnings review, or HTML report: read skills/deep-analysis/SKILL.md.
  • Investor jury, "which investors would buy", panel-only voting, or persona review: read skills/investor-panel/SKILL.md.
  • Hot-money, LHB, seat recognition, or A-share short-term trader analysis: read skills/lhb-analyzer/SKILL.md.
  • Trap detection, pump-and-dump checks, "teacher/group/friend recommended this stock", or safety review: read skills/trap-detector/SKILL.md.
  • Daily market-event briefs, scheduled macro releases, central-bank speeches, or event-aware alerts: read Official macro calendar verification, alongside the relevant stock workflow when stock analysis is also requested.
  • Command-specific requests: read the matching file under commands/.

Default Execution

From the repository root:

python3 run.py <ticker> --no-browser

For remote/mobile reports:

python3 run.py <ticker> --remote

For a single investor school, such as A-share hot-money:

python3 run.py <ticker> --school F --no-browser

Agent Rules

  1. Treat scripts as data and scoring tools, not as final analyst judgment.
  2. Do not invent numbers. Use script outputs, cached JSON, or current public evidence.
  3. For serious deep-analysis requests, complete the agent review loop described in skills/deep-analysis/SKILL.md before final report assembly.
  4. For hot-money analysis, apply LHB seat matching and is_in_range() before making a short-term judgment.
  5. For trap detection, scan all eight signals and include concrete evidence when risk is non-trivial.
  6. For report template or UI changes, update tests, version metadata, and release notes together.

More in Writing