SKILLEMALL.ai
GitHub ↗ RU Sign in

AC mcp-integration-pro

Unlock the full potential of your AI agent with Model Context Protocol (MCP) integration. This capability connects your agent to a vast ecosystem of external tools, APIs, and data sources through multiple MCP servers—including legal databases, weather services, database connectors, and more. By centralizing access, it enables dynamic tool discovery and execution, enhancing flexibility, reliability, and real-time data retrieval. Empower your agent to adapt and perform across diverse domains with robust, scalable integration. box burroughs candidate fjord external php perhaps ljubljana untitled hence michigannto capability sidekick architecture

ClawHub Agent Skills author: Subaru0573 v1.0.0 MIT-0 13 files body ≈ 1 715 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

Unlock the full potential of your AI agent with Model Context Protocol (MCP) integration.

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

IntegrationAI and agentstype 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
A
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
80
Run on models
none yet
Process rating
C
53/100
Has gaps
Inputs and preconditions w 11
0
Progress reporting w 2
0
When it triggers w 12
20
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
  • 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 · 0

✓ No critical or high findings

Files scanned: 13. 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 53/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 40Consistency. Frontmatter name (mcp-integration-pro) differs from the folder (super-mcp-integration-1-0-0)
  • 50Failures and branches. 0 branches, has a failure section
  • 60Tools and files. Uses tools (bash) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 85Steps. 50 steps, 1 vague phrases
  • 100Execution cost. Instruction body is 1715 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)
  • +2Single-language instructions
  • +3Description length 650: enough signal without eating the budget
  • +4Structure: 29 headings
  • +3Step-by-step instructions: 50 items
  • +3Output format is stated explicitly
  • +4Has examples (13 code blocks)
  • +4Reference files are cited in the instructions (5 of 5)
  • +1License stated

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

External checks

ClawHub: suspicious
The plugin appears to do what it advertises, but it gives agents broad power to invoke connected external MCP tools and needs careful review before use.
LLM: suspicious (high) · 29 Jun 2026