expanso-deduplicate-events

Deduplicate HTTP events via content hashing and cache, outputting unique events to Kafka.

1|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/expanso-io/expanso-skills --skill expanso-deduplicate-events
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: expanso-deduplicate-events
Source: https://github.com/expanso-io/expanso-skills/tree/main/skills/recipes/deduplicate-events
Command: npx skills add https://github.com/expanso-io/expanso-skills --skill expanso-deduplicate-events

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill prevents duplicate event processing by identifying and filtering out identical events based on their content.

Core Features & Use Cases

  • Content Hashing: Generates a unique key based on event content for reliable deduplication.
  • Cache-Based Detection: Leverages a cache to efficiently track seen events and detect duplicates.
  • Configurable Strategy: Supports simple event_id based deduplication or a more complex composite key including event type and timestamp.
  • Use Case: In a high-throughput system, ensure that the same event (e.g., a user login) is not processed multiple times, preventing erroneous actions or inflated metrics.

Quick Start

Run the pipeline with sample data using the provided script.

Frequently Asked Questions about expanso-deduplicate-events

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

FAQPage Schema
How do I deduplicate events in a high-throughput data pipeline?

Deduplicate events by applying content hashing to incoming data and leveraging a cache to identify and filter identical entries, which prevents duplicate processing in high-throughput systems.

What is the best way to prevent duplicate event processing based on event content?

The best way to prevent duplicate event processing is using content hashing to generate a unique key based on event content, ensuring identical events are filtered out before causing erroneous actions.

Can I configure the deduplication key to use a composite of event type and timestamp?

Yes, you can configure the deduplication strategy to use either a simple event_id or a composite key that includes event type, source, and a timestamp window to identify duplicate entries.

How does event deduplication work with Kafka and HTTP inputs?

Event deduplication processes incoming events via HTTP, checks a cache for duplicates using content hashing, and outputs unique events to Kafka while logging duplicate entries to a file.

When should I use a cache-based approach for event deduplication?

You should use a cache-based approach for event deduplication when you need to efficiently track seen events in a high-throughput system and prevent identical events from being processed multiple times.