feature-engineer

Computes streaming transaction features from raw Kafka events.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/GaneshMadarasu/real-time-anomaly-detection-pipeline --skill feature-engineer-ganeshmadarasu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-engineer
Source: https://github.com/GaneshMadarasu/real-time-anomaly-detection-pipeline/tree/main/.claude/skills/feature-engineer
Command: npx skills add https://github.com/GaneshMadarasu/real-time-anomaly-detection-pipeline --skill feature-engineer-ganeshmadarasu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you understand and work with the feature-engineer service that converts raw transaction events into enriched fraud-detection features in real time, so streaming anomaly detection can run reliably at scale.

Core Features & Use Cases

  • Faust Stream Processing: Explains how the service consumes Kafka events asynchronously and publishes enriched records.
  • Redis Sliding-Window Features: Covers the per-user 60-second amount window pattern used to compute mean, standard deviation, and z-scores.
  • Risk Feature Engineering: Shows how merchant risk, odd-hour activity, and composite risk scoring are derived from each event.
  • Observability and Reliability: Describes the native health and metrics endpoints, error handling, and implementation gotchas.
  • Use Case: Use this Skill when modifying or reviewing anomaly-detection/services/feature-engineer/main.py, tuning feature logic, or tracing how raw transactions become model-ready inputs.

Quick Start

Use the feature-engineer skill to explain how the service ingests Kafka transactions, computes Redis-backed features, and publishes enriched events.

Frequently Asked Questions about feature-engineer

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

FAQPage Schema
How do I compute streaming transaction features from Kafka events for fraud detection?

Streaming transaction features are computed from Kafka events by using Faust for asynchronous ingestion and publishing enriched records. The service parses JSON events, calculates per-user 60-second statistics, and publishes enriched fraud-detection features downstream.

How does a Redis sliding window calculate per-user transaction statistics?

A Redis sliding window calculates per-user transaction statistics by maintaining a 60-second amount window for each user. This pattern enables the real-time computation of mean, standard deviation, and z-scores to detect anomalous transaction behavior.

How do I derive risk features from raw transaction streams?

Risk features are derived from raw transaction streams by evaluating merchant risk, odd-hour activity, and composite risk scoring for each event. This transforms raw Kafka transactions into model-ready inputs for real-time anomaly detection.

What is the best way to handle Kafka I/O and errors in a Faust stream processing service?

Robust Kafka I/O handling and error management are achieved through native health and metrics endpoints. The service integrates Prometheus metrics to monitor reliability and handle ingestion errors within the Faust stream processing pipeline.

Can I use Faust and Redis for real-time anomaly detection pipelines?

Faust and Redis can be used together for real-time anomaly detection pipelines. Faust handles asynchronous Kafka event consumption while Redis provides the backend for sliding window feature computation required for reliable streaming fraud detection.

Why do I need accurate JSON event parsing in a feature engineering pipeline?

Accurate JSON event parsing is required in a feature engineering pipeline because raw Kafka transactions must be precisely decoded to compute per-user statistics and risk features. Parsing failures disrupt the generation of model-ready inputs for anomaly detection.