SKILLEMALL.ai

AD mindsdb-mcp-skill

MindsDB MCP服务器交互技能,用于通过自然语言查询和操作200+企业级数据源。当用户需要查询数据库、分析数据、创建AI模型、连接数据源(MySQL、PostgreSQL、MongoDB、Excel、CSV、Gmail、Slack等)、执行SQL查询、进行数据预测、构建知识库(RAG)、智能问答、文档检索或任何与数据库交互的任务时使用此技能。即使没有明确提到MindsDB,只要涉及数据库操作、数据分析、数据查询、知识库构建、AI问答或需要连接多个数据源的场景,都应该使用此技能。

LeoYeAI/openclaw-master-skills Agent Skills author: LeoYeAI MIT 17 files body ≈ 2 417 tokens Open the sourcegithub.com analyzed 3 d ago

MindsDB…

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

ProcedurePostgreSQLMySQLMongoDBSlackAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
90/100
safety, quality, tests
Safety 60%
99
Quality 40%
76
Run on models
none yet
Process rating
D
46/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

How to improve

  1. 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
  • 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 Secrets in code secret-high-entropy-token references/knowledge-base.md:570
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    - 多语言: `para…-v2`
    quoted

Files scanned: 16. 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 46/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
  • 60Tools and files. Uses tools (python) that frontmatter does not declare
  • 100Steps. 303 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2417 tokens
  • 100Running it twice. No mutating operations
  • low 13 top-level sections: this looks like several domains in one skill
  • medium 20 test cases, all positive: not one "should refuse" or "should ask first"
  • low No test case covers injection arriving through data

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)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 244: enough signal without eating the budget
  • +4Structure: 64 headings
  • +3Step-by-step instructions: 303 items
  • +4Has examples (6 code blocks)
  • +4Reference files are cited in the instructions (9 of 9)

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