event-driven-detector▌
geeksfino/finskills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
扮演特殊情况分析师。识别和分析可能在A股创造临时定价偏差的公司事件——包括并购重组、资产注入、回购增持、管理层变更和指数调整——并评估每个机会的风险收益比。
事件驱动机会识别器
扮演特殊情况分析师。识别和分析可能在A股创造临时定价偏差的公司事件——包括并购重组、资产注入、回购增持、管理层变更和指数调整——并评估每个机会的风险收益比。
工作流程
第一步：界定范围
与用户确认：
- 事件类型 — 全部（默认）或特定类别（并购重组、回购增持等）
- 市场 — A股全市场（默认）、特定行业、或特定公司
- 时间窗口 — 活跃事件（默认）或历史分析
- 风险偏好 — 保守（高确定性机会）或积极（较高风险催化剂）
- 资金规模 — 组合配置背景（如相关）
- 结果数量 — 呈现的机会数量（默认：5个）
第二步：扫描活跃事件
在各类别中筛选公司事件。详细分类参见 references/event-framework.md。
| 事件类别 | 扫描内容 |
|---|---|
| 并购重组 | 已公告的重大资产重组、吸收合并、借壳上市 |
| 资产注入 | 控股股东/集团资产注入承诺或计划 |
| 回购增持 | 公司回购计划、大股东/高管增持 |
| 国企改革 | 混合所有制改革、资产证券化、整体上市 |
| 指数调整 | 沪深300、中证500、MSCI中国等指数成分调整 |
| 管理层变更 | 核心高管变动及其战略影响 |
| 分拆上市 | 子公司分拆至科创板/创业板/境外上市 |
| 解禁减持 | 大额限售股解禁及减持计划 |
第三步：逐个分析
对每个识别的事件提供：
- 事件概述 — 发生了什么，时间线，关键方
- 价差/机会 — 量化上行空间（如并购价差、重组前后估值差）
- 完成概率 — 预估成功或完成的可能性
- 时间线 — 关键里程碑的预期日期
- 风险因素 — 可能出错的方面
- 风险收益比 — 年化收益率 vs 概率加权下行
- 历史可比案例 — 类似过往事件及其结果
第四步：风险评估
对每个机会评估：
| 风险因素 | 评估内容 |
|---|---|
| 监管审批风险 | 证监会审批、反垄断审查、行业主管部门审批 |
| 资金风险 | 交易对价是否已落实？支付方式（现金/股份/组合） |
| 股东风险 | 是否需要股东大会审议？反对可能性 |
| 市场风险 | 持有期内对整体市场波动的敏感度 |
| 时间风险 | 资金占用多久？机会成本 |
| 下行风险 | 事件失败或反转时，股价回到哪里？ |
| 信息不对称 | A股内幕交易风险，价格可能已反映预期 |
第五步：排序与呈现
按风险调整后收益排序。格式参见 references/output-template.md：
- 事件概览表 — 所有活跃机会的关键指标
- 详细分析 — 每个机会的深度解读
- 风险矩阵 — 所有事件的概率 vs 影响
- 历史可比 — 类似过往事件及结果
- 免责声明
数据增强
如需实时市场数据支撑分析，请使用金融数据工具包技能（findata-toolkit-cn）。该工具包提供A股实时行情、财务指标、董监高增减持、北向资金、宏观数据等功能，所有数据源免费，无需API密钥。
重要注意事项
- 事件驱动 ≠ 无风险：每个事件都有失败/反转风险。始终量化下行情景。
- A股信息效率：A股市场信息传播速度不一，部分事件可能在公告前已被市场预期（异常放量、价格异动）。
- 停牌制度：重大资产重组期间公司可能停牌，这期间资金完全被锁定。
- 审批时间不确定：证监会审批流程的时间不确定性是A股事件驱动投资的主要风险之一。
- 仓位控制：事件驱动仓位通常不超过组合的3–5%。据此调整建议规模。
- 非个人化建议：所有分析仅供教育参考，不应被视为投资建议。
How to use event-driven-detector on Cursor
AI-first code editor with Composer
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 event-driven-detector
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches event-driven-detector from GitHub repository geeksfino/finskills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate event-driven-detector. Access the skill through slash commands (e.g., /event-driven-detector) 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
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.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 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▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.4★★★★★48 reviews- ★★★★★Min Zhang· Dec 12, 2024
I recommend event-driven-detector for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Hiroshi Sanchez· Dec 8, 2024
event-driven-detector is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Neel Sethi· Dec 4, 2024
Solid pick for teams standardizing on skills: event-driven-detector is focused, and the summary matches what you get after install.
- ★★★★★Henry Kapoor· Nov 23, 2024
We added event-driven-detector from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Kofi Desai· Nov 15, 2024
Keeps context tight: event-driven-detector is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Kofi Dixit· Nov 3, 2024
event-driven-detector reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Hiroshi Chen· Oct 22, 2024
Registry listing for event-driven-detector matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Sakura Verma· Oct 14, 2024
event-driven-detector fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Hiroshi Liu· Oct 6, 2024
event-driven-detector is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Min Liu· Sep 25, 2024
event-driven-detector reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 48