Skill Quality MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SKILL_DIRS | No | Additional skill search directories, separated by the system path separator | |
| SONAR_TOKEN | No | SonarQube token generated from My Account → Security | |
| SONAR_SCANNER | No | Full path to sonar-scanner when it is not on PATH | |
| SONAR_HOST_URL | No | SonarQube server URL, e.g. http://localhost:9000; for SonarCloud use https://sonarcloud.io | |
| SONAR_PROJECT_KEY | No | Default SonarQube project key; can be overridden by tool parameters | |
| SONAR_ORGANIZATION | No | SonarCloud organization (only required for SonarCloud) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_skillsA | 列出本机 Agent Skills(Cursor、Codex、Claude 用户目录、插件、SKILL_DIRS),区分同名冲突与镜像。 query:按名称/描述过滤,结果带描述和路径。extra_dirs:额外目录,逗号分隔。detail:全部带描述。 |
| inspect_skillB | 检查一个 Agent Skill 的结构:frontmatter、正文长度、失效链接/锚点、文中引用的文件。skill:技能名或路径。 |
| analyze_dependenciesA | 依赖分析:Python(requirements/pyproject)、npm(package.json,含 monorepo)、Maven、Gradle、Go modules、Composer、NuGet。 检查包装没装、用了没声明、声明了没用、重复声明、循环依赖、外部命令是否在 PATH。 check_vulnerabilities:联网查 OSV 漏洞(按锁文件 / 已装版本)。detail:列出每个包的版本、使用文件和全部漏洞编号。 |
| code_quality_scanA | 本地 Bug 与代码质量扫描(无需 SonarQube):Python、JS/TS、React、Vue、Svelte、Java、Kotlin、Go、C#、PHP, 外加 Spring/.NET 配置里写死的密码和 MyBatis ${} 拼接;给出 Bug、漏洞、安全热点、异味、复杂度、重复、技术债和 A–E 评级。 use_linters:合并已装的 ruff、项目里的 ESLint(会加载项目的 ESLint 配置)、go vet。max_issues:简版列出的重要问题条数。detail:列出全部问题。 |
| sonar_check_connectionA | 检查 SonarQube/SonarCloud 配置、连通性、令牌和 sonar-scanner 是否可用。 |
| sonar_issuesA | 拉取 SonarQube 未解决问题。types:BUG,VULNERABILITY,CODE_SMELL;severities:BLOCKER..INFO,空为全部; project_key 空则用 SONAR_PROJECT_KEY。 |
| sonar_project_metricsC | SonarQube 项目指标:质量门禁、三项评级、Bug/漏洞/异味数、覆盖率、重复率。 |
| sonar_run_scanB | 用 sonar-scanner 扫描并上传到 SonarQube,等待分析完成。没装扫描器可 use_npx=true(首次会下载)。 |
| full_quality_reportA | 一站式报告:Skill 结构(目标是技能时)+ 依赖 + 本地扫描 + SonarQube,给出 通过/有警告/未通过。 sonar:auto=已配置就拉结果,scan=先扫描再拉,off=不用。check_vulnerabilities:联网查 OSV。 detail:返回完整报告。save_to:完整报告另存路径(.md)。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| review_skill | 让 Agent 生成质量报告并按严重度修复问题。 |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Most tools have clearly distinct purposes: skill listing/inspection, dependency analysis, local scanning, and a cohesive sonar_* cluster. Some overlap exists between code_quality_scan and sonar_issues (both surface bugs) and between sonar_issues and sonar_project_metrics, and full_quality_report aggregates the others, but descriptions clarify local vs. Sonar and aggregate vs. individual.
All snake_case throughout, with a predictable pattern: list_/inspect_/analyze_ verbs, sonar_-prefixed cluster, and full_quality_report. Minor deviation where code_quality_scan and sonar_project_metrics use noun-adjective ordering rather than verb_noun, but the grouping remains readable.
Nine tools is well within the ideal 3-15 range and each earns its place across skill, dependency, local scan, and Sonar workflows. The aggregate report tool is arguably redundant with the individual tools, but it serves a distinct one-shot use case.
The surface covers the full quality-check lifecycle: discover skills, inspect structure, analyze dependencies, scan locally, configure and query Sonar, and produce a consolidated pass/fail report. Minor gaps exist (e.g. no dedicated tool to fix or auto-remediate skill structure issues, no cross-skill content search), but core workflows have no dead ends.