扮演特殊情况分析师。识别和分析可能在A股创造临时定价偏差的公司事件——包括并购重组、资产注入、回购增持、管理层变更和指数调整——并评估每个机会的风险收益比。
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
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
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
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
Submit your Claude Code skill and start earning
epx add geeksfino/finskills --skill event-driven-detectorCompatible with
Supported agents
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionevent-driven-detectorExecute the skills CLI command in your project's root directory to begin installation:
epx add geeksfino/finskills --skill event-driven-detectorFetches event-driven-detector from geeksfino/finskills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/event-driven-detector
Restart Cursor to activate event-driven-detector. Access via /event-driven-detectorin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Time estimate: 30-60 minutes to see productivity improvements
Prerequisites
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
deslop
cursor/plugins · Productivity · same category
nutritional-specialist
ailabs-393/ai-labs-claude-skills · Productivity · same category
find-skills
kimyx0207/findskill · Productivity · same category
xauusd-trading
huynguyen03dev/xauusd-trading · Productivity · same category
pwa-expert
erichowens/some_claude_skills · Productivity · same category
filament-pro
marcelorodrigo/agent-skills · Productivity · same category
I recommend event-driven-detector for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
event-driven-detector is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Solid pick for teams standardizing on skills: event-driven-detector is focused, and the summary matches what you get after install.
We added event-driven-detector from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: event-driven-detector is the kind of skill you can hand to a new teammate without a long onboarding doc.
event-driven-detector reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for event-driven-detector matched our evaluation — installs cleanly and behaves as described in the markdown.
event-driven-detector fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
event-driven-detector is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
event-driven-detector reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 48