Eslint
managedcode/dotnet-skills
Use ESLint in .NET repositories that ship JavaScript, TypeScript, React, or other Node-based frontend assets.
Verify eslint-plugin-es-x changes before handoff or release preparation.
Install Es X Release Verification
$ npx skills add eslint-community/eslint-plugin-es-x --skill es-x-release-verification -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install eslint-community/eslint-plugin-es-x es-x-release-verification --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-release-verification .claude/skills/es-x-release-verification && rm -rf skills-srcUse ~/.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/
Install the "es-x-release-verification" agent skill from https://github.com/eslint-community/eslint-plugin-es-x/tree/master/.agents/skills/es-x-release-verification into .claude/skills/es-x-release-verification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "es-x-release-verification", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/eslint-community/eslint-plugin-es-x/tree/master/.agents/skills/es-x-release-verificationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add eslint-community/eslint-plugin-es-x --skill es-x-release-verification -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install eslint-community/eslint-plugin-es-x es-x-release-verification --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/eslint-community/eslint-plugin-es-x.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/es-x-release-verification .agents/skills/es-x-release-verification && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "es-x-release-verification" agent skill from https://github.com/eslint-community/eslint-plugin-es-x/tree/master/.agents/skills/es-x-release-verification into .agents/skills/es-x-release-verification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "es-x-release-verification", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add eslint-community/eslint-plugin-es-x --skill es-x-release-verification -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install eslint-community/eslint-plugin-es-x es-x-release-verification --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/eslint-community/eslint-plugin-es-x.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/es-x-release-verification .cursor/skills/es-x-release-verification && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "es-x-release-verification" agent skill from https://github.com/eslint-community/eslint-plugin-es-x/tree/master/.agents/skills/es-x-release-verification into .cursor/skills/es-x-release-verification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "es-x-release-verification", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/eslint-community/eslint-plugin-es-x.git --path .agents/skills/es-x-release-verification--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add eslint-community/eslint-plugin-es-x --skill es-x-release-verification -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install eslint-community/eslint-plugin-es-x es-x-release-verification --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/eslint-community/eslint-plugin-es-x.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/es-x-release-verification .gemini/skills/es-x-release-verification && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "es-x-release-verification" agent skill from https://github.com/eslint-community/eslint-plugin-es-x/tree/master/.agents/skills/es-x-release-verification into .gemini/skills/es-x-release-verification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "es-x-release-verification", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install eslint-community/eslint-plugin-es-x es-x-release-verificationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add eslint-community/eslint-plugin-es-x --skill es-x-release-verification -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/eslint-community/eslint-plugin-es-x.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/es-x-release-verification .github/skills/es-x-release-verification && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "es-x-release-verification" agent skill from https://github.com/eslint-community/eslint-plugin-es-x/tree/master/.agents/skills/es-x-release-verification into .github/skills/es-x-release-verification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "es-x-release-verification", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add eslint-community/eslint-plugin-es-x --skill es-x-release-verification -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install eslint-community/eslint-plugin-es-x es-x-release-verification --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/eslint-community/eslint-plugin-es-x.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/es-x-release-verification .opencode/skills/es-x-release-verification && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "es-x-release-verification" agent skill from https://github.com/eslint-community/eslint-plugin-es-x/tree/master/.agents/skills/es-x-release-verification into .opencode/skills/es-x-release-verification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "es-x-release-verification", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
es-x-release-verification- GitHub stars
- 157
- Token cost
- ~388 tokens
- SKILL.md length
- 185 words
- Files
- 1
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- MIT
At a glance
Verify eslint-plugin-es-x changes before handoff or release preparation.
- Works in 4 steps: git diff --check → npm test for code, rule, config, test,… → npm run build for lib, packaging, type… → …
- Tasks that involve Linting and formatting
- SKILL.md covers Checks, Review and Known Caveat
- Calls npm and git
What it does
Es X Release Verification is an agent skill from eslint-community/eslint-plugin-es-x. Verify eslint-plugin-es-x changes before handoff or release preparation. Use after rule, config, docs, generated file, Changesets, dependency, packaging, or support-range changes to run the relevant project checks, inspect consistency, and report caveats.
Its SKILL.md is about 390 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. It works with ESLint, JavaScript and npm. 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
Example prompts
- “/es-x-release-verification”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- git diff --check
- npm test for code, rule, config, test, generated file, dependency, or broad release-prep changes.
- npm run build for lib, packaging, type declaration, or public API changes.
- npm run docs:build when docs changed.
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:
npmgit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm and git, which can reach the network depending on how they are called.
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 Release Verification loads about 388 tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 185 words of instructions outside code blocks.
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). 185 words, ~388 tokens.
Download SKILL.mdSave it as
.claude/skills/es-x-release-verification/SKILL.md (or your agent's skills folder).- name
- es-x-release-verification
- description
- Verify eslint-plugin-es-x changes before handoff or release preparation. Use after rule, config, docs, generated file, Changesets, dependency, packaging, or support-range changes to run the relevant project checks, inspect consistency, and report caveats.
ES-X Release Verification
Checks
Run the checks that match the touched surface:
git diff --checknpm testfor code, rule, config, test, generated file, dependency, or broad release-prep changes.npm run buildforlib, packaging, type declaration, or public API changes.npm run docs:buildwhen docs changed.
Run npm run update before verification if generated files may be stale.
Review
Inspect the final diff for:
- Generated files are consistent with their source inputs.
- New or changed configs are listed in
lib/index.tswhen they are public. - Legacy and flat config surfaces stay in sync.
- Rule docs and config docs link to existing config names.
- A
.changeset/*.mdentry exists when the change should appear in release notes. - No unrelated generated artifacts such as
distor coverage output are accidentally included.
Known Caveat
npm run tsc may fail because of third-party type definitions included by repo-level files even when npm run build passes. If this happens, report the exact dependency path and error separately from the verification result. Prefer npm run build as the publish-output type check because it uses tsconfig.build.json with include: ["lib"].
© 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-release-verification of eslint-community/eslint-plugin-es-x.
Open the folder on GitHubat commit b80ba91
Compare with similar skills
Es X Release Verification 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Es X Release Verification this skilleslint-community/eslint-plugin-es-x | 157 | — | ~388 | Automated safety check: Pass | MIT | |
| Eslintmanagedcode/dotnet-skills | 486 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Webhintmanagedcode/dotnet-skills | 486 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Install Anti-Slop Oxlint Rulesdmmulroy/anti-slop | 5.4k | — | ~2.2k | Automated safety check: Pass | MIT | |
| Ultraciteagustinusnathaniel/nextarter-tailwind | 125 | 2 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Code Qualityredis/RedisInsight | 8.9k | — | ~1.2k | Automated safety check: Pass | Custom licence |
Similar skills
Webhint
managedcode/dotnet-skills
Use webhint in .NET repositories that ship browser-facing frontends.
Install Anti-Slop Oxlint Rules
dmmulroy/anti-slop
Installs, updates or migrates the vendored anti-slop Oxlint plugin in a repository, keeping local rule changes and the plugin's license and provenance files.
Ultracite
agustinusnathaniel/nextarter-tailwind
Ultracite is a zero-config linting and formatting preset for JavaScript/TypeScript projects.
- Official
Code Quality
redis/RedisInsight
Code-quality standards for RedisInsight: TypeScript strictness, naming conventions (camelCase, PascalCase, UPPERSNAKECASE), linting rules, no any without reason, no !important in styles, and…
Port Rule
web-infra-dev/rslint
Port a new ESLint core or plugin rule to rslint, including explicitly requested batches.
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.
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".
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.
Es X Eslint Support Update
eslint-community/eslint-plugin-es-x
Update eslint-plugin-es-x ESLint peer support in its own dedicated PR.
Es X Node Support Update
eslint-community/eslint-plugin-es-x
Update eslint-plugin-es-x Node.js support in its own dedicated PR.
Related
Works with
Categories
Questions about Es X Release Verification
What does Es X Release Verification do?
Verify eslint-plugin-es-x changes before handoff or release preparation. Es X Release Verification is an agent skill from eslint-community/eslint-plugin-es-x. Verify eslint-plugin-es-x changes before handoff or release preparation.
When should I use Es X Release Verification?
Es X Release Verification fits situations like: tasks that involve Linting and formatting.
How do I install Es X Release Verification in Claude Code?
Run `npx skills add eslint-community/eslint-plugin-es-x --skill es-x-release-verification -a claude-code`. Or copy the skill folder (.agents/skills/es-x-release-verification in eslint-community/eslint-plugin-es-x) into .claude/skills/es-x-release-verification in your project. Claude Code loads it when a task matches its description.
How do I install Es X Release Verification in Codex?
Run `npx skills add eslint-community/eslint-plugin-es-x --skill es-x-release-verification -a codex`. Or copy the skill folder (.agents/skills/es-x-release-verification in eslint-community/eslint-plugin-es-x) into .agents/skills/es-x-release-verification in your project. Codex loads it when a task matches its description.
Can I use Es X Release Verification 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-release-verification -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-release-verification, .gemini/skills/es-x-release-verification, .github/skills/es-x-release-verification and .opencode/skills/es-x-release-verification in your project.
What does Es X Release Verification need to run?
Going by SKILL.md and its folder, Es X Release Verification needs the command-line tools its instructions call (npm and git).
Does Es X Release Verification access the network?
SKILL.md contains no URLs. Its commands use npm and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Es X Release Verification 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 Release Verification use?
Es X Release Verification 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 Release Verification use?
About 388 tokens (SKILL.md is roughly 1.6k 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 Release Verification?
Skills that share tags, products or a category with Es X Release Verification: Eslint (managedcode/dotnet-skills, 486 stars), Webhint (managedcode/dotnet-skills, 486 stars), Install Anti-Slop Oxlint Rules (dmmulroy/anti-slop, 5.4k stars) and Ultracite (agustinusnathaniel/nextarter-tailwind, 125 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Es X Release Verification?
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.