Eslint Prettier Husky Config
CheckedHelps with ESLint, Prettier as part of agent workflows workflows.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add hopeoverture/worldbuilding-app-skills --skill eslint-prettier-husky-config -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
hopeoverture
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.
Automated safety checks
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 hopeoverture/worldbuilding-app-skills at 1263b3fb00.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 1263b3fb00
- Scanned
- 10 files, 1,178 lines
- Copies in repo
- 2 — all of them scanned
About this skill
What it does
This skill automates code formatting and linting using ESLint, Prettier, and Husky. It ensures consistent coding style across a project by automatically formatting files on commit and enforcing code quality rules. This helps maintain clean, readable, and error-free JavaScript/TypeScript codebases.
When to use it
- New Projects: Automatically set up standard code formatting and linting for new projects from the start.
- Existing Codebases: Integrate consistent code style into existing projects with minimal manual intervention.
- Team Collaboration: Enforce a shared coding style across multiple developers working on the same project.
- Automated Workflows: Integrate code formatting and linting checks into CI/CD pipelines for automated quality assurance.
Key capabilities
- ESLint integration for JavaScript/TypeScript linting.
- Prettier integration for automatic code formatting.
- Husky integration to run linters and formatters before commits.
Example prompts
- "Set up ESLint, Prettier, and Husky in my project."
- "Configure the project with a standard JavaScript coding style using ESLint and Prettier."
- “Automate code formatting on commit.”
Tips & gotchas
- Requires Node.js to be installed.
- May require adjustments to
.eslintrc.jsorprettierrc.jsfor specific project needs.