sm-event-handler

Name: sm-event-handler
Availability: InStock
Author: dchuk

Coordinate SourceMonitor lifecycle events with host application logic.

3|Updated Oct 16, 2025

Search Tags:#automation #events #callbacks #ruby #workflows #source-monitor

Ready to run

npx skills add https://github.com/dchuk/source_monitor --skill sm-event-handler

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sm-event-handler
Source: https://github.com/dchuk/source_monitor/tree/main/.claude/skills/sm-event-handler
Command: npx skills add https://github.com/dchuk/source_monitor --skill sm-event-handler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate SourceMonitor lifecycle events with host application logic to trigger reactions.

Core Features & Use Cases

Event hooks for after_item_created, after_item_scraped, and after_fetch_completed
Support for registering item processors to run post-entry processing
Simple configuration DSL to wire host app logic to engine lifecycle events

Quick Start

Configure event handlers in your SourceMonitor setup to react to feed items as they are created, scraped, or fetched.

Frequently Asked Questions about sm-event-handler

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

FAQPage Schema

How do I automate callbacks for SourceMonitor lifecycle events in Ruby?▼

You can automate SourceMonitor lifecycle events by registering Ruby callbacks for after_item_created, after_item_scraped, and after_fetch_completed workflows to trigger host application reactions like indexing or notifications.

What is the best way to trigger post-processing after a feed item is scraped?▼

Triggering post-scrape processing involves registering item processors through a configuration DSL that wires your host app logic to the after_item_scraped event, enabling immediate analytics or indexing.

How does error isolation work for SourceMonitor event hooks?▼

Error isolation in SourceMonitor event hooks ensures that exceptions thrown within a registered callback handler do not crash the core engine or halt other registered lifecycle workflows.

Can I use a configuration DSL to wire host app logic to SourceMonitor events?▼

Yes, you can use a simple configuration DSL to wire host app logic directly to SourceMonitor engine lifecycle events, enforcing handler registration and arity rules for testable event reactions.

Do I need to register handlers for specific arity rules when automating SourceMonitor workflows?▼

Yes, automating SourceMonitor workflows requires registering handlers that follow strict arity rules, which guarantees the Event structs pass the correct data to your host application logic.

Why should I use SourceMonitor event hooks instead of polling for feed updates?▼

SourceMonitor event hooks provide immediate reactions to lifecycle events without polling overhead, directly coordinating engine events with host app logic for real-time notifications and analytics.