SKILLEMALL.ai
GitHub ↗ RU Sign in

CD youbaolian

Manage youbaolian, orders, users, organ REST API.

Not recommendedcritical or high security findings
modbender/skill-library-mcp Agent Skills author: modbender MIT 2 files body ≈ 325 tokens Open the sourcegithub.com↗ analyzed 3 d ago

Manage youbaolian, orders, users, organ REST API.

As a process D 39/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

IntegrationSecuritytype 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
C
72/100
safety, quality, tests
Safety 60%
76
Quality 40%
65
Run on models
none yet
Process rating
D
39/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

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.

Secrets in code
If you install

The files contain someone else's key or token. If it is live, your agent will call third-party services under a stranger's identity; if it was revoked, the skill's scripts simply fail. Such a key often arrives with the author's whole workspace, personal data included.

For the author

The key is visible to everyone who downloaded the skill and has likely been copied by catalog-scanning bots already. Revoke it now, check bills and access logs, then reissue.

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. 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 · 7

  • high Secrets in code meta-credential-files credentials.json
    Credential / dotenv files bundled with the skill (1)
    credentials.json
Medium and low: 6
  • low Obfuscation obf-base64-blob credentials.json:5
    Long base64-looking blob (quoted — discussed, not commanded)
    "encryption": "1W2V…wiT+fW9h…a2o+VTUr…gkV+j/kqY2…zym+GFJM…EfM="
    quoted
  • low Secrets in code secret-high-entropy-token credentials.json:5
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "encryption": "1W2V…wiT+fW9h…a2o+VTUr…gkV+j/kqY2…zym+GFJM…EfM="
    quoted
  • low Obfuscation obf-base64-blob SKILL.md:18
    Long base64-looking blob (quoted — discussed, not commanded)
    "encryption": "1W2V…wiT+fW9h…a2o+VTUr…gkV+j/kqY2…zym+GFJM…EfM="
    quoted
  • low Secrets in code secret-high-entropy-token SKILL.md:18
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "encryption": "1W2V…wiT+fW9h…a2o+VTUr…gkV+j/kqY2…zym+GFJM…EfM="
    quoted
  • low Obfuscation obf-base64-blob SKILL.md:26
    Long base64-looking blob (quoted — discussed, not commanded)
    export YBL_ENCRYPTION="1W2V…wiT+fW9h…a2o+VTUr…gkV+j/kqY2…zym+GFJM…EfM="
    quoted
  • low Secrets in code secret-high-entropy-token SKILL.md:26
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    export YBL_ENCRYPTION="1W2V…wiT+fW9h…a2o+VTUr…gkV+j/kqY2…zym+GFJM…EfM="
    quoted

Files scanned: 2. 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 "homepage"

Process rating: all ten parameters 39/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
  • 50Steps. 2 steps
  • 60Tools and files. Uses tools (web) that frontmatter does not declare
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 325 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 49: 120–800 characters recommended
  • +3No numbered steps or checklist
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 4 headings
  • +4Has examples (4 code blocks)

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