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
96%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
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, uses natural trigger terms developers would actually search for, and explicitly states both what it does and when to use it. It is highly specific to ESLint v9 flat config and neostandard, making it easily distinguishable from other linting or JavaScript tooling skills. The description is concise yet comprehensive, covering setup, migration, troubleshooting, and CI integration scenarios.
| 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 or fixes linting, 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', 'eslint.config.js', 'eslint.config.mjs', 'neostandard', '.eslintrc', 'lint errors', '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`, `eslint.config.mjs`, `.eslintrc*`), the neostandard package, and the flat config migration scenario make 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 efficiently provides a quick start with executable code, maintains conciseness by assuming Claude's competence with JS tooling, and uses progressive disclosure effectively by linking to detailed rule files. The main weakness is the workflow section, which lists steps but lacks explicit validation checkpoints and error recovery guidance for migration scenarios.
Suggestions
Add a validation/rollback step to the common setup workflow, e.g., 'If `npx eslint .` reports config errors, check that eslint.config.js uses ESM syntax and neostandard is correctly installed; revert to previous config if migration fails.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It doesn't explain what ESLint or linting is, assumes Claude knows JavaScript tooling, and every section serves a clear purpose. The 'When to use' section is slightly verbose but still earns its place as a routing guide. | 3 / 3 |
Actionability | Provides fully executable install commands and a copy-paste ready eslint.config.js example. The quick start is concrete with real bash and JS code, and the verification step (`npx eslint .`) is specific. | 3 / 3 |
Workflow Clarity | The 'Common setup workflow' provides a clear numbered sequence, but lacks explicit validation checkpoints beyond 'confirm no config errors.' For a setup that could involve migration (destructive changes to config files), there's no feedback loop for error recovery or rollback guidance. | 2 / 3 |
Progressive Disclosure | Excellent structure with a concise overview and quick start at the top, then clearly signaled one-level-deep references to specific rule files for detailed implementation. Each linked file has a descriptive label making navigation easy. | 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