SKILLEMALL.ai
GitHub ↗ RU Sign in

AD lucky-today

离线每日运势 — 输出幸运方位/颜色/数字/物品/宜忌,支持今日/明日/本周/本月、双人合盘、面试/考试/相亲/上线/出差等场景化运势,中英双语,可定时推送 Telegram/Feishu。Daily luck oracle with bilingual output, multi-horizon (today/weekly/monthly), couple readings, and scenario-specific fortunes. No external API.

ClawHub Agent Skills author: jiajiaoy v0.1.0 MIT-0 9 files body ≈ 1 527 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process D 49/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, failures and branches

IntegrationTelegramInfrastructuretype 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
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
75
Run on models
none yet
Process rating
D
49/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 · 0

✓ No critical or high findings

Files scanned: 9. 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")
  • note frontmatter-key unknown frontmatter key "keywords"

Process rating: all ten parameters 49/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
  • 30Running it twice. 1 mutating operations with no state check
  • 60Tools and files. Uses tools (bash) that frontmatter does not declare
  • 70When it triggers. States when to use, but not when not to
  • 100Steps. 35 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1527 tokens
  • 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)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 239: enough signal without eating the budget
  • +4Structure: 13 headings
  • +3Step-by-step instructions: 35 items
  • +4Has examples (3 code blocks)
  • +4Reference files are cited in the instructions (5 of 5)

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

External checks

ClawHub: clean
This is a prompt-only offline fortune skill; its main risk is optional local profile storage if the user asks it to remember personal details.
LLM: benign (high) · VirusTotal: · 29 May 2026