HN Showcase
Back to browse
GitHub Repository

An opinionated linter for SKILL.md files

8 starsTypeScript

A Linter for Skill.md Files

by theahura·Mar 5, 2026·2 points·0 comments
Visit ProjectView on HN

AI Analysis

●MidNiche GemShip It

Domain-specific linter for an emerging agent skill format, but audience limited to agentskills.io ecosystem.

Strengths
  • •Hybrid approach combining deterministic rules with LLM validation for hard-to-automate checks
  • •One-liner CLI with both lint and fix modes, lowering friction for adoption
Weaknesses
  • •Highly niche: only useful for agentskills.io users; unclear if framework has meaningful adoption
  • •No comparison to generic markdown linters or similar agent skill validators
Target Audience

AI agent developers using agentskills.io framework

Similar To

ESLint (linting pattern) · Prettier (auto-fix pattern)

Post Description

We wrote a linter for our own internal use, and today we decided to open source it.

SKILLs are the easiest way to configure agents, and you can get a lot of juice from a few well written SKILL files. Unfortunately, most SKILL files are not well written. They are way too long, they waste tokens explaining things that the model already knows, and many don't even follow the agentskills.io spec.

Linters help automate low hanging fruit changes that we find we constantly need to make.

You can run the linter as a one-liner: `npx nori-lint lint path/to/SKILL.md` or `npx nori-lint fix path/to/SKILL.md`

SKILL files are hard to lint deterministically, so there are several rules that require an LLM to do part of the review. You can set up a .nori-lint.json file to include an Anthropic API key, which will kick off a bunch of llm analysis rules.

Similar Projects

Developer Tools●●Solid

Agnix – lint your AI agent configs (Claude.md, skills, MCP, hooks)

Makes agent configs first-class with 229 domain-specific rules, autofix, and LSP support — so a tiny syntax mistake stops being a silent failure. The cross-editor plugins and GitHub Action are the standout moves: lint in your IDE and enforce checks in CI. I want a clearer map of which rules target which toolchains, but the breadth of integrations is impressive.

Niche GemSolve My ProblemSlick
anotherCodder
114mo ago