handle-input

Route touchpad, ring, and IMU events for Even Hub G2 applications.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/Ertejeonline/er-clock --skill handle-input
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handle-input
Source: https://github.com/Ertejeonline/er-clock/tree/main/resources/handle-input
Command: npx skills add https://github.com/Ertejeonline/er-clock --skill handle-input

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Handling user input and routing events in Even Hub G2 apps across multiple input sources (touchpads, ring, IMU) and lifecycle states.

Core Features & Use Cases

  • Supports G2 touchpad, R1 ring, and IMU input sources
  • Defines clear event routing rules for text, list, and system events
  • Provides lifecycle management guidance and safe exit patterns

Quick Start

Integrate the event handling template into your Even Hub G2 app to route gestures and lifecycle events.

Frequently Asked Questions about handle-input

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

FAQPage Schema
How do I handle input events and routing for Even Hub G2 applications?

Event routing for Even Hub G2 apps is managed by implementing a single page listener that directs touchpad gestures, Ring inputs, and IMU data across text, list, and system containers. This enforces lifecycle cleanup and safe exit patterns.

What input sources are supported for G2 touchpad and R1 ring event management?

Supported input sources include G2 touchpad gestures, R1 Ring inputs, and IMU sensor data. The system defines clear event routing rules to process these inputs across text containers, list containers, and system events.

Can I use this event hub approach for lifecycle management and system exits in G2 apps?

Lifecycle management and system exits in G2 apps are supported through enforced lifecycle cleanup and system-exit guidance. The single page listener ensures events are routed safely during text, list, and system state transitions.

What's the best way to route touchpad gestures and IMU data in Even Hub apps?

Routing touchpad gestures and IMU data is best handled by integrating an event handling template into your Even Hub G2 app. This template routes gestures and lifecycle events using a single page listener with defined routing rules.

Why does my G2 app need a single page listener for event routing?

A single page listener is needed for G2 event routing to centralize input management across touchpads, rings, and IMU sources. This approach enforces lifecycle cleanup and prevents event conflicts across text and list containers.

Does this input handling approach work with text and list containers simultaneously?

Input handling works simultaneously with text and list containers by defining clear event routing rules. The system processes G2 touchpad, R1 ring, and IMU inputs while managing lifecycle states across these container types.