Skip to content
TrustedSkillsbeta
Back to all skills

Eslint Prettier Config

Checked
patricio0312rev·vlatest·backend·MIT

Helps with ESLint, Prettier as part of developing backend services and APIs workflows.

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 patricio0312rev/skills --skill eslint-prettier-config -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

patricio0312rev

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 patricio0312rev/skills at 79ea6af485.

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

Commit
79ea6af485
Manifest
foundation/eslint-prettier-config/SKILL.md
Scanned
1 file, 511 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-prettier-config skill provides a preconfigured setup for integrating ESLint and Prettier into code projects. It ensures consistent code formatting and enforces coding standards by combining the linting capabilities of ESLint with the formatting rules of Prettier.

When to use it

  • When setting up a new JavaScript or TypeScript project and wanting automated code quality checks.
  • When collaborating on a team and needing standardized formatting across all contributors' code.
  • When preparing for code reviews and aiming to reduce style-related feedback.

Key capabilities

  • Integrates ESLint and Prettier into a single configuration file.
  • Enforces consistent code formatting rules across the project.
  • Reduces conflicts by aligning linting and formatting tools.

Example prompts

  • "Set up ESLint and Prettier for my React project using this config."
  • "Automate code formatting and linting in my Node.js application with eslint-prettier-config."
  • "Apply the default rules from eslint-prettier-config to ensure consistent style across all files."

Tips & gotchas

  • Ensure ESLint and Prettier are installed as dev dependencies before using this configuration.
  • Customize the config file if your project requires specific linting or formatting rules beyond the defaults.