signal-detector

Capture every inbound message signal for OpenClaw fixture workflows.

1|Updated May 9, 2026
One-click install
npx skills add https://github.com/weiping/gbrain-cn --skill signal-detector-weiping
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: signal-detector
Source: https://github.com/weiping/gbrain-cn/tree/main/test/fixtures/openclaw-reference-minimal/skills/signal-detector
Command: npx skills add https://github.com/weiping/gbrain-cn --skill signal-detector-weiping

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of reliably capturing and routing every inbound message signal so downstream systems can react with complete context rather than partial or delayed inputs.

Core Features & Use Cases

  • Always-on ambient capture: Continuously processes inbound message events for an OpenClaw reference fixture scenario.
  • Deterministic trigger coverage: Treats every inbound message as an input signal to support consistent e2e testing and reference behavior.
  • Use Case: Use it in an agent workflow where each received message must be logged/forwarded for later synthesis, graph updates, or evaluation steps.

Quick Start

Use the signal-detector skill in the OpenClaw reference fixture so every inbound message is captured as an ambient signal.

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 signal for event-driven agent workflows?

To capture every inbound message signal for event-driven agent workflows, use an always-on ambient capture mechanism that treats each received message as a deterministic input. This ensures comprehensive ingestion without missing context for downstream processing.

What is ambient message ingestion in e2e testing fixtures?

Ambient message ingestion in e2e testing fixtures is the continuous processing of inbound message events within a deterministic, fixture-scoped environment. It ensures consistent reference behavior by treating every inbound message as a comprehensive input signal.

How do I configure an all-inbound trigger for message capture?

To configure an all-inbound trigger for message capture, set up a root-level SKILL.md configuration. This establishes deterministic, fixture-scoped behavior to ensure every inbound message is comprehensively logged and forwarded.

Does the signal-detector skill work with the OpenClaw reference fixture?

Yes, the signal-detector skill works specifically with the OpenClaw reference fixture. It is designed to support event-driven agent workflows by providing always-on ambient capture of every inbound message within that environment.

Why do I need deterministic trigger coverage for e2e testing?

Deterministic trigger coverage is needed for e2e testing to ensure every inbound message is treated as a consistent input signal. This prevents partial or delayed inputs, allowing downstream systems to react with complete context.

What are the limitations of using ambient capture for message ingestion?

Ambient capture for message ingestion is limited to deterministic, fixture-scoped behavior and requires a root-level SKILL.md configuration. It is specifically tailored for OpenClaw reference fixture scenarios rather than general-purpose event processing.