skill-lint
Lint agent SKILL.md files and MCP tool schemas to catch issues like missing descriptions, similar skills, unconstrained parameters, and destructive tools without confirmation gates.
README
skill-lint
Lint agent SKILL.md files and MCP tool schemas.
Agent skills and MCP tools rarely fail loudly. They fail by never being chosen —
a description that never says when to use it, two tools the model can't tell
apart, a schema so verbose it costs you tokens on every single turn. skill-lint
finds those, plus the ones that bite harder: a destructive tool with no
confirmation gate, an unconstrained command parameter, a skill pointing at a
file that isn't there.
Zero dependencies. Runs as a CLI or as an MCP server.
uv tool install skill-lint # or: pipx install skill-lint
skill-lint ~/.claude/skills # lint a skill library
skill-lint --mcp tools.json # lint an MCP tools/list payload
skill-lint . --format github # CI annotations
Example
$ skill-lint ~/.claude/skills
skills/report-writer/SKILL.md
▲ SL007 description never says WHEN to use the skill — Generates polished reports…
→ Add an explicit trigger clause: "Use when …", "Triggers on …". This is the
single most common reason a working skill never gets invoked.
▲ SL011 references a missing file — templates/quarterly.md
→ The model will try to read this and fail.
197 checked · 1 error(s) · 129 warning(s) · 75 info
As an MCP server
// claude_desktop_config.json / .mcp.json
{
"mcpServers": {
"skill-lint": { "command": "skill-lint-mcp" }
}
}
Exposes lint_skills and lint_mcp_tools. The server speaks the MCP stdio
protocol directly — no SDK, so it starts in milliseconds and adds nothing to
your dependency tree.
Rules
Skills
| Code | Severity | What it catches |
|---|---|---|
| SL001 / SL002 | error | Missing name / description |
| SL003 | warn | name doesn't match its directory (breaks invocation) |
| SL004 | warn | Name isn't kebab-case, or is over 64 chars |
| SL005 / SL006 | warn | Description too short to route on / long enough to cost real tokens |
| SL007 | warn | Description never says when to use the skill |
| SL008 | info | Description written in first person |
| SL009 | warn/error | Skill body large enough to bloat every load |
| SL010 | error | Frontmatter with no body |
| SL011 | warn | Links to or runs a file that doesn't exist |
| SL012 | error | Two skills share a name — one silently shadows the other |
| SL013 | error | Frontmatter doesn't parse |
| SL014 | info | Unrecognised frontmatter keys (usually typos) |
| SL016 | warn | Two descriptions so similar the model can't choose between them |
SL007 is the one that matters most. On a real 197-skill library it fired 116 times — most skills describe what they are and never say when to reach for them, so the router never picks them and the author assumes the skill is fine.
Trigger detection is English-first. Descriptions that don't look English are
reported at info rather than warn, since the heuristic can't judge them.
MCP tools
| Code | Severity | What it catches |
|---|---|---|
| MC001 | error/warn | Tool has no description, or one too short to route on |
| MC002 | warn | Parameter has no description |
| MC003 | error | Destructive tool with no confirmation gate |
| MC004 | warn | Unconstrained free-form command/path/query — injection surface |
| MC005 | info | Tool name isn't snake_case |
| MC006 | warn | Description long enough to matter, paid every request |
| MC007 | warn | Schema has no required list |
| MC008 | info | additionalProperties not false |
| MC009 | error | Duplicate tool name — one is unreachable |
| MC010 | warn | More than ~40 tools; selection accuracy drops |
| MC011 | warn | Whole tool list is expensive per request |
MC003 matches the tool name and its opening sentence, not the whole description — a destructive verb in later context ("use before publishing") isn't what the tool does, and matching it turns the rule into noise.
Options
--mcp treat paths as MCP tool-schema JSON
--format text|json|github
--fail-on error|warn|info|never minimum severity that exits non-zero
--select SL007,MC003 only these codes
--ignore SL014 suppress these codes
CI
- run: pipx install skill-lint
- run: skill-lint .claude/skills --format github --fail-on warn
Development
PYTHONPATH=src python3 -m unittest discover -s tests -v
The test suite includes a dogfood case: this server's own tool schema has to pass its own linter.
Licence
MIT
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。