← Back to Skills Marketplace
vahnxu

Signalradar

by vahnxu · GitHub ↗ · v1.0.8 · MIT-0
cross-platform ✓ Security Clean
834
Downloads
2
Stars
1
Active Installs
42
Versions
Install in OpenClaw
/install signalradar
Description
SignalRadar — Monitor Polymarket prediction markets for probability changes and send alerts when thresholds are crossed. Use when user asks to "add a Polymar...
Usage Guidance
This skill appears to be what it says: a Polymarket monitor implemented as Python scripts that run locally and can be scheduled. Before enabling: 1) Be aware it will create and write files under ~/.signalradar (watchlist, baselines, audit logs, reply-route) — review or back up that directory if needed. 2) The skill may modify your system crontab to enable periodic checks — only allow this if you approve a background job. 3) Alert delivery to webhooks means you will supply target URLs; treat those as secrets (Slack/Telegram webhooks or bot URLs contain tokens). 4) The skill documents relying on OpenClaw-injected env vars (OPENCLAW_REPLY_CHANNEL/TARGET) and will persist route info for background push; if you run it on the OpenClaw platform, know that route info will be stored indefinitely until overwritten. 5) If you want extra assurance, scan/inspect route_delivery.py and signalradar.py (delivery and scheduling code paths) to confirm no unexpected external endpoints or behaviors. If you do not want crontab changes or local persistence, run manual checks only (use run/show commands) rather than enabling scheduling.
Capability Analysis
Type: OpenClaw Skill Name: signalradar Version: 1.0.8 SignalRadar is a legitimate tool designed to monitor Polymarket prediction markets and alert users to probability changes. It utilizes `crontab` for background task persistence and `urllib` for network communication with the Polymarket API and user-configured webhooks, both of which are essential for its stated functionality. The code is well-structured, uses atomic file operations in `config_utils.py` to prevent corruption, and includes explicit instructions in `SKILL.md` to prevent common AI agent errors. No evidence of malicious intent, data exfiltration, or harmful prompt injection was found.
Capability Assessment
Purpose & Capability
Name/description (monitor Polymarket markets and send alerts) matches the declared requirements and included code. Required binaries (python3, crontab) are appropriate for a Python CLI that can be scheduled. No unrelated cloud credentials or unrelated binaries are requested.
Instruction Scope
Runtime instructions focus on reading Polymarket via gamma-api.polymarket.com and delivering alerts via webhook/file/openclaw. The SKILL.md references platform-injected env vars (OPENCLAW_REPLY_CHANNEL, OPENCLAW_REPLY_TARGET) and describes persisting a reply route file (~/.signalradar/cache/openclaw_reply_route.json); those platform envs are not listed as required in metadata (they are platform-injected, but the mismatch is worth noting). The skill will call external webhooks (user-supplied targets) to deliver alerts; that is expected but means data will be transmitted to arbitrary endpoints the user configures.
Install Mechanism
No install spec (instruction-only) — the bundle contains Python scripts that will run under the existing python3 interpreter. There are no downloads from untrusted URLs in the manifest and no package installs declared. This is low-risk from an install-source perspective.
Credentials
The skill does not request secrets or service credentials. It documents optional SIGNALRADAR_* env overrides for config/data paths (reasonable). Note: webhook targets provided by the user often contain secrets/tokens (e.g., Slack/Telegram bot URLs); treat configured webhook URLs as sensitive since the skill will send event payloads to them.
Persistence & Privilege
The skill writes and persists runtime state under the user's home (~/.signalradar/), including baselines, watchlist, audit logs, digest state, and a persisted OpenClaw reply route. It also attempts to auto-enable background monitoring and prefers using system crontab — that implies the ability to add/remove a crontab entry. Those are reasonable for a scheduler/monitoring tool, but they are material privileges: crontab modification and persistent reply-route capture are actions you should explicitly consent to.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install signalradar
  3. After installation, invoke the skill by name or use /signalradar
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.8
# SignalRadar 1.0.8 Changelog - Version bump to 1.0.8; updated version metadata in SKILL.md. - No user-facing feature or behavior changes. - Documentation updated for accurate versioning.
v1.0.7
- Updated version to 1.0.7 with metadata adjustments in SKILL.md. - Removed redundant README.md file. - No functional or user-facing command changes.
v1.0.6
Version 1.0.6 - Removed sample/developer file TODO.md; no user-facing changes. - No feature or critical rule changes. - All core functionality and behaviors remain unchanged.
v1.0.5
SignalRadar 1.0.5 - Updated version metadata to 1.0.5. - Added a TODO.md file for tracking future tasks. - Made minor updates to SKILL.md, including version and possible rule refinements. - Updated script files for consistency and documentation.
v0.9.931
Re-publish with crontab push fix: only add --push when delivery channel is openclaw; template overhaul; list --output json; script version string sync
v0.9.93
- Updated internal documentation version from 0.9.91 to 0.9.92 in SKILL.md. - No other functional or behavioral changes.
v0.9.92
Align DEFAULT_CONFIG delivery to webhook (matches default_config.json); declare crontab in requires.bins
v0.9.91
Version alignment; includes v0.9.8 channel-aware diagnostics + v0.9.9 bot token security fix
v0.9.9
Security fix: remove webhook URL (contains bot token) from user-visible HIT notification text. Route info remains in machine_payload for debugging.
v0.9.8
Channel-aware delivery diagnostics: schedule output now shows status relevant to the active delivery channel (webhook/openclaw/file); CR-11 rewritten for channel-aware diagnosis; new runtime-vs-docs conflict handling instruction
v0.9.7
Fix marketplace display name to English-only
v0.9.6
English-first SKILL.md (589→465 lines); add CR-11 push readiness check; add config delivery webhook shortcut; fix entry_id format; clean stale version refs
v0.9.5
v0.9.5: Webhook-first delivery — default channel changed to webhook for new installs, config shortcut command, doctor webhook check, onboard webhook setup guidance
v0.9.4
Add security scan precheck to prepublish gate: catches description contradictions, docstring/code inconsistencies, env var drift, and unscoped prohibitions before publish
v0.9.3
Fix security scan: resolve activation rule contradiction in description (URL sharing triggers show, not auto-add)
v0.9.2
v0.9.2 — Route gate decouple - Monitoring and push delivery decoupled: missing reply route no longer blocks cron from starting - schedule N now includes route gate warning (previously bypassed) - Shorter English-only description for ClawHub summary display
v0.9.1
v0.9.1 — Metadata & doc polish - Shorten description for ClawHub summary display (no truncation mid-sentence) - Fix display name: Signalradar → SignalRadar - Align SKILL.md / README.md / references/config.md auto-monitoring docs with route gate semantics
v0.9.0
v0.9.0 — OpenClaw Bot Readiness - Add 3-step bot-mode onboarding (onboard --step preview|confirm|finalize) - Return ONBOARD_NEEDED from add/run when watchlist is empty (JSON mode) - Replace unreliable --channel last with explicit reply-route persistence - Route gate: refuse to arm crontab when openclaw delivery has no captured route - Delivery observability in last_run.json, run --output json, schedule --output json - Remove internal files from public package (.clawhubignore enforcement)
v0.8.6
Version 0.8.6 - Bump version to 0.8.6 in metadata and documentation - Update SKILL.md for new version and compatibility information - No functional/logic changes to codebase; documentation and metadata updates only - Minor markup and version info adjustments for clarity and accuracy
v0.8.5
Webhook payload: add content field for Discord; text+content covers Slack, Telegram, Discord, MS Teams
Metadata
Slug signalradar
Version 1.0.8
License MIT-0
All-time Installs 1
Active Installs 1
Total Versions 42
Frequently Asked Questions

What is Signalradar?

SignalRadar — Monitor Polymarket prediction markets for probability changes and send alerts when thresholds are crossed. Use when user asks to "add a Polymar... It is an AI Agent Skill for Claude Code / OpenClaw, with 834 downloads so far.

How do I install Signalradar?

Run "/install signalradar" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Signalradar free?

Yes, Signalradar is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Signalradar support?

Signalradar is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Signalradar?

It is built and maintained by vahnxu (@vahnxu); the current version is v1.0.8.

💬 Comments