Skip to content
TrustedSkillsbeta
Back to all skills

Eslint

Checked
g1joshi·vlatest·backend·MIT

Enforces g1joshi's custom ESLint rules to ensure code style consistency and quality within JavaScript projects.

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 g1joshi/agent-skills --skill eslint -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

g1joshi

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 g1joshi/agent-skills at 6a74cf03a8.

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

Commit
6a74cf03a8
Manifest
skills/tools/eslint/SKILL.md
Scanned
1 file, 182 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 provides linting capabilities for JavaScript and related codebases using ESLint. It analyzes code for potential errors, stylistic problems, and adherence to coding standards. The agent can use this skill to automatically identify and suggest fixes for common coding issues, improving code quality and maintainability.

When to use it

  • Code Review: Automatically check a codebase for linting errors before merging changes.
  • Automated Formatting: Enforce consistent code style across a project by applying ESLint's formatting rules.
  • Educational Tool: Help developers learn best practices and common coding pitfalls through real-time feedback.
  • Pre-Commit Hooks: Integrate with version control systems to run linting checks before committing code changes.

Key capabilities

  • JavaScript linting
  • Code style enforcement
  • Error detection
  • Automated fixes (potentially)
  • Configuration via .eslintrc files

Example prompts

  • "Lint this JavaScript file: [file path]"
  • "Check the code for stylistic issues and suggest improvements."
  • "Run ESLint on my project and report any errors."

Tips & gotchas

  • Requires a valid .eslintrc configuration file to be present in the codebase. Without it, ESLint will use default rules which may not match your desired style.