SKILLEMALL.ai
GitHub ↗ RU Sign in

BC polymarket-news-monitor

Monitor official Polymarket sources (The Oracle blog, API status) for important updates, security alerts, and breaking news. Automatic importance scoring with instant notifications for critical events.

modbender/skill-library-mcp Agent Skills author: modbender MIT 3 files body ≈ 1 163 tokens Open the sourcegithub.com↗ analyzed 3 d ago

Monitor official Polymarket sources (The Oracle blog, API status) for important updates, security alerts, and breaking news.

As a process C 61/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches

IntegrationSoftware developmentInfrastructureWriting and documentstype 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
84/100
safety, quality, tests
Safety 60%
92
Quality 40%
71
Run on models
none yet
Process rating
C
61/100
Has gaps
Inputs and preconditions w 11
0
Failures and branches w 10
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Risky intent medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The purpose itself is risky: wallets, browser password stores, offensive security. Even an honest implementation gives the agent access to things that cost money.

For the author

Explain in the description why the access is needed and how it is limited; add tests that show refusals on dangerous requests.

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 · 4

✓ No critical or high findings

Medium and low: 4
  • medium Risky intent intent-wallet-secrets SKILL.md:101
    Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target
    - private key, seed phrase, credential, attack
  • low Risky intent intent-wallet-secrets scripts/polymarket-monitor.py:52
    Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target (quoted — discussed, not commanded)
    "private key", "seed phrase", "password", "credential",
    quoted

A further 2 matches are quotations in this security skill's documentation and are not counted as findings.

Files scanned: 3. 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 61/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 1 mutating operations with no state check
  • 60Result and completion. Output format stated, no completion criterion
  • 100Tools and files. No external tools needed
  • 100Steps. 22 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1163 tokens
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 11 top-level sections: this looks like several domains in one skill

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)
  • -5TODO / placeholder text left in the skill
  • -216 emoji in the instructions: noise for the model
  • +1No license
  • +2Single-language instructions
  • +3Description length 201: enough signal without eating the budget
  • +4Structure: 24 headings
  • +3Step-by-step instructions: 22 items
  • +3Output format is stated explicitly
  • +4Has examples (5 code blocks)
  • +3All 1 scripts are documented

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