CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

shell-script-reviewer

Reviews Bash, Zsh, and Fish shell scripts for bugs, security vulnerabilities, portability issues, and style violations against the Google Shell Style Guide, ShellCheck, BashPitfalls, and shell-specific idiom conventions. Use when the user asks to review, audit, lint, or improve a .sh/.bash/.zsh/.fish file, or pastes shell script content for feedback.

Quality

95%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%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.

An exceptionally well-structured review skill: executable commands, a validated workflow with feedback loops, and model progressive disclosure (a 'when to read' table plus conditional-loading guidance, with all nine bundle files present, real, and consistent with the body's claims). The only weakness is mild redundancy around the set -e/-u stance, which keeps conciseness just below the top anchor.

Suggestions

State the set -e/set -u anti-pattern stance once in the intro (with the reference pointer) and have Steps 3b and --fix reference it by name instead of restating it.

Trim the opening framing paragraph ('grounded in named authorities rather than ad-hoc opinion') to one clause; the named-authority table and closing goal statement already carry this point.

Consider compressing the output skeleton's severity placeholder sections (### High/### Medium/### Low '...') into a single annotated placeholder to save ~10 lines without losing the template.

DimensionReasoningScore

Conciseness

The body is procedural, assumes Claude's competence, and wastes nothing on shell tutorials. However, the set -e/set -u error-handling stance is restated in three places (intro, Step 3b, and the --fix ordering) and the opening framing paragraph could be trimmed — minor instances of over-explanation, matching the 4 anchor rather than the every-token-earns-its-place of 5.

4 / 5

Actionability

Fully executable guidance throughout: concrete wrapper invocations (scripts/detect_shell.sh <file>, scripts/run_shellcheck.sh <file> [bash|sh]), exact fix commands (shfmt -w -i 2 -ci -bn -sr --, diff | patch -p1), a copy-paste output skeleton, and named ShellCheck codes (SC3045). All commands reference verified bundle scripts, matching the 5 anchor.

5 / 5

Workflow Clarity

Steps 1–5 are clearly sequenced (dialect detection → static analysis → prioritized manual review → structured output → escalation), with explicit validation checkpoints: static analysis runs before and is re-run after --fix to confirm, --fix requires user confirmation before applying, and the escalation rule handles disagreement and runtime-dependent constructs — a genuine feedback loop matching the 5 anchor.

5 / 5

Progressive Disclosure

A reference table with a 'When to read' column, explicit conditional-loading guidance ('Load only the file(s) relevant to the current script'), and one-level-deep references — all nine bundle files exist and their contents match the body's claims (e.g., the scripts' header comments confirm the zsh-via-bash and shfmt-flag behavior). Content is appropriately split with detail pushed to references, matching the 5 anchor.

5 / 5

Total

19

/

20

Passed

Description

100%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: concrete capabilities, named authorities, explicit use-when triggers with synonyms and extensions, and a distinct niche. It mirrors the best practice examples in structure and density without padding.

DimensionReasoningScore

Specificity

The description lists four concrete review actions ("bugs, security vulnerabilities, portability issues, and style violations") across three named dialects (Bash, Zsh, Fish) with named authorities (Google Shell Style Guide, ShellCheck, BashPitfalls). Coverage is comprehensive for a reviewer skill with no gaps, matching the 5 anchor rather than the 'minor gaps' of 4.

5 / 5

Completeness

It explicitly answers what ("Reviews Bash, Zsh, and Fish shell scripts for...") and when ("Use when the user asks to review, audit, lint, or improve a .sh/.bash/.zsh/.fish file, or pastes shell script content for feedback") with concrete trigger phrases — the exact structure of the 5 anchor.

5 / 5

Trigger Term Quality

It includes natural synonyms users would say ("review, audit, lint, improve"), file extensions (.sh/.bash/.zsh/.fish), and a paste-content trigger, matching the 5 anchor's comprehensive coverage of natural terms including synonyms and file extensions.

5 / 5

Distinctiveness Conflict Risk

A clear niche (shell script review for three named shells) with distinct, specific triggers (dialect names and file extensions) gives minimal conflict risk with other skills. Third-person voice throughout, so no voice penalty applies.

5 / 5

Total

20

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

rikdc/ai-skills

Path

plugins/dev-skills/skills/shell-script-reviewer/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.