SKILLEMALL.ai
GitHub ↗ RU Sign in

AB zx

Comprehensive guide for writing shell scripts with Google zx — a tool for writing better scripts using JavaScript/TypeScript. Use when writing, debugging, or refactoring zx scripts (.mjs, .js, .ts files using zx), executing shell commands from JavaScript, working with ProcessPromise/ProcessOutput APIs, piping streams, configuring zx options, or using zx CLI. Do NOT use for general Node.js questions unrelated to shell scripting.

LeoYeAI/openclaw-master-skills Agent Skills author: LeoYeAI MIT 7 files body ≈ 2 170 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Comprehensive guide for writing shell scripts with Google zx — a tool for writing better scripts using JavaScript/TypeScript.

As a process B 66/100 · Nearly there — weak spots: inputs and preconditions, running it twice

GeneratorSoftware developmenttype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
A
98/100
safety, quality, tests
Safety 60%
100
Quality 40%
95
Run on models
none yet
Process rating
B
66/100
Nearly there
Inputs and preconditions w 11
0
Running it twice w 4
30
Failures and branches w 10
50
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 0

    ✓ No critical or high findings

    Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 66/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 30Running it twice. 1 mutating operations with no state check
    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
    • 60Result and completion. Output format stated, no completion criterion
    • 85Steps. 4 steps, 2 vague phrases
    • 100When it triggers. States when to use and when not to
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2170 tokens
    • 100Progress reporting. Reports progress

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +1No license
    • +2Single-language instructions
    • +4Description says when NOT to use the skill
    • +3Description length 432: enough signal without eating the budget
    • +4Structure: 19 headings
    • +3Step-by-step instructions: 4 items
    • +3Output format is stated explicitly
    • +4Has examples (14 code blocks)
    • +4Reference files are cited in the instructions (4 of 4)

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 95.