Score7.9
Popularity70.0
Risknone
TierSilver
Score breakdown
Usefulness8.0
Novelty9.0
Momentum7.0
Maturity7.2
Open-source/build8.4
Evidence7.2
Workflow potential9.4
Setup ease8.8
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for engineering teams that maintain AI-coding-assistant config files (CLAUDE.md, AGENTS.md, MCP server configs, skill definitions) and want them linted and validated in CI before they silently break in production.
Who should use it
engineering teams that maintain CLAUDE.md, AGENTS.md, .cursorrules, or MCP server configs in gitplatform teams building CI gates that catch broken agent configs before they reach developersagent config authors who need editor-level validation (VS Code / JetBrains / Neovim / Zed)multi-tool stack teams (Claude Code + Cursor + Copilot) where one config breaks anotherOSS maintainers shipping Claude Code / Codex skills who need to validate skill metadata
Who should skip it
Skip if the source link, docs, or setup requirements do not match your workflow.
Risk explanation
No inherent user-impacting risk is flagged from the captured evidence.
Evidence links
Closest alternatives / related signals
linterlspclaude-codecodexcursorcopilotagent-configci