Skip to content
TrustedSkillsbeta
Back to all skills

Shellcheck Configuration

Listed
sickn33·vlatest·other·MIT

This skill generates a basic ShellCheck configuration file to help identify potential issues and improve shell script quality.

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 sickn33/agentic-awesome-skills --skill shellcheck-configuration -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

sickn33

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 failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • Declares what it does: failed

    No SKILL.md was found in the skill's directory.

    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 sickn33/antigravity-awesome-skills at 5a4cdd9df8.

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

Commit
5a4cdd9df8
Manifest
skills/shellcheck-configuration/SKILL.md
Scanned
0 files
Copies in repo
3 — all of them scanned
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

The shellcheck-configuration skill enables AI agents to analyze shell scripts for potential errors, style issues, and security vulnerabilities using the ShellCheck static analysis tool. It provides immediate feedback on bash, sh, dash, and zsh scripts to ensure robustness before execution.

When to use it

  • Pre-commit validation: Integrate into CI/CD pipelines or local workflows to catch syntax errors before code reaches production.
  • Security auditing: Identify dangerous commands like eval or unsafe variable expansions that could lead to shell injection attacks.
  • Style enforcement: Enforce consistent coding standards across a team by configuring specific rules for linting.
  • Legacy script modernization: Analyze outdated scripts to suggest improvements in syntax and best practices.

Key capabilities

  • Static analysis of shell scripts without execution.
  • Detection of syntax errors, undefined variables, and quoting issues.
  • Support for multiple shells including bash, sh, dash, and zsh.
  • Configurable rule sets to suppress specific warnings or enforce strict standards.
  • Integration with various development environments via CLI or API hooks.

Example prompts

  • "Run ShellCheck on this script and list all critical security vulnerabilities found."
  • "Configure ShellCheck to ignore warning SC2086 but flag all undefined variable usage in my bash file."
  • "Analyze this legacy shell script for deprecated syntax and suggest modern alternatives."

Tips & gotchas

Ensure the target shell scripts are syntactically valid enough for ShellCheck to parse; highly malformed scripts may yield false positives. Always review warnings marked as 'style' rather than treating them as critical errors unless strict compliance is required.