Agent skill

Es X Node Support Update

by eslint-community in eslint-community/eslint-plugin-es-x

Update eslint-plugin-es-x Node.js support in its own dedicated PR.

MITAuto-check passedDevelopment

Install Es X Node Support Update

skills CLI
$ npx skills add eslint-community/eslint-plugin-es-x --skill es-x-node-support-update -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install eslint-community/eslint-plugin-es-x es-x-node-support-update --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/eslint-community/eslint-plugin-es-x.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/es-x-node-support-update .claude/skills/es-x-node-support-update && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
es-x-node-support-update
GitHub stars
157
Token cost
~980 tokens
SKILL.md length
466 words
Files
1
Skills in repo
6
Repo updated
First seen
Licence
MIT

At a glance

Update eslint-plugin-es-x Node.js support in its own dedicated PR.

  • Works in 8 steps: Inspect current Node.js support… → Check current Node.js EOL status and… → Choose the non-EOL Node.js major lines… → …
  • Tasks that involve Linting and formatting
  • SKILL.md covers Workflow and Current Major-Prep Pattern
  • Calls npm; reaches raw.githubusercontent.com and nodejs.org

What it does

Es X Node Support Update is an agent skill from eslint-community/eslint-plugin-es-x. Update eslint-plugin-es-x Node.js support in its own dedicated PR. Use during major release preparation or support policy changes to check the current Node.js release schedule, keep the intended non-EOL Node.js lines with explicit major-line ranges, and update package engines, public documentation requirements, Node.js CI matrix entries, lockfile root metadata, release notes, and verification without changing the ESLint peer dependency.

Its SKILL.md is about 980 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Linting and formatting, Dependency management and Changelog and release notes. It works with Node.js, ESLint and JavaScript. The repository describes itself as: ESLint plugin about ECMAScript syntactic features. The licence is MIT.

When your agent uses it

  • Tasks that involve Linting and formatting
  • Tasks that involve Dependency management
  • Tasks that involve Changelog and release notes

Example prompts

  • “/es-x-node-support-update”

Requirements

  • Node.js

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. Inspect current Node.js support declarations
  2. Check current Node.js EOL status and releases before choosing the new support range
  3. Choose the non-EOL Node.js major lines that should remain supported after the drop, then build package.json engines.node from those lines
  4. Update CI
  5. Update user-facing support documentation
  6. Refresh lockfile root metadata with npm install --package-lock-only if package-lock.json does not update automatically.
  7. Add release notes through .agents/es-x-changeset/SKILL.md.
  8. Verify through .agents/es-x-release-verification/SKILL.md.

What it can do on your machine

Read from SKILL.md and the folder at commit b80ba91. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • raw.githubusercontent.com
    • nodejs.org

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Es X Node Support Update loads about 980 tokens when it runs. Until then it costs about 116 tokens; SKILL.md has 466 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~116
When it runs · the whole SKILL.md, loaded when a task matches
~980

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from eslint-community/eslint-plugin-es-x at commit b80ba91, republished under its MIT licence (© eslint-community). 466 words, ~980 tokens.

