SKILLEMALL.ai
GitHub ↗ RU Sign in

BF jisilu-cb-daily

每日从集思录抓取可转债基本数据、强赎倒计时、下修倒计时，支持Cookie管理和本地持久化存储

ClawHub Agent Skills author: ccHunter v1.0.0 MIT-0 4 files body ≈ 1 251 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process F 31/100 · Will not run — References files that are not bundled: references/cookie.json

ProcedureInfrastructuretype 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
86/100
safety, quality, tests
Safety 60%
99
Quality 40%
66
Run on models
none yet
Process rating
F
31/100
Will not run
References files that are not bundled: references/cookie.json
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 · 1

✓ No critical or high findings

Medium and low: 1
  • low Dangerous commands cmd-cron-mention README.md:60
    Mentions editing / listing crontab
    # crontab -e

Files scanned: 4. 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 missing-ref reference to a missing file: references/cookie.json

Process rating: all ten parameters 31/100

Will not run. References files that are not bundled: references/cookie.json
  • 0Tools and files. 1 referenced file(s) missing: references/cookie.json
  • 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 (jisilu-cb-daily) differs from the folder (jisulu-cb-daily)
  • 100Steps. 47 steps
  • 100Execution cost. Instruction body is 1251 tokens
  • 100Running it twice. No mutating operations

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 46: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 19 headings
  • +3Step-by-step instructions: 47 items
  • +4Has examples (9 code blocks)
  • +3All 1 scripts are documented

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

External checks

ClawHub: suspicious
The skill appears purpose-built for authenticated Jisilu automation, but it asks users to provide and persist a live browser session cookie without enough safeguards.
LLM: suspicious (medium) · VirusTotal: · 29 May 2026