SKILLEMALL.ai
GitHub ↗ RU Sign in

FC yuyonghao-mcp-client

(no description)

Blockedguard blocked the skill: signs of malicious behaviour
ClawHub Agent Skills author: yuyonghao-123 v0.1.1 MIT-0 15 files body ≈ 1 386 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureGitHubAI and agentsInfrastructuretype 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
F
6/100
safety, quality, tests
Safety 60%
10
Quality 40%
0
Run on models
none yet
Process rating
C
51/100
Has gaps
Result and completion w 14
0
When it triggers w 12
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten
Guard blocked this skill: critical findings below. Do not install it until the author fixes them.

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. Remove the critical guard findings (secrets, dangerous commands, hidden instructions): while they stand the skill is blocked and cannot grade above F.
  2. Add a description to the frontmatter: without it the skill never triggers.
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

  • critical Secrets in code secret-github-token src/mcp-config.json:25
    GitHub token (quoted — discussed, not commanded)
    "GITHUB_TOKEN": "ghp_…rTC"
    quoted
Medium and low: 6
  • low Secrets in code secret-high-entropy-token package-lock.json:74
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…GLi+2W/6ao+6Y7gu/RCwR…Kng==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:253
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…GLw+xYSd…cqA==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:308
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…FrF+LTRo…W3g==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:317
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…A6j+hAmM…GbS+kf5c…csw==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:326
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…5bm+c2gQ…aG5+esrLODihIorn+Pe6F…dXA==",
    detector
  • low Secrets in code secret-high-entropy-token src/mcp-config.json:25
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "GITHUB_TOKEN": "ghp_…rTC"
    quoted

Files scanned: 10. 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

Process rating: all ten parameters 51/100

  • 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
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 100Tools and files. No external tools needed
  • 100Steps. 24 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1386 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 0: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • -2localhost URLs: will not work for another user
  • +1No license
  • +2Single-language instructions
  • +4Structure: 20 headings
  • +3Step-by-step instructions: 24 items
  • +4Has examples (10 code blocks)

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

External checks

ClawHub: suspicious
The skill is a plausible MCP client, but it ships with a hardcoded GitHub token and its advertised approval controls do not actually block sensitive actions.
LLM: suspicious (high) · VirusTotal: · 28 May 2026