SKILLEMALL.ai

FB minimax-coding-plan-tool

MiniMax Token Plan工具 - 支持图片生成、图像理解、语音合成和视频生成。直接调用MiniMax官方API,纯JavaScript实现,无需外部MCP服务器。

Blockedguard blocked the skill: signs of malicious behaviour
ClawHub Agent Skills author: yongjie666888 v1.0.4 MIT-0 4 files body ≈ 1 000 tokens Open the sourceclawhub.ai analyzed 4 d ago

As a process B 65/100 · Nearly there — weak spots: when it triggers, failures and branches, consistency

ReferenceSoftware developmentInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
F
35/100
safety, quality, tests
Safety 60%
10
Quality 40%
72
Run on models
none yet
Process rating
B
65/100
Nearly there
Failures and branches w 10
0
Progress reporting w 2
0
When it triggers w 12
20
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. 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 · 1

  • critical Secrets in code secret-openai-key SKILL.md:56
    OpenAI-style API key (quoted — discussed, not commanded)
    openclaw config set skills.entries.minimax-coding-plan-tool.apiKey "sk-c…Bv8"
    quoted

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")

Process rating: all ten parameters 65/100

  • 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 (minimax-coding-plan-tool) differs from the folder (minimax-coding-plan-tool-yongjie)
  • 60Result and completion. Output format stated, no completion criterion
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Tools and files. No external tools needed
  • 100Steps. 9 steps
  • 100Execution cost. Instruction body is 1000 tokens
  • 100Running it twice. No mutating operations
  • low 25 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 87: 120–800 characters recommended
  • +1No license
  • +2Single-language instructions
  • +4Structure: 36 headings
  • +3Step-by-step instructions: 9 items
  • +3Output format is stated explicitly
  • +4Has examples (16 code blocks)

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

External checks

ClawHub: suspicious
This MiniMax wrapper mostly does what it says, but it includes unsafe credential guidance and some capability/documentation mismatches users should review before installing.
LLM: suspicious (high) · VirusTotal: · 29 May 2026