SKILLEMALL.ai
GitHub ↗ RU Sign in

AC glab-mcp

Work with Model Context Protocol (MCP) server for AI assistant integration. Exposes GitLab features as tools for AI assistants (like Claude Code) to interact with projects, issues, merge requests, and pipelines. Use when integrating AI assistants with GitLab or working with MCP servers. Triggers on MCP, Model Context Protocol, AI assistant integration, glab mcp serve.

modbender/skill-library-mcp Agent Skills author: modbender MIT 2 files body ≈ 626 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Work with Model Context Protocol (MCP) server for AI assistant integration.

As a process C 53/100 · Has gaps — weak spots: steps, inputs and preconditions, failures and branches

IntegrationGitLabAI 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
95/100
safety, quality, tests
Safety 60%
100
Quality 40%
88
Run on models
none yet
Process rating
C
53/100
Has gaps
Steps w 15
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: 2. 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 53/100

    • 0Steps. Prose only: no discrete steps
    • 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
    • 60Result and completion. Output format stated, no completion criterion
    • 70When it triggers. States when to use, but not when not to
    • 100Tools and files. No external tools needed
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 626 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

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • +3No numbered steps or checklist
    • +1No license
    • +2Single-language instructions
    • +3Description length 370: enough signal without eating the budget
    • +4Structure: 7 headings
    • +3Output format is stated explicitly
    • +4Has examples (2 code blocks)
    • +4Reference files are cited in the instructions (1 of 1)

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