SKILLEMALL.ai

AC mcp-config

MCP server configuration and diagnostics. add - add server (scope selection + registration) [add.md], move - change server scope (project→local, local→user) [move.md], format - JSON format reference (differences per agent) [format.md], catalog - list of commonly used servers [catalog.md], diagnostics - connection failure diagnosis and troubleshooting [diagnostics.md]. Use when: "add MCP", "mcp-config", "MCP server config", "add context7", "MCP format", "MCP server list", "move MCP", "MCP scope", "scope change", "MCP connection failed", "MCP error", "Failed to reconnect", "code-mode not working", "MCP server issue".

ClawHub Agent Skills author: es6kr v0.3.2 MIT-0 9 files body ≈ 327 tokens Open the sourceclawhub.ai analyzed 4 d ago

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

AnalyzerAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
96/100
safety, quality, tests
Safety 60%
100
Quality 40%
90
Run on models
none yet
Process rating
C
50/100
Has gaps
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

    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: 9. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 50/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
    • 75Steps. 3 steps
    • 100Tools and files. No external tools needed
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 327 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

    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • +2Single-language instructions
    • +5Description quotes 14 example trigger phrases
    • +3Description length 622: enough signal without eating the budget
    • +4Structure: 4 headings
    • +3Step-by-step instructions: 3 items
    • +4Has examples (1 code blocks)
    • +1License stated

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

    External checks

    ClawHub: suspicious
    This MCP configuration skill is mostly coherent, but its PostgreSQL examples encourage unrestricted database access and inline credentials without enough warning.
    LLM: suspicious (high) · 18 Aug 2026