Skip to content
TrustedSkillsbeta
Back to all skills

Review

Checked
johnlindquist·vlatest·other

Analyzes code snippets for style, best practices, and potential improvements based on John Lindquist's coding philosophy.

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 johnlindquist/claude --skill review -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

johnlindquist

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 johnlindquist/claude at eb37d88225.

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

Commit
eb37d88225
Manifest
skills/review/SKILL.md
Scanned
23 files, 5,401 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, johnlindquist-review, leverages Claude to provide detailed and critical reviews of software or tools. It can analyze code snippets, documentation, or even entire projects based on provided context. The goal is to offer constructive feedback and identify potential areas for improvement, mimicking a professional technical review process.

When to use it

  • Code Review: Get an automated critique of your code before submitting it for peer review.
  • Tool Evaluation: Quickly assess the strengths and weaknesses of a new software library or framework.
  • Documentation Analysis: Have Claude identify gaps, inconsistencies, or areas needing clarification in technical documentation.
  • Project Assessment: Obtain a high-level overview of a project's design and potential challenges.

Key capabilities

  • Claude integration for natural language processing.
  • Critical analysis of software and tools.
  • Identification of areas for improvement.
  • Review of code snippets, documentation, or entire projects.

Example prompts

  • "Review this Python function for efficiency and potential bugs: [code snippet]"
  • "Analyze the documentation for the 'requests' library and identify any missing examples."
  • "Provide a critical review of this project’s architecture based on these design documents: [link to docs]"

Tips & gotchas

The quality of the review depends heavily on the clarity and completeness of the provided context. Be sure to provide sufficient information for Claude to accurately assess the subject matter.