CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bash-defensive-patterns

Master defensive Bash programming techniques for production-grade scripts. Use when writing robust shell scripts, CI/CD pipelines, or system utilities requiring fault tolerance and safety.

Quality

62%

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 ./skills/bash-defensive-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

42%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 with sensible scope, anti-scope, safety, and limitation sections, but it functions as a stub: every concrete technique is deferred to a playbook file that is missing from the bundle, leaving no executable guidance. Redundant sections (duplicated reference and approval bullets) also dilute an otherwise lean layout.

Suggestions

Add the referenced bundle file resources/implementation-playbook.md (or fix the path) so the deferred patterns, checklists, and templates actually exist; remove the duplicate mention in the Safety section.

Include at least a few executable anchors inline, e.g., `set -euo pipefail`, a `trap ... ERR EXIT` example, and a quoted-variable file-handling pattern, so the skill is actionable even without the playbook.

Consolidate the duplicated destructive-operation approval guidance (Instructions step 5 vs. the Safety section) and trim the overlapping use-case bullets and intro paragraph that restate the description.

DimensionReasoningScore

Conciseness

The body is compact but contains clear redundancy: the intro paragraph restates the frontmatter description, the reference to "resources/implementation-playbook.md" appears twice (in the Safety tail and the Resources section), and the destructive-operation approval bullet is duplicated between Instructions step 5 and Safety. Mostly efficient but could be tightened, matching the 3 anchor rather than 4 where over-explanation is only minor.

3 / 5

Actionability

Instructions are high-level hints — "Enable strict mode and safe defaults from the start", "Validate inputs, quote variables, and handle files safely", "Add logging, error traps, and basic tests" — with no executable commands or code (e.g., no `set -euo pipefail` or trap example), and all concrete patterns are deferred to a playbook file that does not exist in the bundle. This matches the 2 anchor (minimal concrete guidance, missing specific steps) rather than 3, since there is not even partial or pseudocode-level executable content.

2 / 5

Workflow Clarity

A coherent 5-step sequence exists (confirm environment → strict mode → validation → logging/traps/tests → approval for destructive ops), but checkpoints are implicit: "basic tests" is undefined and there is no validate-then-proceed or fix-and-retry loop, which the destructive/batch-operation guidance in this skill makes important. The missing explicit validation keeps it at 3 rather than 4.

3 / 5

Progressive Disclosure

Sections are well organized and the body correctly defers detail to a one-level-deep reference, but that reference ("resources/implementation-playbook.md") does not exist in the bundle — no resources/, references/, scripts/, or assets/ directories are present — so the pointer resolves to nothing and is stated twice. Structure is present yet the broken, duplicated reference prevents a 4.

3 / 5

Total

11

/

20

Passed

Description

65%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 well-formed description with an explicit 'Use when' clause, natural trigger terms, and a distinct niche. Its main weakness is specificity: it describes the domain and its qualities but never names the concrete techniques (strict mode, error traps, input validation) the skill actually provides.

Suggestions

Enumerate 2-3 concrete capabilities in the description, e.g., "Implements strict mode (set -euo pipefail), error traps, input validation, and safe file handling in Bash scripts."

Add natural trigger terms users commonly say, such as "error handling", "make my script fail-safe", or ".sh files", to broaden keyword coverage.

Keep the third-person, imperative style but replace the abstract "Master... techniques" framing with the specific actions the skill performs.

DimensionReasoningScore

Specificity

"Master defensive Bash programming techniques for production-grade scripts" names the domain but lists no concrete techniques (e.g., strict mode, error traps, input validation); the trailing "requiring fault tolerance and safety" is an attribute, not an action. It sits at the 'names the domain, actions generic' anchor rather than 3 because no specific capability is enumerated, and not 1 because the domain and scope are clearly stated.

2 / 5

Completeness

Both parts are present: the what ("Master defensive Bash programming techniques for production-grade scripts") and an explicit when ("Use when writing robust shell scripts, CI/CD pipelines, or system utilities..."). Not 5 because the 'what' is abstract and lacks concrete trigger capabilities; not 3 because the when clause is explicit, not merely implied.

4 / 5

Trigger Term Quality

"robust shell scripts", "CI/CD pipelines", "system utilities", "fault tolerance and safety" are phrases users would naturally say when needing this skill. Not 5 because common variations like "error handling", "shell scripting", or file extensions like ".sh" are missing; not 3 because coverage goes beyond a couple of generic keywords.

4 / 5

Distinctiveness Conflict Risk

"defensive Bash programming" with "fault tolerance" carve out a distinct niche that is unlikely to trigger for unrelated skills. Minor overlap risk remains with general Bash/scripting or general code-quality skills, which keeps it below the 5 anchor.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

sickn33/agentic-awesome-skills

Path

skills/bash-defensive-patterns/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.