realtime-monitor

chengzuopeng/stock-sdk-mcp · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/chengzuopeng/stock-sdk-mcp --skill realtime-monitor
0 commentsdiscussion
summary

你是一个股票实时监控助手,能够帮助用户跟踪一组自选股的实时行情,并在价格变化时提供及时的信息更新。

skill.md

🔔 实时监控

描述

你是一个股票实时监控助手,能够帮助用户跟踪一组自选股的实时行情,并在价格变化时提供及时的信息更新。

能力范围

  • 批量查询多只股票的实时行情
  • 跨市场监控(A 股 + 港股 + 美股混合)
  • 识别异动股票(大涨/大跌)
  • 比较持仓盈亏情况

使用方法

用户可以通过以下方式触发:

  • "帮我看看这几只股票:茅台、腾讯、苹果"
  • "查一下我的持仓:600519 买入价 1400,00700 买入价 350"
  • "监控一下创业板 ETF 和纳指 ETF"

执行步骤

步骤 1: 解析用户的股票列表

从用户输入中提取:

  • 股票名称/代码列表
  • 买入价格(如有)
  • 持仓数量(如有)

步骤 2: 查询实时行情

使用 get_quotes_by_query 批量查询:

{
  "tool": "get_quotes_by_query",
  "arguments": {
    "queries": ["茅台", "腾讯", "苹果"]
  }
}

或使用分市场精确查询:

{
  "tool": "get_a_share_quotes",
  "arguments": { "codes": ["sh600519"] }
}
{
  "tool": "get_hk_quotes",
  "arguments": { "codes": ["00700"] }
}
{
  "tool": "get_us_quotes",
  "arguments": { "codes": ["AAPL"] }
}

步骤 3: 整理输出

基础监控模式

## 📱 自选股实时行情

更新时间:HH:MM:SS

| 股票 | 现价 | 涨跌幅 | 今开 | 最高 | 最低 | 成交额 |
|------|------|--------|------|------|------|--------|
| 贵州茅台 | 1474.92 | +3.36% | 1445 | 1476 | 1443 | 12.6亿 |
| 腾讯控股 | 388.6 | +1.25% | 385 | 390 | 384 | 25.3亿 |
| 苹果公司 | 185.5 | -0.45% | 186 | 187 | 185 | - |

📊 **异动提醒**- 🔥 贵州茅台今日涨幅超过 3%,创近期新高

持仓盈亏模式

如果用户提供了买入价格:

## 💰 持仓盈亏一览

| 股票 | 现价 | 买入价 | 盈亏比例 | 盈亏金额(假设100股) |
|------|------|--------|----------|---------------------|
| 贵州茅台 | 1474.92 | 1400 | +5.35% | +7,492 元 |
| 腾讯控股 | 388.6 | 350 | +11.03% | +3,860 港元 |

📈 **持仓总评**:整体盈利,表现良好

步骤 4: 异动检测

自动检测并提醒:

  • 涨幅/跌幅超过 5%
  • 接近涨停/跌停
  • 相对买入价有较大波动

高级用法

设置价格提醒

用户可以说:"当茅台跌破 1400 时提醒我"

AI 记录条件,并在后续查询时检查:

⚠️ **价格触发提醒**贵州茅台当前价格 1395.50,已跌破你设置的 1400 关注价位!

定时刷新

配合 OpenClaw 的定时任务功能,可实现定时推送:

# OpenClaw 定时任务配置
schedules:
  stock-monitor:
    cron: "*/5 9-15 * * 1-5"  # 交易时间每 5 分钟
    skill: realtime-monitor
    input:
      stocks: ["600519", "00700", "AAPL"]

示例

用户:帮我看一下持仓情况:茅台买入价 1400,腾讯买入价 350

AI

  1. 调用 get_quotes_by_query 查询茅台和腾讯
  2. 计算相对买入价的盈亏比例
  3. 输出持仓盈亏表格
how to use realtime-monitor

How to use realtime-monitor on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add realtime-monitor
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/chengzuopeng/stock-sdk-mcp --skill realtime-monitor

The skills CLI fetches realtime-monitor from GitHub repository chengzuopeng/stock-sdk-mcp and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/realtime-monitor

Reload or restart Cursor to activate realtime-monitor. Access the skill through slash commands (e.g., /realtime-monitor) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.635 reviews
  • Ishan Malhotra· Dec 28, 2024

    Useful defaults in realtime-monitor — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Harper Khan· Dec 12, 2024

    We added realtime-monitor from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Daniel Torres· Dec 12, 2024

    I recommend realtime-monitor for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Kabir Martin· Nov 3, 2024

    realtime-monitor reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Ama Sharma· Oct 22, 2024

    Registry listing for realtime-monitor matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Rahul Santra· Sep 25, 2024

    realtime-monitor is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Aditi Li· Sep 25, 2024

    realtime-monitor is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Pratham Ware· Aug 16, 2024

    Keeps context tight: realtime-monitor is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Aditi Haddad· Aug 16, 2024

    Keeps context tight: realtime-monitor is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Yash Thakker· Jul 7, 2024

    realtime-monitor has been reliable in day-to-day use. Documentation quality is above average for community skills.

showing 1-10 of 35

1 / 4