Skip to content
TrustedSkillsbeta
Back to all skills

Eslint Detector

Checked
alex-popov-tech·vlatest·backend·MIT

Identifies and flags potential JavaScript code style and error issues using ESLint rules.

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 alex-popov-tech/.dotfiles --skill eslint-detector -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

alex-popov-tech

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 alex-popov-tech/.dotfiles at 729394ec7a.

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

Commit
729394ec7a
Manifest
claude/.claude/skills/eslint-detector/SKILL.md
Scanned
1 file, 217 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

The eslint-detector skill allows AI agents to detect and report on the presence of ESLint configuration files within a given directory. It identifies whether an .eslintrc.* file or a package.json with ESLint defined exists, providing valuable information about project linting setup. This helps in understanding code quality practices and potential development workflows.

When to use it

  • Codebase Assessment: Quickly determine if a repository uses ESLint for JavaScript/TypeScript code style enforcement.
  • Onboarding New Developers: Help new team members understand the existing code quality tools used in a project.
  • Automated Checks: Integrate into CI/CD pipelines to verify that linting configurations are present and consistent across projects.
  • Project Migration: Evaluate whether ESLint is already configured when migrating a codebase or integrating with new tooling.

Key capabilities

  • Detects .eslintrc.* files.
  • Checks package.json for ESLint dependencies/configuration.
  • Reports presence or absence of ESLint configuration.

Example prompts

  • "Does this project use ESLint?"
  • "Check the /src directory for an ESLint configuration."
  • "Is there a .eslintrc.js file in the root of this repository?"

Tips & gotchas

  • The skill relies on standard file system paths and naming conventions; unusual configurations might not be detected.
  • Requires access to the project's directory structure for accurate detection.