skill-lint
Related Servers
Alternatives to skill-lint
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceStatic security linter for MCP servers. Scans tool definitions for vulnerabilities (path traversal, SQL injection, SSRF), scores description quality, and auto-rewrites descriptions for safer agent tool selection.2229 PyPI10MIT
- AlicenseNot gradedqualityDmaintenanceScores MCP tool definitions and tool lists from 0-100, flagging vague descriptions, missing parameter docs, non-verb-first naming, oversized enums, and nested schemas with severity, rationale, and concrete fixes. It also validates marketplace listings against platform character caps such as MCPize's 500-character short-description limit before deploy.MIT
- AlicenseAqualityAmaintenanceSecurity scanner for third-party AI agent-skill files: SKILL.md manifests, hooks, and bundled scripts, exposed via an MCP tool.110 npm1Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients to evaluate text or local files for LLM-output quality issues, returning 0-100 scores, grades, and precise line/column findings. It also lets clients list all available lint rules and severities.MIT

meok-agents-md-lint-mcpofficial
AlicenseNot gradedqualityDmaintenanceValidates AGENTS.md files against the cross-vendor coding-agent spec, detecting security smells and consistency issues.MIT- FlicenseNot gradedqualityBmaintenancePolicy-as-code gate for AI-SDLC, providing MCP tools to review prompts, diff tool manifests, vet MCP servers, and run evaluation suites for LLM agent repos.1-
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.