Linting Neostandard Eslint9
CheckedThis skill uses Neostandard and ESLint9 to automatically identify and fix code style issues, improving code quality and consistency.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add mcollina/skills --skill linting-neostandard-eslint9 -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
mcollina
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned mcollina/skills at 856efd268a.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 856efd268a
- Scanned
- 7 files, 343 lines
About this skill
What it does
This skill automates code style checks and fixes for JavaScript and TypeScript projects using Neostandard and ESLint9. It provides a baseline configuration based on Neostandard, allowing you to enforce consistent coding standards. The skill facilitates migration from older configurations (like .eslintrc*) or the Standard linting toolset to modern ESLint v9 with its flat config system (eslint.config.js or eslint.config.mjs).
When to use it
- Setting up linting in a new JavaScript or TypeScript project.
- Migrating an existing project from Standard or legacy
.eslintrc*configurations to Neostandard and ESLint v9. - Ensuring consistent code style across local development and CI environments.
- Creating a baseline ESLint v9 configuration using the flat config system.
- Implementing reproducible linting with pinned major versions of dependencies.
Key capabilities
- Provides a Neostandard-based ESLint v9 flat configuration.
- Supports migration from Standard or legacy
.eslintrc*configurations. - Facilitates setting up linting in CI environments.
- Offers guidance on editor integration and pre-commit hooks.
- Includes documentation for configuring, extending, and migrating to Neostandard and ESLint v9.
Example prompts
- "Set up linting with Neostandard and ESLint 9."
- "Migrate my project from Standard to Neostandard."
- "Create an
eslint.config.jsfile using Neostandard as a baseline." - “Configure ESLint v9 for this JavaScript project.”
Tips & gotchas
- Requires installation of
eslint@9andneostandarddependencies (npm install --save-dev eslint@9 neostandard). - The skill emphasizes keeping the configuration minimal and explicit.
- For CI environments, perform linting runs without auto-fixing to treat failures as quality gates.