SKILLEMALL.ai
GitHub ↗ RU Sign in

AC rollhub-bot-builder

Build and deploy autonomous gambling bots for Telegram, Discord, and Twitter using Agent Casino API. Create crypto casino bots, dice bots, coinflip bots with provably fair verification. Bot templates for python-telegram-bot, Discord.js, Twitter API. Automated betting, slash commands, inline keyboards, tweet results. Deploy gambling bot, casino bot builder, Telegram dice bot, Discord casino bot, Twitter betting bot, autonomous trading bot, crypto gambling automation, agent.rollhub.com API integration, real-time bet notifications, provably fair bot.

modbender/skill-library-mcp Agent Skills author: modbender MIT 5 files · 1 script body ≈ 901 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Build and deploy autonomous gambling bots for Telegram, Discord, and Twitter using Agent Casino API.

As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

GeneratorDiscordTelegramAI and agentsInfrastructuretype 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
A
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
79
Run on models
none yet
Process rating
C
51/100
Has gaps
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 · 0

✓ No critical or high findings

Files scanned: 5. 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 51/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. 6 mutating operations with no state check
  • 100Tools and files. No external tools needed
  • 100Steps. 21 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 901 tokens
  • low The response is described with custom markup (3 tags): a typed call is more reliable

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 553: enough signal without eating the budget
  • +4Structure: 13 headings
  • +3Step-by-step instructions: 21 items
  • +4Has examples (5 code blocks)
  • +4Reference files are cited in the instructions (3 of 3)
  • +3All 1 scripts are documented

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