event-driven

Score news events and generate time-decayed trading signals in CSV format.

Updated May 5, 2026
One-click install
npx skills add https://github.com/wudye/traderAssistHK --skill event-driven-wudye
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: event-driven
Source: https://github.com/wudye/traderAssistHK/tree/main/backend/src/skills/event-driven
Command: npx skills add https://github.com/wudye/traderAssistHK --skill event-driven-wudye

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pandas, numpy.

What problem does it solve?

This Skill reduces subjective, inconsistent event interpretation by converting news, announcements, and macro updates into standardized sentiment scores and time-decayed trading signals.

Core Features & Use Cases

  • Event-to-signal pipeline: fetch event text via read_url, score impact on a fixed scale from -1.0 to 1.0, and store results in an event CSV with a strict schema.
  • Decoupled data and logic: keep the event CSV as the data layer and use signal_engine.py as the logic layer for time decay and aggregation.
  • Weighted integration with technicals: combine the event-driven signal with an existing technical signal using a configurable weight (alpha, default 0.6), producing a final clipped signal in [-1.0, 1.0].
  • Look-ahead bias safeguards: enforce that the event CSV uses the knowable date and only aggregates events with event_date <= trade_date.

Quick Start

Ask the AI to build an event CSV from your latest news and announcements, score each item with the provided prompt scale, then aggregate it with your technical signal to output the final [-1.0, 1.0] trading signal using the default decay and alpha settings.

Frequently Asked Questions about event-driven

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert event news into time-decayed trading signals for backtesting?

Event news is converted into time-decayed trading signals by scoring sentiment on a -1.0 to 1.0 scale, storing it in a strict event CSV schema, and aggregating it with exponential decay to align with trade dates. This avoids look-ahead bias by using knowable dates.

How does event signal fusion work with existing technical indicators?

Event signal fusion combines the event-driven signal with a technical signal using a configurable weight parameter called alpha, defaulting to 0.6. The logic layer aggregates both inputs to produce a final clipped trading signal bounded between -1.0 and 1.0.

How do I prevent look-ahead bias when building event-driven trading signals?

To prevent look-ahead bias when building event-driven signals, the event CSV must use the knowable date instead of the announcement date. The aggregation logic strictly enforces that only events with an event date less than or equal to the trade date are processed.

Can I use pandas and numpy to aggregate event sentiment scores with exponential decay?

You can use pandas and numpy to aggregate event sentiment scores with exponential decay. The logic layer processes the event CSV data to apply configurable decay parameters, converting raw sentiment scores into time-decayed signals suitable for backtesting.

What is the required CSV schema for generating event-driven trading signals?

The required CSV schema for event-driven trading signals separates the data layer from the logic layer. It mandates strict adherence to specific fields for event dates and sentiment scores scaled from -1.0 to 1.0, ensuring proper time decay aggregation and look-ahead bias safeguards.

Does this event-driven signal approach work for macro updates and announcements?

This event-driven signal approach works for macro updates and announcements by reducing subjective interpretation. It fetches event text, scores the impact on a fixed scale, and outputs a standardized time-decayed event CSV applicable to backtesting scenarios.