SKILLEMALL.ai
GitHub ↗ RU Sign in

BC polyclaw

Become an autonomous prediction market trader on Polymarket with AI-powered analysis and a performance-backed token on Base. Trade real markets, build a track record, and let the buyback flywheel run.

modbender/skill-library-mcp Agent Skills author: modbender MIT 8 files · 3 scripts body ≈ 8 334 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Become an autonomous prediction market trader on Polymarket with AI-powered analysis and a performance-backed token on Base.

As a process C 59/100 · Has gaps — weak spots: when it triggers, execution cost, running it twice

AnalyzerAI and agentstype 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%
98
Quality 40%
65
Run on models
none yet
Process rating
C
59/100
Has gaps
Progress reporting w 2
0
When it triggers w 12
20
Running it twice w 4
30
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.
  2. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
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 · 2

✓ No critical or high findings

Medium and low: 2
  • low Exfiltration net-credential-use scripts/register.sh:237
    Credential used in a network call (verify the destination is the intended service) (quoted — discussed, not commanded)
    echo "     curl \"$API_BASE/agents/$AGENT_ID/positions\" -H \"Authorization: Bearer \$AGENT_API_KEY\""
    quoted
  • low Exfiltration net-credential-use scripts/register.sh:238
    Credential used in a network call (verify the destination is the intended service) (quoted — discussed, not commanded)
    echo "     curl \"$API_BASE/agents/$AGENT_ID/metrics\" -H \"Authorization: Bearer \$AGENT_API_KEY\""
    quoted

Files scanned: 8. 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")
  • warning body-long SKILL.md body ≈ 8334 tokens (recommended < 5000); move details to references/
  • note frontmatter-key unknown frontmatter key "requirements"

Process rating: all ten parameters 59/100

  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 9 mutating operations with no state check
  • 40Execution cost. Instruction body is 8334 tokens: crowds the task out of the window
  • 50Failures and branches. 0 branches, has a failure section
  • 60Tools and files. Uses tools (web) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 85Steps. 125 steps, 2 vague phrases
  • 100Consistency. Name and required fields are in place
  • low 20 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)
  • -33 of 3 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +3Description length 200: enough signal without eating the budget
  • +4Structure: 78 headings
  • +3Step-by-step instructions: 125 items
  • +3Output format is stated explicitly
  • +4Has examples (39 code blocks)
  • +4Reference files are cited in the instructions (4 of 4)

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