mcollina/linting-neostandard-eslint9
Configures ESLint v9 flat config and neostandard for JavaScript and TypeScript projects, including migrating from legacy `.eslintrc*` files or the `standard` package. Use when you need to set up or fix linting with `eslint.config.js` or `eslint.config.mjs`, troubleshoot lint errors, configure neostandard rules, migrate from `.eslintrc` to flat config, or integrate linting into CI pipelines and pre-commit hooks.
96
95%
Does it follow best practices?
Impact
97%
1.25xAverage score across 5 eval scenarios
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly defines its scope (ESLint v9 flat config and neostandard), lists concrete actions (configuring, migrating, troubleshooting, integrating), and provides explicit trigger guidance via a comprehensive 'Use when...' clause. It uses third person voice correctly and includes highly specific, natural trigger terms that developers would actually use. It serves as a strong example of a well-crafted skill description.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: configures ESLint v9 flat config, configures neostandard, migrates from legacy `.eslintrc*` files, migrates from `standard` package, sets up `eslint.config.js`/`eslint.config.mjs`, troubleshoots lint errors, configures neostandard rules, integrates linting into CI pipelines and pre-commit hooks. | 3 / 3 |
Completeness | Clearly answers both 'what' (configures ESLint v9 flat config and neostandard, migrates from legacy configs) and 'when' with an explicit 'Use when...' clause listing specific trigger scenarios like setting up linting, troubleshooting errors, migrating configs, and integrating into CI. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'ESLint', 'flat config', 'neostandard', 'eslint.config.js', 'eslint.config.mjs', '.eslintrc', 'lint errors', 'linting', 'CI pipelines', 'pre-commit hooks', 'JavaScript', 'TypeScript', 'standard' package. These are all terms a developer would naturally use when seeking help with this topic. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: ESLint v9 flat config and neostandard specifically. The mention of specific file names (`eslint.config.js`, `.eslintrc`), specific tools (neostandard, ESLint v9), and specific migration paths makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill that serves as an effective overview document. It provides an immediately actionable quick start with executable code, maintains excellent token efficiency by avoiding unnecessary explanations, and uses progressive disclosure effectively by pointing to detailed rule files. The main weakness is the workflow section, which could benefit from explicit validation/error-recovery steps.
Suggestions
Add a brief error recovery note to the workflow, e.g., 'If `npx eslint .` reports config errors, check that `package.json` has `"type": "module"` or rename to `eslint.config.mjs`'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. The 'When to use' section is a concise bullet list, the quick start is minimal with executable code, and the core principles are brief. No unnecessary explanations of what ESLint or linting is. | 3 / 3 |
Actionability | Provides fully executable commands (npm install, npx eslint), a copy-paste ready eslint.config.js, and concrete steps for setup. The quick start is immediately actionable. | 3 / 3 |
Workflow Clarity | The 'Common setup workflow' section provides a clear numbered sequence, but lacks explicit validation checkpoints or error recovery steps. Step 4 ('confirm no config errors') is implicit rather than having a feedback loop for what to do if errors occur. | 2 / 3 |
Progressive Disclosure | Excellent structure with a concise overview and quick start at the top, then clearly signaled one-level-deep references to five specific rule files covering different aspects. Navigation is easy and well-organized. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
Total | 10 / 11 Passed | |
Reviewed
Table of Contents