skills.rest
Morris-UTRUST
Morris-UTRUSTCOMMUNITY
Explore all skills by this author →
GitHub

signal-detector

Capture ambient signals during OpenClaw reference test runs.

Updated May 16, 2026
Search Tags:#testing#monitoring#e2e#observability#fixture#signal
One-click install
npx skills add https://github.com/Morris-UTRUST/GBrain-knowledge --skill signal-detector-morris-utrust
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: signal-detector
Source: https://github.com/Morris-UTRUST/GBrain-knowledge/tree/main/test/fixtures/openclaw-reference-minimal/skills/signal-detector
Command: npx skills add https://github.com/Morris-UTRUST/GBrain-knowledge --skill signal-detector-morris-utrust

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ambient signal capture is required during OpenClaw reference tests to diagnose timing and behavior without instrumenting code.

Core Features & Use Cases

  • Continuous ambient signal capture during test runs for debugging and validation.
  • Lightweight, non-intrusive collection that does not affect test performance.
  • Use Case: verify that signals are observed across inbound messages in end-to-end tests.

Quick Start

Run the OpenClaw reference test fixture and observe the emitted ambient signals to verify continuous capture.

Frequently Asked Questions about signal-detector

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

FAQPage Schema
How do I capture ambient signals during e2e test runs without instrumenting code?▼

Non-intrusive ambient signal capture during e2e test runs is achieved by observing emitted signals from the test harness without modifying source code. This verifies continuous sensing across inbound messages safely.

What is ambient signal capture in testing and when do I need it?▼

Ambient signal capture in testing is the continuous, lightweight collection of behavioral signals during test execution. You need it to diagnose timing and behavior issues in e2e fixture tests without invasive instrumentation.

Does non-intrusive signal capture affect test performance or require external network calls?▼

Non-intrusive signal capture operates with safe defaults and does not affect test performance. It performs lightweight collection locally and makes no external network calls, ensuring isolated and safe test validation.

How do I verify continuous signal sensing across inbound messages in end-to-end tests?▼

To verify continuous signal sensing across inbound messages in e2e tests, run the reference test fixture and observe the emitted ambient signals. This confirms ongoing sensing throughout the test harness execution.

What is the best way to debug timing issues in e2e fixture tests without adding code instrumentation?▼

The best way to debug timing issues in e2e fixture tests without instrumentation is using always-on ambient signal capture. It collects diagnostic data non-intrusively within the test harness to validate timing and behavior.

Related Skills

Explore More Software Engineering Skills→
ltdrewltdrew
1

signal-detector

Detect ambient signals in inbound messages for OpenClaw reference fixtures.

Community
Basic
iciakkyiciakky

debug

Diagnoses root causes of code modifications using a seven-step debugging workflow and generates verified fix plans.

Community
Intermediate
jetteimjetteim

creating-observability-pipelines

Define and validate tool-agnostic telemetry pipeline contracts for observability data.

Community
Advanced
israel-salgadoisrael-salgado
2

dt-obs-frontends

Analyze RUM data to diagnose frontend performance, sessions, and errors.

Community
Advanced