360 Secure SkillHub
360 安全技能中心

A股新闻研报检索

面向中国A股财经信息的检索Skill：把用户问题改写为含主体、事件、时间窗的查询，调用Python脚本访问东方财富妙想搜索接口，在终端展示标题、来源、日期与正文摘要，并生成.txt与.json结果文件，要求引用来源并区分事实与推断。需配置MX_APIKEY，不适用于行情数据、选股、自选与模拟交易。

zoeluli7459-dev
zoeluli7459-dev
热度 28.91
最近更新 2026-07-27 19:09:58
分类：搜索依赖：代码执行 / 第三方 API / 读写文件应用场景：研究 / 市场分析 / 财务

安装技能

复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill： npx secure-skills-cli add zoeluli7459-dev/mx-search
Metadata
name
mx-search
description
Use this skill for finance-specific information retrieval with Eastmoney MX search when the user asks for time-sensitive or source-backed financial news, announcements, research reports, policies, trading rules, market events, event explanations, or impact analysis. Prefer it over generic web search for China/A-share finance information. Do not use for exact quote/financial statement data (use mx-data), condition-based stock screening (use mx-xuangu), watchlist actions (use mx-zixuan), or simulated trading operations (use mx-moni).

mx-search

Use mx_search.py to retrieve finance news and event context from Eastmoney MX selected sources.

Trigger Boundaries

  • Use for "latest", "today", "recent", "why did it move", announcements, research reports, policy updates, trading rules, event timelines, and source-backed market explanations.
  • Use before analysis when the user asks about a specific finance event whose facts may have changed.
  • Do not use for pure numerical quote/financial data; call mx-data.
  • Do not use for stock universe filtering; call mx-xuangu.

Inputs

  • Required: event/topic/entity plus what kind of source is needed if known, such as announcement, research report, policy, or news.
  • Ask a follow-up only when missing entity/time/source type would likely retrieve the wrong event.
  • Require MX_APIKEY. Optional: set MX_OUTPUT_DIR; otherwise output goes to ~/.codex/skills-output/mx_data/output.

Workflow

  1. Rewrite the user request into a search query with entity, event, date window if known, and source preference.
  2. Run:
python /Users/lu/.codex/skills/mx-search/mx_search.py "贵州茅台最新研报 机构观点"
  1. Read terminal results for title, source, date, and content trunk.
  2. Load the generated .txt for longer extracted content or .json when metadata matters.
  3. If source ranking or result fields are unclear, read references/result-fields.md.

Output Contract

  • Cite source names and dates from the returned results.
  • Separate facts, source claims, and your inference.
  • For impact analysis, state the transmission logic and uncertainty instead of presenting source snippets as certainty.
  • Include generated file paths when useful for audit.

Failure Handling

  • Missing MX_APIKEY: stop and ask the user to configure it.
  • Sparse results: broaden the query or try the official name/code of the entity.
  • Conflicting sources: present the conflict and prefer official announcements or exchange/company disclosures where available.
  • API limit/auth/network errors: report the exact issue and do not fill gaps from memory.

Validation

  • Use evals/evals.json after changing routing or output behavior.
  • When changing the description, add both positive trigger examples and near-miss negative examples.