bash-pro

Master of defensive Bash scripting for production automation, CI/CD pipelines, and system utilities. Expert in safe, portable, and testable shell scripts.

Quality

28%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agent/skills/bash-pro/SKILL.md

Quality

Discovery

22%

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 description relies heavily on self-promotional language ('Master of', 'Expert in') rather than describing concrete capabilities. It fails to provide any guidance on when Claude should select this skill and lacks specific actionable verbs describing what the skill actually does.

Suggestions

Replace vague claims with specific actions: 'Write defensive Bash scripts with error handling, create CI/CD pipeline scripts, build portable shell utilities, debug shell scripts'

Add explicit trigger guidance: 'Use when the user asks about Bash scripts, .sh files, shell automation, cron jobs, or CI/CD shell commands'

Remove first-person promotional language ('Master of', 'Expert in') and use third-person action verbs instead

Dimension	Reasoning	Score
Specificity	Uses vague, abstract language like 'Master of' and 'Expert in' without listing concrete actions. No specific capabilities are described - only broad domains like 'production automation' and 'CI/CD pipelines'.	1 / 3
Completeness	Partially addresses 'what' at a high level but completely lacks any 'when' guidance. No 'Use when...' clause or explicit trigger conditions are provided.	1 / 3
Trigger Term Quality	Contains some relevant keywords users might say ('Bash', 'CI/CD', 'shell scripts', 'automation') but missing common variations like 'bash script', '.sh files', 'cron jobs', 'deploy scripts', or specific commands.	2 / 3
Distinctiveness Conflict Risk	Bash/shell scripting is somewhat specific, but 'automation' and 'CI/CD' are broad terms that could overlap with many other skills (Python automation, deployment tools, etc.).	2 / 3
	Total	6 / 12 Passed

Implementation

35%

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

This skill is comprehensive but severely over-documented, explaining many Bash best practices that Claude already knows (quoting variables, using local, consistent naming). The content would benefit from aggressive trimming to focus on project-specific patterns, with concrete script templates replacing the extensive bullet-point lists. The sub-skill structure is promising but the main document should be a lean overview rather than duplicating detailed guidance.

Suggestions

Reduce content by 70%+ by removing explanations of standard Bash practices Claude already knows (variable quoting, naming conventions, indentation) and keeping only project-specific patterns or unusual requirements

Add 2-3 complete, executable script templates demonstrating the defensive patterns in context rather than isolated snippets

Move detailed sections (Safety & Security, Performance, Documentation Standards) into the referenced sub-skills and keep only a brief summary with links in the main file

Add explicit validation checkpoints to the Instructions workflow, e.g., 'Run ShellCheck before proceeding' with specific commands and expected output

Dimension	Reasoning	Score
Conciseness	Extremely verbose with extensive lists of best practices Claude already knows. Sections like 'Readability & Maintainability' explain basic coding conventions (snake_case, consistent indentation, descriptive names) that don't need explicit instruction. The document is over 200 lines of guidance that could be condensed to essential project-specific patterns.	1 / 3
Actionability	Contains some concrete code snippets (strict mode, script directory detection, NUL-safe patterns) but most content is descriptive bullet points rather than executable examples. Missing complete, copy-paste ready script templates that demonstrate the patterns in context.	2 / 3
Workflow Clarity	The 'Instructions' section provides a 4-step workflow but lacks validation checkpoints and feedback loops. For a skill involving potentially destructive operations (automation, CI/CD), there's no explicit 'validate before proceeding' step or error recovery guidance in the workflow itself.	2 / 3
Progressive Disclosure	References 7 sub-skills at the end which is good structure, but the main document is a monolithic wall of bullet points that should be distributed across those sub-skills. The 'Essential Tools' section header has no content before jumping to sub-skill links, suggesting incomplete organization.	2 / 3
	Total	7 / 12 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

Repository: Dokhacgiakhoa/antigravity-ide
Commit: 3395991

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