Content
32%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a comprehensive but bloated reference document for POSIX shell scripting. Its main weakness is extreme verbosity with heavy repetition across sections (constraints, pitfalls, and best practices all cover the same bash-isms to avoid). It lacks a clear workflow, has no complete executable examples, and inlines far too much content that should be in separate reference files. The content reads more like a wiki article than an actionable skill for Claude.
Suggestions
Consolidate the overlapping sections (POSIX Constraints, Common Pitfalls, POSIX-Specific Best Practices) into a single concise reference table, and move detailed tool/reference lists to a separate bundle file.
Add a clear multi-step workflow: write script → run `shellcheck -s sh` → test with dash/ash → fix issues → re-validate, with explicit validation checkpoints.
Include at least one complete, executable example script (e.g., a portable argument-parsing template) rather than scattered one-liner snippets.
Move the tool lists, CI/CD integration details, embedded systems guidance, and references into separate bundle files (e.g., `resources/tools.md`, `resources/ci-cd.md`) and reference them from the main skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~300+ lines with massive repetition across sections. Many sections overlap (e.g., 'POSIX Constraints', 'Common Pitfalls to Avoid', 'POSIX-Specific Best Practices' all cover the same ground). Lists of tools, references, and focus areas are padded well beyond what Claude needs. Claude already knows most of these POSIX shell concepts. | 2 / 5 |
Actionability | Provides concrete inline code snippets and patterns (e.g., trap usage, positional parameters for arrays, portable conditionals), but most guidance is bullet-point lists rather than executable, copy-paste-ready scripts. No complete script example demonstrating the full workflow. Many items are high-level directives ('Sanitize user input before using in commands') without showing how. | 3 / 5 |
Workflow Clarity | No clear multi-step workflow is defined. The skill is a collection of categorized bullet points with no sequencing, no validation checkpoints, and no feedback loops. The 'Instructions' section is only 4 vague lines. The migration section hints at a workflow but lacks explicit steps with validation. For a skill that involves writing and validating scripts, there should be a clear write → lint → test → fix cycle. | 2 / 5 |
Progressive Disclosure | References `resources/implementation-playbook.md` but no bundle files are provided, making this a dead reference. The massive amount of content (tool lists, references, advanced techniques, migration guides, CI/CD integration) is all inlined in a single file when much of it should be split into separate reference documents. The structure has many section headers but the content is monolithic. | 2 / 5 |
Total | 9 / 20 Passed |