← Back to Skills Marketplace
diagnostikon

Polymarket Cybersecurity Trader

by diagnostikon · GitHub ↗ · v0.0.3 · MIT-0
cross-platform ⚠ suspicious
321
Downloads
0
Stars
0
Active Installs
5
Versions
Install in OpenClaw
/install polymarket-cybersecurity-trader
Description
Trades Polymarket prediction markets on major cyberattacks, ransomware incidents, data breaches, zero-day exploits, and national cybersecurity legislation. E...
Usage Guidance
Before installing, confirm and resolve the metadata mismatch: the repository files require a SIMMER_API_KEY and the simmer-sdk Python package even though the registry said none. If you will run live trades, you must supply SIMMER_API_KEY and understand the Simmer service's privileges and fees. By default the code runs in paper mode (venue='sim') and requires an explicit --live flag to execute real trades. If you plan to install, review the simmer-sdk package source (network behavior, where API keys are sent), and only provide SIMMER_API_KEY to services you trust. Ask the publisher why the registry metadata omitted the env and pip requirements; that inconsistency is the primary red flag here.
Capability Analysis
Type: OpenClaw Skill Name: polymarket-cybersecurity-trader Version: 0.0.3 The polymarket-cybersecurity-trader skill is a legitimate trading bot designed to execute trades on Polymarket based on cybersecurity event signals like CVE disclosures and ransomware trends. The implementation in trader.py is transparent, follows the strategy described in SKILL.md, and includes safety features such as a default paper-trading mode (venue='sim') and slippage safeguards. There are no signs of data exfiltration, malicious execution, or prompt injection; the code strictly interacts with the stated simmer-sdk and uses standard environment variables for configuration.
Capability Tags
cryptorequires-sensitive-credentials
Capability Assessment
Purpose & Capability
The skill's name, SKILL.md, and trader.py all describe a Polymarket cybersecurity trader and the requested runtime access to a Simmer trading API (SIMMER_API_KEY) is consistent with that purpose. However, the top-level registry metadata claimed no required env vars or install steps while clawhub.json and trader.py clearly require SIMMER_API_KEY and the simmer-sdk pip package. The mismatch between declared registry requirements and bundled files is incoherent.
Instruction Scope
SKILL.md and trader.py focus on market discovery, conviction sizing, and timing signals (Patch Tuesday). The instructions don't ask the agent to read unrelated system files, harvest credentials, or post data to unknown endpoints. The template wording 'Your agent provides the alpha' gives the agent latitude to supply signals, but that is not itself overbroad.
Install Mechanism
Registry metadata claimed 'No install spec — instruction-only', but clawhub.json lists a pip dependency ('simmer-sdk'). That means the skill will require installing a third-party Python package even though the registry said otherwise. This discrepancy should be clarified; installing pip packages is a higher-risk action than an instruction-only skill.
Credentials
trader.py directly reads os.environ['SIMMER_API_KEY'] and other SIMMER_* tunables; those are proportionate to a trading client but the registry initially advertised no required env vars. The single required secret (SIMMER_API_KEY) is expected for trading, but it is undeclared in the top-level metadata—this mismatch is the main proportionality issue.
Persistence & Privilege
always:false and autostart:false. The automaton entrypoint is managed but the skill does not request permanent/always-on inclusion or system-wide config changes. It does call apply_skill_config if available (to load tunables), which is normal for managed skills.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install polymarket-cybersecurity-trader
  3. After installation, invoke the skill by name or use /polymarket-cybersecurity-trader
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.0.3
SDK resilience: try/except runt apply_skill_config
v0.0.2
fix: add _client.live=True so --live actually routes to polymarket-venue for real USDC trades
v1.0.2
Fix apply_skill_config AttributeError for new Simmer SDK compatibility
v1.0.1
**Expanded structural edge logic and bias-driven conviction system:** - Introduces built-in "cyber_bias()" logic that weights markets by tractability (e.g., ransomware/sector, CVE/KEV, DDoS, legislation, attribution, physical outage) using public base rates and timing windows. - Now exploits Patch Tuesday effect: checks if CISA KEV additions or cyber event markets fall within 72 hours of Patch Tuesday, applying an automated bias multiplier without requiring any API connection. - Reworks signal sizing—conviction and bias multipliers determine trade size and prioritization, with built-in safeguards (spread, volume, days to resolution). - Much deeper breakdown of market inefficiencies, technical information asymmetry, and threat calendar effects for transparency and edge explanation. - Adds extensive documentation and justification for each bias multiplier and recommended signal remixing strategies—makes the template easier to extend or adapt.
v1.0.0
- Initial release of the Cybersecurity & Hacking Events Trader skill for Polymarket. - Scans and trades markets related to cyberattacks, ransomware, data breaches, zero-day exploits, and cybersecurity legislation using threat intelligence feeds. - Integrates with CISA's Known Exploited Vulnerabilities (KEV) catalog to detect major cybersecurity incidents before markets adjust. - Defaults to safe paper trading mode; live trading only enabled with a specific launch flag. - Fully documented risk parameters and credential requirements for secure configuration. - Built with simmer-sdk as its trading backend.
Metadata
Slug polymarket-cybersecurity-trader
Version 0.0.3
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 5
Frequently Asked Questions

What is Polymarket Cybersecurity Trader?

Trades Polymarket prediction markets on major cyberattacks, ransomware incidents, data breaches, zero-day exploits, and national cybersecurity legislation. E... It is an AI Agent Skill for Claude Code / OpenClaw, with 321 downloads so far.

How do I install Polymarket Cybersecurity Trader?

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

Is Polymarket Cybersecurity Trader free?

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

Which platforms does Polymarket Cybersecurity Trader support?

Polymarket Cybersecurity Trader is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Polymarket Cybersecurity Trader?

It is built and maintained by diagnostikon (@diagnostikon); the current version is v0.0.3.

💬 Comments