shellcheck-configuration

Master ShellCheck static analysis configuration and usage for shell script quality. Use when setting up linting infrastructure, fixing code issues, or ensuring script portability.

Quality

58%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/shellcheck-configuration/SKILL.md

Quality

Content

46%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill reads more like a comprehensive ShellCheck reference manual than a concise, actionable skill for Claude. It over-explains fundamentals Claude already knows, inlines extensive reference material that should be in separate files, and lacks a clear guided workflow with validation checkpoints. The concrete code examples are a strength, though some contain errors (identical problem/solution pairs).

Suggestions

Drastically reduce the content to a concise overview (~50-80 lines) covering configuration setup, key integration patterns, and suppression syntax, moving the error code catalog and detailed examples to a separate REFERENCE.md file.

Remove the 'What is ShellCheck?' section and installation instructions — Claude already knows these. Focus only on project-specific configuration decisions and non-obvious patterns.

Fix the broken examples where problem and solution code are identical (SC2086 and SC2206 sections show the same code for both).

Add a clear sequential workflow with validation: e.g., 1) Create .shellcheckrc → 2) Run initial analysis → 3) Review and categorize findings → 4) Fix or suppress with documentation → 5) Verify clean run → 6) Set up CI gate.

Dimension	Reasoning	Score
Conciseness	Severely verbose for a skill targeting Claude. Explains what ShellCheck is, lists installation methods Claude already knows, describes what POSIX shells are, and includes extensive error code catalogs that belong in a reference file. The 'Best Practices' section is generic advice Claude already knows. Much of this content is reference material that should be in a separate file or omitted entirely.	2 / 5
Actionability	Provides concrete, executable code examples for configuration files, CI/CD integration, pre-commit hooks, and common violation fixes. The examples are mostly copy-paste ready. However, some examples have issues (e.g., the SC2086 'fix' shows the same code as the problem, and the SC2206 example similarly shows identical problem/solution), which slightly undermines actionability.	4 / 5
Workflow Clarity	The CI/CD integration section has a reasonable workflow with failure handling, but there's no overarching workflow for 'setting up ShellCheck for a project' with validation checkpoints. The skill lacks a clear sequential process for analyzing and fixing scripts — it's more of a reference catalog than a guided workflow. No feedback loops for iterative fixing are explicitly defined.	3 / 5
Progressive Disclosure	The content is a monolithic wall of reference material (~300+ lines) that should be split into separate files (error code reference, integration patterns, configuration examples). It references `resources/implementation-playbook.md` but no bundle files exist. The massive inline error code catalog and integration examples would be much better as separate referenced files.	2 / 5
	Total	11 / 20 Passed

Description

70%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is competent with a clear 'what' and 'when' structure and good tool-specific terminology. Its main weakness is that the capabilities listed are somewhat high-level rather than enumerating concrete actions (e.g., configuring directives, suppressing specific warnings, CI integration). Adding more natural trigger terms and synonyms would further strengthen discoverability.

Suggestions

Add more concrete actions such as 'configure ShellCheck directives, suppress specific warnings (SC codes), integrate with CI pipelines, validate POSIX compliance'.

Include additional trigger terms and synonyms like 'bash linting', '.sh files', 'SC warnings', 'POSIX', 'shell script errors' to improve keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (ShellCheck static analysis) and mentions a few actions ('setting up linting infrastructure, fixing code issues, ensuring script portability'), but these are fairly high-level and not deeply concrete — e.g., it doesn't mention specific capabilities like configuring directives, suppressing warnings, integrating with CI, or handling specific shell dialects.	3 / 5
Completeness	Has both 'what' (ShellCheck static analysis configuration and usage for shell script quality) and 'when' ('Use when setting up linting infrastructure, fixing code issues, or ensuring script portability'). The 'when' clause is present and reasonably explicit, though it could be more specific with additional trigger scenarios.	4 / 5
Trigger Term Quality	Includes good natural keywords like 'ShellCheck', 'linting', 'shell script', 'portability', and 'code issues'. Missing some common variations users might say such as 'bash linting', 'sh', '.sh files', 'shellcheck directives', 'SC warnings', or 'static analysis for bash'.	4 / 5
Distinctiveness Conflict Risk	ShellCheck is a specific tool, which makes this fairly distinct. However, 'fixing code issues' and 'linting infrastructure' are broad enough to potentially overlap with other linting or code quality skills. The mention of 'shell script' and 'ShellCheck' narrows it well but 'fixing code issues' introduces some overlap risk.	4 / 5
	Total	15 / 20 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/shellcheck-configuration/SKILL.md
Commit: fbdfd63

Reviewed: about 19 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.