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/shell-scripting/skills/shellcheck-configuration/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

40%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 body is well-structured and points to a real one-level reference file, but it functions as a table of contents rather than guidance: it contains almost no executable commands, no example ShellCheck invocation or output, and no sequenced workflow with validation. Its value depends almost entirely on the reader descending into details.md.

Suggestions

Add a minimal quick-start with copy-paste commands in the body, e.g. 'shellcheck script.sh' and 'shellcheck --shell=bash --enable=all script.sh', so the skill is actionable without opening the reference.

Include a short run/interpret/fix/re-run workflow with a validation checkpoint (run ShellCheck, read the SC#### code and message, apply the suggested fix, re-run until clean).

Enumerate the topics available in references/details.md (e.g., error-code catalog, suppression directives, CI/pre-commit integration) at the pointer so readers know when to descend, and trim the description-duplicating 'When to Use' bullets.

DimensionReasoningScore

Conciseness

The body is short and free of concept explanations Claude already knows, but the intro sentence ('Comprehensive guidance for configuring and using ShellCheck to improve shell script quality...') merely restates the frontmatter description, and the 8-bullet 'When to Use' list largely duplicates the description's triggers. This is 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the minor-trim level 4, since two sections are redundant with the description.

3 / 5

Actionability

The body gives only high-level hints: 'Run ShellCheck in CI/CD', 'Configure for your target shell', 'Enable strict mode - Use --enable=all with careful exclusions'. The sole concrete token is the --enable=all flag; there is no runnable command (e.g., 'shellcheck script.sh' or '--shell=bash'), no example output, and no error-code example — matching 'minimal concrete guidance; high-level hints but missing the specific steps to execute'. It is above level 1 only because it names the real tool and flag rather than being entirely abstract.

2 / 5

Workflow Clarity

No sequenced process exists anywhere in the body — the numbered 'Best Practices' are disconnected tips, not steps, and there is no run/interpret/fix/re-run loop or validation checkpoint. This lands at 'rough sequence present but many gaps; steps poorly defined; validation absent' (an implied order of set-up-then-fix is faintly present via the use-case bullets) rather than level 1's fully incoherent presentation, and well below the simple-skill exemption because the single action (how to actually run ShellCheck) is never made unambiguous.

2 / 5

Progressive Disclosure

The body is a lean overview with a clearly signaled, verified one-level-deep reference ('Detailed pattern documentation lives in references/details.md. Read that file when the navigation tier above is insufficient'), and that file exists in the bundle. It misses level 5 because the pointer does not enumerate what topics live in details.md (error codes, suppression directives, CI integration), so navigation depends on opening the file to discover its contents.

4 / 5

Total

11

/

20

Passed

Description

83%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 strong description: third-person, concise, with a clear what and an explicit multi-trigger 'Use when' clause anchored to a specific named tool. Minor improvements possible by adding natural synonyms ('bash', '.sh', 'linter') and making every trigger ShellCheck-specific.

DimensionReasoningScore

Specificity

The description names the domain ('ShellCheck static analysis configuration and usage for shell script quality') and several concrete actions ('setting up linting infrastructure, fixing code issues, or ensuring script portability'). It stops short of comprehensive coverage — error-code interpretation, suppression configuration, and CI integration from the body are absent — so it fits 'several specific actions; minor gaps' rather than the level-5 comprehensive anchor.

4 / 5

Completeness

It clearly answers 'what' ('Master ShellCheck static analysis configuration and usage for shell script quality') and 'when' with an explicit 'Use when' clause carrying three concrete trigger phrases, mirroring the level-5 anchor example. The 'when' is explicit and specific, not merely present, so level 4 does not fit.

5 / 5

Trigger Term Quality

Natural trigger phrases users would actually say are present: 'setting up linting', 'fixing code issues', 'ensuring script portability', 'shell script quality'. Coverage is good but misses common synonyms and extensions a user might say ('bash scripts', '.sh files', 'linter'), so it matches 'good keyword coverage; a few natural terms missing' rather than the level-5 anchor.

4 / 5

Distinctiveness Conflict Risk

Naming ShellCheck carves out a clear niche, but the trigger 'fixing code issues' is generic and overlaps with general code-quality/linting skills for other languages, matching 'mostly distinct; minor overlap risk with closely related skills'. It is not level 5 because not every trigger is ShellCheck-specific, and not level 3 because the tool name makes confusion with unrelated skills unlikely.

4 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

wshobson/agents

Path

plugins/shell-scripting/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.