Skip to content
TrustedSkillsbeta
Back to all skills

Eslint 9

Checked
grahamcrackers·vlatest·backend·MIT

Automatically identifies and suggests fixes for JavaScript code style and potential errors using ESLint version 9.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add grahamcrackers/skills --skill eslint-9 -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

grahamcrackers

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.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

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 grahamcrackers/skills at ca83de4544.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
ca83de4544
Manifest
skills/eslint-9/SKILL.md
Scanned
1 file, 221 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill, eslint-9, provides automated JavaScript linting. It analyzes code to identify potential problems like syntax errors, style inconsistencies, and possible bugs. This helps maintain code quality and consistency across projects by enforcing coding standards.

When to use it

  • Code Review: Integrate into a CI/CD pipeline to automatically check pull requests for linting issues before merging.
  • New Project Setup: Apply ESLint rules from the start of a project to ensure consistent code style and prevent common errors.
  • Refactoring Existing Code: Use ESLint to identify areas where existing code deviates from established coding standards during refactoring efforts.
  • Team Collaboration: Enforce team-wide coding conventions, reducing debates about stylistic choices and improving overall readability.

Key capabilities

  • JavaScript linting
  • Enforcement of coding standards
  • Identification of syntax errors
  • Detection of style inconsistencies
  • Bug prevention

Example prompts

  • "Lint this JavaScript code: [paste code here]"
  • "Check this file for ESLint errors: my_script.js"
  • "Run the configured ESLint rules on all files in the 'src' directory."

Tips & gotchas

  • Requires a JavaScript project with an existing .eslintrc.* configuration file to function effectively. Without it, ESLint will use default settings which may not align with your desired style.