CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/shellcheck-configuration/SKILL.md

The canonical home for this skill is shellcheck-configuration in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

46%Weight 40%Scale 1-5

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

The content is rich in concrete, executable configuration examples but suffers from significant duplication (error codes explained twice), padding that assumes no baseline knowledge, and a broken reference to a nonexistent playbook file. A restructuring into a lean overview with real reference files would address most weaknesses.

Suggestions

Remove the duplicate 'Common Violations and Fixes' section and the 'What is ShellCheck?' explainer, and move the error-code catalog into a references/ file the body links to.

Fix or delete the broken 'resources/implementation-playbook.md' reference — the bundle contains no such file (and the conventional directory is references/).

Correct the technically wrong examples: the SC2086/SC2206 'fixes' identical to the flagged code, the unterminated SC2181 if-block, and the nonexistent SHELLCHECK_SHELL/SHELLCHECK_STRICT/SHELLCHECK_CONFIG environment variables.

Replace the vague 'Instructions' bullets with a concrete setup sequence (install → configure .shellcheckrc → integrate CI/pre-commit → verify with shellcheck --version and a test run).

DimensionReasoningScore

Conciseness

The body is noticeably verbose: the 'What is ShellCheck?' section explains concepts Claude already knows, an ~80-line error-code catalog duplicates ShellCheck's own wiki output, and the 'Common Violations and Fixes' section repeats SC2086/SC2015/SC2016/SC2009/SC2181 examples already shown in 'Common ShellCheck Error Codes'. Not 1 because the configuration, CI integration, and output-format sections do add non-obvious value; not 3 because the padding and duplication are extensive rather than occasional.

2 / 5

Actionability

Mostly executable guidance: install commands, .shellcheckrc examples, CLI invocations, pre-commit hook, and CI YAML are copy-paste ready. Not 5 because several snippets are broken or wrong — the SC2086 'solutions' are identical to the problem ('for i in $list; do done'), the SC2206 fix 'array=( $items )' matches the flagged code, the SC2181 example is missing 'fi', and the SHELLCHECK_SHELL/SHELLCHECK_STRICT/SHELLCHECK_CONFIG environment variables are not real ShellCheck settings.

4 / 5

Workflow Clarity

Concrete recipes exist (CI loop with '|| exit 1', pre-commit with failure exit) but there is no coherent setup sequence with validation checkpoints — the 'Instructions' section is filler ('Clarify goals, constraints, and required inputs', 'Apply relevant best practices and validate outcomes') and steps are scattered across parallel sections. Not 4 because no overarching sequence connects install → configure → integrate → verify; not 2 because individual recipes do carry implicit failure handling.

3 / 5

Progressive Disclosure

The body inlines ~460 lines of reference material (error-code catalog, output formats, performance caching) that clearly belongs in separate files, and its only reference — 'resources/implementation-playbook.md' — does not exist in the bundle (no references/, scripts/, or assets/ directories at all). Not 1 because section headers make the document navigable; not 3 because the single provided reference is broken rather than merely unclear, and large catalogs remain inlined.

2 / 5

Total

11

/

20

Passed

Description

78%Weight 40%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.

A solid description that explicitly covers both what the skill does and when to use it, anchored by the specific tool name ShellCheck. The main weakness is mild genericity in the lead phrase ('Master ... configuration and usage') and 'fixing code issues', plus missing common trigger synonyms like bash or .sh.

Suggestions

Replace the generic lead 'Master ShellCheck static analysis configuration and usage' with concrete capabilities, e.g. 'Configure .shellcheckrc files, interpret SC error codes, and suppress false positives'.

Add natural trigger synonyms users would say: bash scripts, .sh files, pre-commit hooks, CI linting.

Sharpen the 'Use when' clause with user-mention phrasing such as 'when the user mentions shellcheck, shell scripts, or script linting'.

DimensionReasoningScore

Specificity

The description names the domain and lists several concrete actions — "setting up linting infrastructure, fixing code issues, or ensuring script portability" — though "Master ShellCheck static analysis configuration and usage" and "fixing code issues" are somewhat generic. Not 5 because coverage lacks concrete action specificity like 'extract text, fill forms, merge documents'; not 3 because more than 1-2 concrete actions are present.

4 / 5

Completeness

Both "what" ("Master 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") are explicitly present. Not 5 because the 'when' triggers lack the concrete user-mention phrasing of the 5 anchor; not 3 because 'when' is explicitly stated, not merely implied.

4 / 5

Trigger Term Quality

Good natural keywords: "ShellCheck", "linting", "static analysis", "shell script" — terms users would actually say. Not 5 because common variations like bash, .sh, pre-commit, CI/CD, or 'lint my script' are missing; not 3 because coverage goes beyond merely relevant to genuinely natural phrasing.

4 / 5

Distinctiveness Conflict Risk

Names the specific tool ShellCheck with distinct triggers (static analysis, linting infrastructure, shell script portability) — a clear niche with minimal conflict risk against other skills.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills-claude/skills/shellcheck-configuration/SKILL.md

Reviewed

Table of Contents

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.