SKILLEMALL.ai

DF tmp

(no description)

Not recommendedcritical or high security findings · low grade D
modbender/skill-library-mcp Agent Skills author: modbender MIT 15 files body ≈ 2 853 tokens Open the sourcegithub.com analyzed 3 d ago

统一入口和智能路由中心,自动识别用户意图并路由到相应技能。基于 Cue 产品设计,提供专业化的深度研究体验。 本 Skill 是一个具有持久化状态和后台行为的金融研究+监控工具:

As a process F 35/100 · Will not run — References files that are not bundled: scripts/cue.sh, scripts/research.sh, scripts/notifier.sh

ProcedureInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
D
46/100
safety, quality, tests
Safety 60%
76
Quality 40%
0
Run on models
none yet
Process rating
F
35/100
Will not run
References files that are not bundled: scripts/cue.sh, scripts/research.sh, scripts/notifier.sh
Tools and files w 18
0
Result and completion w 14
0
When it triggers w 12
0
the three weakest of ten parameters · all ten

What is at stake

The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.

Dangerous commands
If you install

The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.

For the author

Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.

How to improve

  1. Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
  2. Add a description to the frontmatter: without it the skill never triggers.
  3. 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 · 3

  • high Dangerous commands cmd-persistence README.md:90
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    cat cue/crontab.txt | crontab -
Medium and low: 2
  • medium Dangerous commands cmd-persistence README.md:174
    Persistence mechanism (cron / launchd / scheduled task / autorun registry) (documentation table row)
    | 监控不执行 | crontab 未设置 | 执行 `crontab crontab.txt` |
    table
  • low Dangerous commands cmd-cron-mention README.md:93
    Mentions editing / listing crontab
    crontab -l

Files scanned: 15. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • error frontmatter SKILL.md: no YAML frontmatter block found
  • error name-missing SKILL.md: frontmatter has no `name`
  • error description-missing SKILL.md: no `description` — the skill can never trigger
  • warning missing-ref reference to a missing file: scripts/cue.sh
  • warning missing-ref reference to a missing file: scripts/research.sh
  • warning missing-ref reference to a missing file: scripts/notifier.sh
  • warning missing-ref reference to a missing file: scripts/cuecue-client.js
  • warning missing-ref reference to a missing file: scripts/create-monitor.sh
  • warning missing-ref reference to a missing file: scripts/monitor-daemon.sh
  • warning missing-ref reference to a missing file: scripts/monitor-notify.sh
  • warning missing-ref reference to a missing file: scripts/executor/monitor-engine.sh
  • warning missing-ref reference to a missing file: scripts/executor/search-executor.sh
  • warning missing-ref reference to a missing file: scripts/executor/browser-executor.sh

Process rating: all ten parameters 35/100

Will not run. References files that are not bundled: scripts/cue.sh, scripts/research.sh, scripts/notifier.sh
  • 0Tools and files. 10 referenced file(s) missing: scripts/cue.sh, scripts/research.sh, scripts/notifier.sh
  • 0Result and completion. Does not say what the result is
  • 0When it triggers. No condition that starts the skill
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 8 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 100Steps. 103 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2853 tokens

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 0: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • -244 emoji in the instructions: noise for the model
  • +1No license
  • +2Single-language instructions
  • +4Structure: 30 headings
  • +3Step-by-step instructions: 103 items
  • +4Has examples (13 code blocks)

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