lint

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

1.14x

Quality

—

Does it follow best practices?

Impact

87%

1.14x

Average score across 6 eval scenarios

Securityby

Passed

No known issues

Quality

Content

87%

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

A tight, actionable skill body with executable code and clean organization, weakened only by the absence of an explicit re-lint validation loop after fixes.

Suggestions

Add an explicit validation checkpoint in 'Handling Issues' directing Claude to re-run shellcheck/actionlint after fixes to confirm a clean result before reporting done.

Clarify the changed-file scope when 'git diff' returns nothing (no main branch or fresh repo) so the workflow has a defined fallback path.

Note how to surface linter exit codes / aggregate results so Claude reports failures deterministically rather than per-file ad hoc.

Dimension	Reasoning	Score
Conciseness	Lean body with no concept re-explanation or padding; every section earns its place and assumes Claude's competence.	3 / 3
Actionability	Both bash blocks are concrete, executable, and copy-paste ready with real git/shellcheck/actionlint commands rather than pseudocode.	3 / 3
Workflow Clarity	Steps are listed in 'Handling Issues' but a batch linting operation lacks an explicit re-run-to-confirm-clean validation checkpoint, capping clarity at 2 per the feedback-loops note.	2 / 3
Progressive Disclosure	A simple sub-50-line skill with well-organized sections and no bundle files; structure is clear and one-level, warranting a 3 for simple skills.	3 / 3
	Total	11 / 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.

A concise, specific description that states concrete actions and an explicit use-when trigger, covering both what and when without fluff. It is clearly distinct from adjacent skills.

Dimension	Reasoning	Score
Specificity	Names two concrete actions — 'Run shellcheck' on shell scripts and 'actionlint' on GitHub Actions workflows — matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers what ('Run shellcheck and actionlint...') and when ('Use before pushing or when fixing lint issues'), satisfying both halves.	3 / 3
Trigger Term Quality	Natural terms a user would say are well covered: 'shellcheck', 'actionlint', 'shell scripts', 'GitHub Actions workflows', 'lint issues', and 'pushing'.	3 / 3
Distinctiveness Conflict Risk	A clear niche (linting shell + GitHub Actions) with distinct triggers; unlikely to fire for the wrong skill.	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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: aaddrick/claude-desktop-debian
Commit: 6bcf6bd

Reviewed: about 5 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.