lint

Run shellcheck and actionlint on shell scripts and GitHub Actions workflows. Use before pushing or when fixing lint issues.

1.14x

Quality

86%

Does it follow best practices?

Impact

87%

1.14x

Average score across 6 eval scenarios

Securityby

Passed

No known issues

Quality

Content

72%

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

This is a solid, actionable skill with executable commands and clear structure for running shellcheck and actionlint on changed files. Its main weaknesses are a missing re-validation step after fixing lint issues and some minor verbosity in explaining concepts Claude already understands (like fixing issues and reporting changes).

Suggestions

Add an explicit re-run/verify step after fixing issues (e.g., 'Re-run the linting commands to confirm all issues are resolved before reporting') to close the feedback loop.

Trim the 'Handling Issues' section — 'Fix the issues' and 'Report what was fixed' are obvious to Claude; focus on the non-obvious guidance like the disable directive policy.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable commands, but includes some unnecessary framing ('Run linting tools on shell scripts and GitHub Actions workflows in this project') and the 'Handling Issues' section explains things Claude already knows (like fixing lint issues and reporting changes). Could be tightened.	2 / 3
Actionability	Provides fully executable bash commands for finding changed files and running both shellcheck and actionlint. The disable directive example with explanation is concrete and copy-paste ready.	3 / 3
Workflow Clarity	The two-step process (shellcheck then actionlint) is clearly sequenced, and the 'Handling Issues' section provides a fix workflow. However, there's no explicit validation/feedback loop — no step to re-run linting after fixes to confirm issues are resolved, which is important for a lint-fix-verify cycle.	2 / 3
Progressive Disclosure	For a simple, single-purpose skill under 50 lines with no need for external references, the content is well-organized into clear sections (shell scripts, workflows, handling issues, optional guidance). The structure is appropriate for the scope.	3 / 3
	Total	10 / 12 Passed

Description

100%

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

This is a strong, concise description that names specific tools and targets, includes natural trigger terms, and explicitly states both what the skill does and when to use it. It occupies a clear niche that is unlikely to conflict with other skills. The only minor improvement could be mentioning file extensions like .sh or .yml/.yaml for additional trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists specific concrete actions: 'Run shellcheck and actionlint' on specific targets: 'shell scripts and GitHub Actions workflows'. Names the exact tools and file types involved.	3 / 3
Completeness	Clearly answers both what ('Run shellcheck and actionlint on shell scripts and GitHub Actions workflows') and when ('Use before pushing or when fixing lint issues') with explicit trigger guidance.	3 / 3
Trigger Term Quality	Includes strong natural trigger terms users would say: 'shellcheck', 'actionlint', 'shell scripts', 'GitHub Actions workflows', 'lint issues', 'pushing'. These cover the main ways users would refer to this task.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive by naming specific tools (shellcheck, actionlint) and specific file types (shell scripts, GitHub Actions workflows). Unlikely to conflict with general linting or code quality skills due to the narrow, well-defined scope.	3 / 3
	Total	12 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: aaddrick/claude-desktop-debian
Commit: 2d1d0c5

Reviewed: 4 days 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.