Name: shellcheck-configuration
Rating: 58.4 (1 reviews)
Author: administrakt0r

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

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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

Quality

Content

57%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 a comprehensive, actionable ShellCheck reference with strong code examples, but it is overlong for SKILL.md, repeats error-code content, lacks explicit validation feedback loops in its batch workflows, and keeps material inline that should be split into referenced files.

Suggestions

Deduplicate the error-code material: keep one curated reference (ideally in a separate file) instead of listing codes in both 'Common ShellCheck Error Codes' and 'Common Violations and Fixes'.

Add explicit validation feedback loops to the CI/CD and pre-commit workflows (e.g., run shellcheck, on failure surface the offending script and SC code, fix, re-run) so batch operations clear the workflow-clarity cap.

Move the error-code reference and integration patterns into separate reference files under a real references/ directory and fix or remove the dangling 'resources/implementation-playbook.md' pointer.

Dimension	Reasoning	Score
Conciseness	Mostly efficient reference material, but error codes are documented twice (in 'Common ShellCheck Error Codes' and again in 'Common Violations and Fixes') and the 'What is ShellCheck?' section restates a concept Claude already knows, so it could be tightened past anchor 3.	3 / 5
Actionability	Provides abundant concrete, mostly copy-paste-ready code for installation, .shellcheckrc, CI/CD, pre-commit hooks, and suppression directives, with only minor gaps and illustrative-error examples keeping it below anchor 5.	4 / 5
Workflow Clarity	The 'Instructions' section offers a vague three-step process and the CI/pre-commit batch operations lack explicit validate-then-fix-then-retry feedback loops; per the rubric, batch operations without validation cap workflow clarity at 3.	3 / 5
Progressive Disclosure	Header structure is reasonable, but the bulk error-code reference and integration patterns are inlined when they belong in separate files, and the single external reference ('resources/implementation-playbook.md') is neither a real bundle file nor clearly signaled, fitting anchor 3.	3 / 5
	Total	13 / 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.

The description is third-person, clearly scoped to ShellCheck, and supplies both a concrete 'what' and an explicit 'Use when' trigger clause. It is strong overall, with only minor generic phrasing in the 'what' and a few missing trigger synonyms.

Dimension	Reasoning	Score
Specificity	Names the ShellCheck domain plus several actions ('setting up linting infrastructure, fixing code issues, or ensuring script portability'), though some phrasing like 'fixing code issues' remains generic, keeping it just below the comprehensive anchor 5.	4 / 5
Completeness	Both 'what' ('Master ShellCheck static analysis configuration and usage') and an explicit 'when' ('Use when setting up linting infrastructure, fixing code issues, or ensuring script portability') are present; the 'what' is slightly generic, fitting anchor 4 rather than 5.	4 / 5
Trigger Term Quality	Includes natural terms users would say ('ShellCheck', 'linting', 'shell script quality', 'static analysis', 'portability') with good coverage, but a few synonyms or file extensions are missing so it does not reach anchor 5.	4 / 5
Distinctiveness Conflict Risk	Targets a named, specific tool (ShellCheck) with clear distinct triggers and minimal overlap with other skills, matching the clear-niche anchor 5.	5 / 5
	Total	17 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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
Commit: 57c135b

Reviewed: 21 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.