signal-detector

Capture ambient inbound signals for the OpenClaw e2e reference fixture.

5|1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/GYF0311/lorekit --skill signal-detector-gyf0311
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: signal-detector
Source: https://github.com/GYF0311/lorekit/tree/main/brain/test/fixtures/openclaw-reference-minimal/skills/signal-detector
Command: npx skills add https://github.com/GYF0311/lorekit --skill signal-detector-gyf0311

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Signal detection for the OpenClaw e2e reference fixture: reliably capture every inbound message so downstream test logic can react to it.

Core Features & Use Cases

  • Always-on ambient capture: Listens for an inbound-message trigger and records/forwards signal events continuously.
  • Fixture-scoped behavior: Tailored for the OpenClaw reference compatibility test workflow (test/e2e/openclaw-reference-compat.test.ts).
  • Trigger-driven operation: Runs on every inbound message to ensure no relevant event is missed.

Quick Start

Enable the signal-detector fixture skill and run the OpenClaw reference compatibility test so inbound messages are captured for the test assertions.

Frequently Asked Questions about signal-detector

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

FAQPage Schema
How do I capture every inbound message during e2e testing without gaps?

Ambient signal detection captures every inbound message during e2e testing by triggering on each received event. This ensures continuous event observation without missing data for downstream test assertions.

What is continuous signal detection in OpenClaw compatibility tests?

Continuous signal detection in OpenClaw compatibility tests is a fixture-scoped behavior that records and forwards inbound signal events. It operates trigger-driven on every message to guarantee no ambient event is missed.

How do I set up signal detection for the OpenClaw reference fixture?

Enable the signal-detector fixture skill and run the OpenClaw reference compatibility test to set up signal detection. This captures inbound messages continuously for your test assertions.

Does the signal detector support fixture-scoped event capture for e2e workflows?

Yes, the signal detector supports fixture-scoped event capture tailored for the OpenClaw reference compatibility test workflow. It applies to e2e scenarios requiring observation of all incoming events.

Why are inbound messages being missed in my e2e compatibility test?

Inbound messages are missed in e2e compatibility tests when the capture mechanism is not trigger-driven for every event. Always-on ambient signal detection ensures continuous recording without event gaps.

Can I use ambient signal detection for other e2e test scenarios outside OpenClaw?

Ambient signal detection is tailored for the OpenClaw reference compatibility test workflow, but its trigger-driven event capture mechanism applies to any e2e scenario requiring continuous inbound message observation.