skill-lint
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lint_skillsA | Lint agent SKILL.md files in one or more directories. Reports missing or untriggerable descriptions, name/directory mismatches, oversized bodies, broken file references, duplicate skill names, and pairs of skills too similar for a model to choose between. Use when auditing a skill library, before publishing a skill, or when a skill exists but never seems to get invoked. |
| lint_mcp_toolsA | Lint an MCP tool schema — pass the JSON from a tools/list response or a bare array of tool objects. Reports missing descriptions, destructive tools with no confirmation gate, unconstrained free-form parameters that widen prompt-injection surface, duplicate tool names, and the per-request token cost of the whole tool list. Use when designing or reviewing an MCP server. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools are cleanly separated by input target: lint_skills operates on SKILL.md files/directories, while lint_mcp_tools operates on MCP tool schema JSON. There is no realistic way to confuse the two, since each description names a distinct artifact and use case.
Both names follow an identical verb_noun pattern (lint_skills, lint_mcp_tools) with consistent snake_case and a shared 'lint_' prefix that signals the server's purpose. Fully predictable.
Two tools map directly to the server's two linting domains, so each earns its place and the surface is tightly scoped. It is slightly thin—there is no config, list, or fix operation—but not unreasonably so for a focused linter.
The linter covers both advertised domains and reports a broad range of issues (descriptions, naming, size, duplicates, similarity, token cost). Missing auto-fix or rule-configuration operations are minor gaps an agent can work around.