Skip to content
TrustedSkillsbeta
Back to all skills

Nextjs Reviewer

Checked
jaredpalmer·vlatest·frontend

Analyzes Next.js projects for best practices, performance bottlenecks, and potential accessibility issues with actionable suggestions.

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 jaredpalmer/claude-plugins --skill nextjs-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

jaredpalmer

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 jaredpalmer/claude-plugins at 8eaecf5a1e.

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

Commit
8eaecf5a1e
Manifest
skills/nextjs-reviewer/SKILL.md
Scanned
1 file, 1,155 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 nextjs-reviewer skill allows AI agents to review Next.js codebases, identifying potential issues and suggesting improvements. It can analyze component structure, identify performance bottlenecks, and flag accessibility concerns within a Next.js application. This helps developers maintain high-quality and performant Next.js projects.

When to use it

  • Code Review: When you need an automated first pass at reviewing a Next.js codebase for common errors or style inconsistencies before human review.
  • Performance Optimization: To identify potential performance bottlenecks in your Next.js application, such as inefficient data fetching or rendering.
  • Accessibility Audit: When ensuring that your Next.js application meets accessibility standards and guidelines.

Key capabilities

  • Next.js codebase analysis
  • Component structure review
  • Performance bottleneck identification
  • Accessibility concern flagging

Example prompts

  • "Review this Next.js component for potential performance issues: [component code]"
  • "Analyze this Next.js application and identify any accessibility concerns."
  • "Can you check the structure of this Next.js project for best practices?"

Tips & gotchas

The skill requires access to the Next.js codebase being reviewed. Large or complex projects may take longer to analyze, and results should always be verified by a human developer.