Skip to content
TrustedSkillsbeta
Back to all skills

Nodejs Best Practices Reviewer

Checked
dayanand-clerisy·vlatest·backend

Analyzes Node.js code for adherence to best practices, identifying potential bugs, security vulnerabilities, and style issues.

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 dayanand-clerisy/nodejs-best-practices-reviewer --skill nodejs-best-practices-reviewer -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

dayanand-clerisy

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 dayanand-clerisy/nodejs-best-practices-reviewer at 66f5380cde.

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

Commit
66f5380cde
Manifest
SKILL.md
Scanned
8 files, 572 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 reviews Node.js code and provides feedback based on established best practices. It identifies potential issues related to security, performance, maintainability, and coding style. The reviewer aims to improve the overall quality of the codebase by suggesting improvements and highlighting areas for refactoring.

When to use it

  • Code Review Automation: Integrate into a CI/CD pipeline to automatically review pull requests before merging.
  • Learning Node.js Best Practices: Use on personal projects or tutorials to understand how to write cleaner, more efficient code.
  • Refactoring Existing Codebases: Identify areas in legacy code that could benefit from modernization and improved practices.
  • Onboarding New Developers: Help new team members quickly learn and adhere to the project's coding standards.

Key capabilities

  • Identifies security vulnerabilities
  • Suggests performance improvements
  • Enforces consistent coding style
  • Highlights maintainability issues

Example prompts

  • "Review this Node.js code for potential security flaws: [code snippet]"
  • "Can you suggest ways to improve the performance of this function? [function code]"
  • "Check this file for adherence to common Node.js best practices: [file path]"

Tips & gotchas

The skill's effectiveness depends on providing clear and complete code snippets or file paths. It is designed to augment, not replace, human review.