SKILLEMALL.ai
GitHub ↗ RU Sign in

BD polymarket-cybersecurity-trader

Trades Polymarket prediction markets on major cyberattacks, ransomware incidents, data breaches, zero-day exploits, and national cybersecurity legislation. Exploits two structural edges — technical information asymmetry (retail cannot read CISA KEV advisories or Verizon DBIR base rates) and the Patch Tuesday timing window (CISA adds the most KEV entries in the 72 hours post-Patch-Tuesday; Polymarket reprices with a 6–12 hour lag).

ClawHub Agent Skills author: diagnostikon v0.0.3 MIT-0 4 files body ≈ 2 381 tokens Open the sourceclawhub.ai↗ analyzed 4 d ago

As a process D 43/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
85/100
safety, quality, tests
Safety 60%
94
Quality 40%
72
Run on models
none yet
Process rating
D
43/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 6

✓ No critical or high findings

Medium and low: 6
  • low Risky intent intent-offensive-security skill-card.md:2
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    Trades Polymarket prediction markets on major cyberattacks, ransomware incidents, data breaches, zero-day exploits, and national cybersecurity legislation using cybersecurity-specific timing and tract
  • low Risky intent intent-offensive-security SKILL.md:3
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    description: Trades Polymarket prediction markets on major cyberattacks, ransomware incidents, data breaches, zero-day exploits, and national cybersecurity legislation. Exploits two structural edges —
  • low Risky intent intent-offensive-security SKILL.md:41
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    | Ransomware attack on named group / sector milestone | **1.25x** | Ransomware.live tracks victims in real time; Verizon DBIR documents sector frequencies; healthcare is ~35% of all ransomware targets
  • low Risky intent intent-offensive-security SKILL.md:58
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    | Ransomware question + Q1 or Q4 (Jan–Mar / Oct–Dec) | **1.15x** | Verizon DBIR documents peak ransomware frequency: Q1 (holiday staffing debt) and Q4 (end-of-year pressure) |
  • low Risky intent intent-offensive-security SKILL.md:75
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (documentation table row)
    | "Will healthcare sector ransomware attacks exceed 500 in Q1?" — January | 1.25x | 1.15x (Q1 peak) | **1.35x cap** |
    table
  • low Risky intent intent-offensive-security SKILL.md:85
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    cyberattack, ransomware, data breach, hack, zero-day, malware,

Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 43/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 4 mutating operations with no state check
  • 60Tools and files. Uses tools (python) that frontmatter does not declare
  • 100Steps. 19 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2381 tokens
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 434: enough signal without eating the budget
  • +4Structure: 12 headings
  • +3Step-by-step instructions: 19 items
  • +4Has examples (1 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.

External checks

ClawHub: clean
This is a disclosed Polymarket trading skill that defaults to paper trading and only uses live trading when explicitly run with the live flag.
LLM: benign (high) · VirusTotal: · 29 May 2026