SKILLEMALL.ai
GitHub ↗ RU Sign in

BF lottery-predictor-v2.15

基于 V2.15 数学模型的双色球预测工具，包含均值回归、正态分布、大数定律、卡方检验等 7 种算法，提供红球 TOP10 和蓝球 TOP4 推荐。

ClawHub Agent Skills author: mumuli2021 v2.15.0 MIT-0 15 files · 1 script body ≈ 493 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process F 31/100 · Will not run — References files that are not bundled: scripts/verify_prediction.py, scripts/backtest.py, references/v2.15_documentation.md

ReferenceInfrastructuretype 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
80/100
safety, quality, tests
Safety 60%
100
Quality 40%
50
Run on models
none yet
Process rating
F
31/100
Will not run
References files that are not bundled: scripts/verify_prediction.py, scripts/backtest.py, references/v2.15_documentation.md
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
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.
  2. The text references files that are not there: add them or drop the references.
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: 15. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning missing-ref reference to a missing file: scripts/verify_prediction.py
  • warning missing-ref reference to a missing file: scripts/backtest.py
  • warning missing-ref reference to a missing file: references/v2.15_documentation.md

Process rating: all ten parameters 31/100

Will not run. References files that are not bundled: scripts/verify_prediction.py, scripts/backtest.py, references/v2.15_documentation.md
  • 0Tools and files. 3 referenced file(s) missing: scripts/verify_prediction.py, scripts/backtest.py, references/v2.15_documentation.md
  • 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
  • 40Consistency. Frontmatter name (lottery-predictor-v2.15) differs from the folder (lottery-predictor-v2-15)
  • 100Steps. 53 steps
  • 100Execution cost. Instruction body is 493 tokens
  • 100Running it twice. No mutating operations
  • 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)
  • +3Description length 74: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • -31 of 2 scripts are never mentioned in SKILL.md
  • +2Single-language instructions
  • +4Structure: 23 headings
  • +3Step-by-step instructions: 53 items
  • +4Has examples (3 code blocks)
  • +1License stated

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

External checks

ClawHub: suspicious
The lottery predictor mostly matches its purpose, but it ships unrelated publishing automation that could use a user’s ClawHub account if run.
LLM: suspicious (high) · VirusTotal: · 29 May 2026