Download SKILL.mdSave it as .claude/skills/es-x-node-support-update/SKILL.md (or your agent's skills folder).
name
es-x-node-support-update
description
Update eslint-plugin-es-x Node.js support in its own dedicated PR. Use during major release preparation or support policy changes to check the current Node.js release schedule, keep the intended non-EOL Node.js lines with explicit major-line ranges, and update package engines, public documentation requirements, Node.js CI matrix entries, lockfile root metadata, release notes, and verification without changing the ESLint peer dependency.

ES-X Node.js Support Update

Workflow

Use this when dropping old Node.js support. Keep this work separate from ESLint support drops and annual ECMAScript snapshot config updates unless the user explicitly asks for a combined PR.

  1. Inspect current Node.js support declarations:
    • package.json engines.node
    • docs/index.md Requirements Node.js line
    • .github/workflows/ci.yml Node.js matrix entries
    • top-level package-lock.json engines.node
  2. Check current Node.js EOL status and releases before choosing the new support range:
    • Prefer the official schedule data at https://raw.githubusercontent.com/nodejs/Release/main/schedule.json.
    • Use the current date to exclude Node.js majors whose end date has passed.
    • Use official release data, such as https://nodejs.org/dist/index.json, to find the latest release for each retained non-EOL major.
    • Include Current and LTS Node.js majors when they are not EOL; do not restrict the choice to LTS unless the user explicitly asks.
  3. Choose the non-EOL Node.js major lines that should remain supported after the drop, then build package.json engines.node from those lines:
    • For each retained line except the newest retained major, use a caret range from the first patch release of that line's latest required major/minor line, such as ^22.18.0.
    • For the newest retained major, use an open lower-bound range from the first patch release of that line's latest required major/minor line, such as >=24.7.0.
    • Join multiple ranges with ||. For example, if Node.js 22 and 24 remain supported, use a range shaped like ^22.18.0 || >=24.7.0, not >=22.18.0.
    • Do not add any other upper bound unless the project already has one or the user explicitly asks for one.
  4. Update CI:
    • Remove jobs for Node.js majors and minor lines outside the new supported range, even if those older majors are not EOL.
    • Keep one minimum-supported Node.js job for each retained major line, such as 22.18.0 and 24.7.0 when the new range is ^22.18.0 || >=24.7.0.
    • Keep platform coverage on a normal supported Node.js version.
    • Do not change ESLint matrix versions except where a Node.js job must be moved to a supported Node.js version.
  5. Update user-facing support documentation:
    • Keep docs/index.md Requirements in sync with package.json engines.node.
    • Preserve the existing prose format: - Node.js `X.Y.Z`, `A.B.C` or newer..
    • For multiple supported Node.js ranges, list the lower-bound version from each range rather than pasting the raw semver expression.
  6. Refresh lockfile root metadata with npm install --package-lock-only if package-lock.json does not update automatically.
  7. Add release notes through .agents/es-x-changeset/SKILL.md.
  8. Verify through .agents/es-x-release-verification/SKILL.md.
Show full SKILL.md (81 more words)Show less

Current Major-Prep Pattern

For any major-prep Node.js support PR:

  • Check the official Node.js release schedule and release index.
  • Build the engine range from the retained non-EOL Node.js lines. Use caret ranges for retained older majors and an open lower-bound range for the newest retained major, such as ^22.18.0 || >=24.7.0.
  • Keep docs/index.md Requirements synchronized with the same minimum versions while preserving its prose format.
  • Remove CI coverage for Node.js versions outside that range.
  • Keep the ESLint support range unchanged in this PR.

© eslint-community, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/es-x-node-support-update of eslint-community/eslint-plugin-es-x.

Open the folder on GitHubat commit b80ba91

Compare with similar skills

Es X Node Support Update next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Es X Node Support Update compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Es X Node Support Update this skilleslint-community/eslint-plugin-es-x157—~980Automated safety check: PassMIT
Generate Release Notesteambit/bit18k—~2.2kAutomated safety check: PassCustom licence
Ultraciteagustinusnathaniel/nextarter-tailwind1252 repos~1.2kAutomated safety check: PassMIT
Code Qualityredis/RedisInsight8.9k—~1.2kAutomated safety check: PassCustom licence
Port Ruleweb-infra-dev/rslint460—~1.7kAutomated safety check: PassMIT
Migrate OxlintAsvarox/allkaraoke2614 repos~2.5kAutomated safety check: PassNone

Similar skills

  • Generate comprehensive release notes for Bit from git commits and pull requests.

    18k GitHub stars~2.2k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Ultracite

    agustinusnathaniel/nextarter-tailwind

    Ultracite is a zero-config linting and formatting preset for JavaScript/TypeScript projects.

    125 GitHub starsUsed in 2 repos~1.2k tokens
    DevelopmentAuto-check passed
  • Code Quality

    redis/RedisInsight

    Official

    Code-quality standards for RedisInsight: TypeScript strictness, naming conventions (camelCase, PascalCase, UPPERSNAKECASE), linting rules, no any without reason, no !important in styles, and…

    8.9k GitHub stars~1.2k tokensUpdated 4 days ago
    DevelopmentAuto-check passed
  • Port Rule

    web-infra-dev/rslint

    Port a new ESLint core or plugin rule to rslint, including explicitly requested batches.

    460 GitHub stars~1.7k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Migrate Oxlint

    Asvarox/allkaraoke

    Guide for migrating a project from ESLint to Oxlint. An agent skill from Asvarox/allkaraoke.

    261 GitHub starsUsed in 4 repos~2.5k tokens
    DevelopmentAuto-check passed
  • Cb Code Quality

    BlkLeg/CircuitBreaker

    Circuit Breaker code conventions and the quality gates that actually block a push — ruff, mypy, eslint, the pytest coverage ratchet, and the make verify tiers.

    201 GitHub stars~1.9k tokensUpdated 3 days ago
    DevelopmentAuto-check passed

More from eslint-community/eslint-plugin-es-x

  • Es X Changeset

    eslint-community/eslint-plugin-es-x

    Add or update Changesets entries for eslint-plugin-es-x. An agent skill from eslint-community/eslint-plugin-es-x.

    157 GitHub stars~383 tokensUpdated 13 days ago
    Auto-check passed
  • Es X Major Version Prep

    eslint-community/eslint-plugin-es-x

    Prepare eslint-plugin-es-x for a major version release from a broad instruction such as "prepare the major version upgrade" or "prepare the next major release".

    157 GitHub stars~801 tokensUpdated 13 days ago
    Auto-check passed
  • Es X Snapshot Config Update

    eslint-community/eslint-plugin-es-x

    Update eslint-plugin-es-x for a newly finalized yearly ECMAScript/ECMA-402 snapshot in its own dedicated PR.

    157 GitHub stars~550 tokensUpdated 13 days ago
    Auto-check passed
  • Es X Eslint Support Update

    eslint-community/eslint-plugin-es-x

    Update eslint-plugin-es-x ESLint peer support in its own dedicated PR.

    157 GitHub stars~798 tokensUpdated 13 days ago
    Auto-check passed
  • Es X Release Verification

    eslint-community/eslint-plugin-es-x

    Verify eslint-plugin-es-x changes before handoff or release preparation.

    157 GitHub stars~388 tokensUpdated 13 days ago
    Auto-check passed

Categories

Questions about Es X Node Support Update

What does Es X Node Support Update do?

Update eslint-plugin-es-x Node.js support in its own dedicated PR. Es X Node Support Update is an agent skill from eslint-community/eslint-plugin-es-x.js support in its own dedicated PR.

When should I use Es X Node Support Update?

Es X Node Support Update fits situations like: tasks that involve Linting and formatting; tasks that involve Dependency management; tasks that involve Changelog and release notes.

How do I install Es X Node Support Update in Claude Code?

Run `npx skills add eslint-community/eslint-plugin-es-x --skill es-x-node-support-update -a claude-code`. Or copy the skill folder (.agents/skills/es-x-node-support-update in eslint-community/eslint-plugin-es-x) into .claude/skills/es-x-node-support-update in your project. Claude Code loads it when a task matches its description.

How do I install Es X Node Support Update in Codex?

Run `npx skills add eslint-community/eslint-plugin-es-x --skill es-x-node-support-update -a codex`. Or copy the skill folder (.agents/skills/es-x-node-support-update in eslint-community/eslint-plugin-es-x) into .agents/skills/es-x-node-support-update in your project. Codex loads it when a task matches its description.

Can I use Es X Node Support Update in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add eslint-community/eslint-plugin-es-x --skill es-x-node-support-update -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/es-x-node-support-update, .gemini/skills/es-x-node-support-update, .github/skills/es-x-node-support-update and .opencode/skills/es-x-node-support-update in your project.

What does Es X Node Support Update need to run?

Going by SKILL.md and its folder, Es X Node Support Update needs the command-line tools its instructions call (npm). Our summary lists: Node.js.

Does Es X Node Support Update access the network?

SKILL.md names 2 domains. In commands or code: raw.githubusercontent.com and nodejs.org; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Es X Node Support Update safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Es X Node Support Update use?

Es X Node Support Update is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Es X Node Support Update use?

About 980 tokens (SKILL.md is roughly 3.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Es X Node Support Update?

Skills that share tags, products or a category with Es X Node Support Update: Generate Release Notes (teambit/bit, 18k stars), Ultracite (agustinusnathaniel/nextarter-tailwind, 125 stars), Code Quality (redis/RedisInsight, 8.9k stars) and Port Rule (web-infra-dev/rslint, 460 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Es X Node Support Update?

eslint-community (a GitHub organization) maintains it in eslint-community/eslint-plugin-es-x, which has 157 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on September 25, 2026.

Source: eslint-community/eslint-plugin-es-x on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.