CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

posix-shell-pro

Expert in strict POSIX sh scripting for maximum portability across Unix-like systems. Specializes in shell scripts that run on any POSIX-compliant shell (dash, ash, sh, bash --posix).

50

Quality

63%

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/posix-shell-pro/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 rich with concrete, executable POSIX guidance but is over-long and redundant, with the same rules repeated across multiple sections. It lacks an explicit sequenced workflow with validation checkpoints and keeps all material inline rather than splitting detailed references into bundle files.

Suggestions

De-duplicate repeated guidance (quoting, [ vs [[, . vs source, printf vs echo) into a single canonical section and reference it elsewhere instead of restating.

Add an explicit end-to-end workflow with validation checkpoints, e.g. write -> `sh -n` syntax check -> `shellcheck -s sh` -> test on dash/ash -> fix -> re-test.

Move the large Essential Tools inventory and References & Further Reading into separate reference files (e.g. TOOLS.md, REFERENCES.md) and link to them one level deep to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The ~300-line body is noticeably verbose: the same guidance (quote expansions, use [ not [[, use . not source, printf over echo) is repeated across 'POSIX Constraints', 'Approach', 'Common Pitfalls', and 'POSIX-Specific Best Practices', creating padded redundant sections.

2 / 5

Actionability

Provides many concrete, executable snippets (e.g. `trap 'rm -f "$tmpfile"' EXIT INT TERM`, `case $num in *[!0-9]*) exit 1 ;; esac`, `command -v cmd >/dev/null 2>&1`); most are copy-paste ready, with only minor gaps where bullets stay fragmentary.

4 / 5

Workflow Clarity

'Approach' is a practice list rather than a sequenced workflow, and validation checkpoints are implicit; the Migration section offers a rough sequence but lacks explicit validate-fix-retry loops, so workflow clarity sits at the cap of 3 for validation gaps.

3 / 5

Progressive Disclosure

Sections are well-organized with clear headers, but everything is inlined in one large file with no one-level-deep references to bundle files; content like the Essential Tools inventory and Migration guide that could live in separate references is inline.

3 / 5

Total

12

/

20

Passed

Description

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

The description clearly communicates a focused POSIX-shell-portability niche with good natural trigger terms, but lacks an explicit 'Use when...' clause and lists few concrete actions. It is mostly distinct from adjacent shell skills but would benefit from explicit trigger guidance.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when writing or debugging portable shell scripts, migrating bash to POSIX sh, or targeting dash/ash/BusyBox.'

List 2-3 concrete actions (e.g. writes, validates with ShellCheck -s sh, migrates bash scripts to POSIX sh) to lift specificity.

Include common synonyms like 'portable shell script' and 'sh script' to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the domain ('strict POSIX sh scripting') and a concrete framing (portable scripts across dash, ash, sh, bash --posix), but stops short of listing multiple concrete actions like writing, validating, or migrating scripts.

3 / 5

Completeness

Clearly states what the skill does, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Includes natural terms users would say ('POSIX sh', 'shell scripts', 'dash', 'ash', 'sh', 'bash --posix', 'Unix-like systems'); a few common synonyms like 'portable shell' or 'sh script' are absent.

4 / 5

Distinctiveness Conflict Risk

The strict-POSIX-portability niche is fairly distinct with specific shell triggers, though it carries minor overlap risk with a general bash/shell-scripting skill.

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

rmyndharis/antigravity-skills

Path

skills/posix-shell-pro/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.