Skip to content
TrustedSkillsbeta
Back to all skills

Shellcheck

Checked
julianobarbosa·vlatest·devops·MIT

Shellcheck analyzes shell scripts for syntax errors, potential security vulnerabilities, and bad practices, improving code reliability and safety.

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 julianobarbosa/claude-code-skills --skill shellcheck -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

julianobarbosa

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

    Only contacts known or declared hosts: github.com.

    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.

    Hosts contacted

    github.comsource host

  • 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 julianobarbosa/claude-code-skills at 57f5fe8c0d.

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

Commit
57f5fe8c0d
Manifest
skills/shellcheck/SKILL.md
Scanned
9 files, 2,395 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 ShellCheck skill analyzes shell scripts to identify potential bugs and style issues. It provides static analysis, meaning it examines code without executing it, highlighting common errors like incorrect quoting, unused variables, or problematic command usage. This helps ensure script reliability and maintainability by catching problems early in the development process.

When to use it

  • Automated Script Review: Integrate ShellCheck into a CI/CD pipeline to automatically check shell scripts for errors before deployment.
  • Script Debugging: Use ShellCheck to quickly identify the root cause of unexpected script behavior.
  • Code Quality Improvement: Enforce consistent coding style and best practices within a team by using ShellCheck's recommendations.
  • Learning Best Practices: New shell scripters can use it to learn common pitfalls and improve their scripting skills.

Key capabilities

  • Static analysis of shell scripts
  • Identification of potential bugs and stylistic issues
  • Provides specific error messages and suggestions for improvement
  • Supports various shell syntaxes (e.g., Bash, Zsh)

Example prompts

  • "Analyze this script: [paste shell script here]"
  • "Check the following bash code for errors: [paste shell script here]"
  • "Run ShellCheck on my deployment script."

Tips & gotchas

ShellCheck's output can sometimes be verbose. Focus on addressing the most critical warnings first, and consider customizing its rules to fit your project’s specific needs.