Skip to main content
skill CX Codex

shellscript-coder — Claude Code skill: features and installation

shellscript-coder — a Claude Code skill for writing and refactoring shell scripts and command-line tools. It applies to automation, Git helpers, and infrastructure tasks.

Apache-2.0 ★ 869 updated 2026-11-16

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add sno-ai/sno-station-skills --skill shellscript-coder -a claude-code
Open on GitHub

What shellscript-coder does

This skill guides work on Bash scripts, command-line utilities, process wrappers, and automation. It calls for reading the target script, its callers, libraries, and nearby tests before editing. When a task changes a tool version, the relevant release notes and current official documentation inform the change.

Its guidance covers failure handling, temporary files, locks, argument safety, bounded retries, and output intended for agents. In JSON mode, stdout carries the result while diagnostics go to stderr. Checks start with changed files and focused tests; a full suite requires the owner's explicit request. The setup requires shell access and file read-write access.

What it helps with

  • write Bash scripts that validate arguments and dependencies
  • refactor a CLI tool while preserving repository conventions
  • handle timeouts, retries, and partial failures
  • separate JSON output from diagnostic messages

Example prompts for the agent

  • Write a Bash script for this task after inspecting its callers and tests.
  • Refactor this process wrapper without changing repository conventions.
  • Add a --json mode and clear failure handling to this CLI tool.

How to install shellscript-coder

1Skills CLI (Vercel)

npx skills add sno-ai/sno-station-skills --skill shellscript-coder -a claude-code

2Manually: put the files in place

~/.claude/skills/shellscript-coder/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/shellscript-coder/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about shellscript-coder

How do I install shellscript-coder in Claude Code?

Run npx skills add sno-ai/sno-station-skills --skill shellscript-coder -a claude-code. The skill file is located at ~/.claude/skills/shellscript-coder/SKILL.md.

What does shellscript-coder do?

It guides the creation and refactoring of Bash scripts, CLI tools, and automation. Its guidance addresses failure handling, logs, and machine-readable output.

What does shellscript-coder need to run?

It requires shell access and the ability to read and write files.

Source text

SKILL.md · Apache-2.0
---
name: shellscript-coder
description: "Implement and refactor production shell scripts, command-line tools, automation, process wrappers, and Git or infrastructure helpers with reliable failures, useful logs, and machine-readable output."
requires:
  programs: []
  harness:
    - {slot: 4.shell, need: required}
    - {slot: 4.file-read-write, need: required}
---

# Shell Script Coder

Every development task has a finite budget including setup, tests, and reporting.
Before running tests, estimate duration from available timings and identify the changed
behavior or directly affected consumer. If timing is unknown, state an estimate; do not
build a timing system or run a preliminary suite. Full evaluation, unit, integration,
or repository suites require the owner's explicit request, never a skill, PRD, review,
or default command. Remove checks that neither prove the requested main function nor
expose its defects. Repeat only after a relevant change or failure.
Every new security check requires the owner's explicit approval for that specific check;
remove auxiliary security, assertion, hash, or bookkeeping blockers of useful work.


Write small, production-grade Bash that fits the repository and remains understandable during failure. Local instructions define the runtime and style; they may strengthen these rules but not weaken reliability.

## Read Before Writing

- Confirm the required shell from the shebang, callers, CI, and repository docs. Use Bash when the target is Bash; do not claim POSIX portability unless it is required and tested.
- Read the complete target script, immediate callers, sourced libraries, config, and nearby tests. Reuse existing argument, logging, state, and error conventions.
- Before changing a tool version, or using a third-party CLI, API, or service in a way neither the PRD nor existing scripts already show, read its current official documentation; for a version change, read the release notes between the two versions. Name the page and version in the report. When a PRD governs the work and lacks or contradicts that fact, add it to the PRD's execution notes.
- Decide the observable success result, failure result, exit codes, and verification command before editing.
- Preserve unrelated work. Touch only requested behavior and remove only orphans created by the change.

## Boundaries

- No backward-compatibility aliases, dual paths, legacy flags, or fallbacks unless the user confirms an external published contract requires them.
- No speculative options or abstractions. Prefer one explicit path over a configurable framework.
- Use deterministic shell or an existing deterministic helper for routing, parsing, retries, validation, and state transitions. Never ask a model to decide them.
- Never use `eval` or construct executable commands in strings. Use functions and arrays.
- Never print secrets, tokens, credential-bearing URLs, raw environment dumps, or sensitive command lines.

## Reliability

- Start new Bash scripts with `set -Eeuo pipefail` unless a documented caller contract makes one option incompatible. Handle expected nonzero statuses locally instead of globally weakening failure behavior.
- Quote every expansion unless intentional word splitting is proven and commented. Use arrays for argument lists, `--` before user-controlled paths, `[[ ... ]]` for tests, and `printf` rather than `echo` for data.
- Validate required arguments, enums, paths, and dependencies before mutation. Reject unknown flags and malformed state with a specific message and nonzero exit.
- Keep functions focused, use `local`, pass values explicitly, and avoid hidden mutable globals. Constants are uppercase and readonly where practical.
- Clean temporary files, locks, mounts, and child processes with traps or an explicit cleanup function. Preserve the original exit status.
- Write durable files atomically: create in the destination directory, flush when required, then rename. Never expose a partially written state file.
- Use `flock` or the repository's existing lock for shared state. Keep the critical section narrow and define what a lock timeout means.
- Make retryable operations idempotent. Bound retries, use a fresh observation before retrying, and distinguish “already completed” from “failed.”
- Bound external commands with a timeout when they can hang. Propagate signals to children and verify termination when orphaned processes would be harmful.
- For work that may exceed two minutes, emit per-unit progress with completed/total, rate, and ETA.

## Messages and Agent-Facing Interfaces

Design messages as operational evidence, not narration.

- Keep stdout reserved for the primary result. Send progress, diagnostics, and errors to stderr. If `--json` is supported, stdout contains exactly one valid JSON result and no decoration.
- Error messages name: operation, target, failed condition, consequence, and the next safe action. Include relevant identifiers and paths; omit secrets and noisy stack traces unless a debug mode already exists.
- Progress messages identify the current stage and include stable context so a detached AI agent can tell which task and resource produced the line.
- Use stable, documented exit codes when callers branch on failure classes. Otherwise use `0` for success and a small nonzero set; do not invent dozens of codes.
- Prefer non-interactive flags and stdin over prompts. A command intended for agents must support `--help`, reject missing inputs immediately, and never wait silently for a terminal response.
- Make input contracts explicit: required flags, accepted values, path ownership, preconditions, and whether rerunning is safe.
- Make output easy to inspect and bind to the action. For a new JSON interface, prefer a minimal envelope such as `ok`, `operation`, `target`, and either `result` or `error`; include recorded commits, digests, or state paths when they are the proof a controller needs.
- Generate JSON with `jq` or another repository-standard encoder, never by string concatenation.

## Failure Design

For every external command or multi-step mutation, answer:

1. What can fail or time out?
2. What state may already have changed?
3. Can the exact operation be retried safely?
4. What evidence lets an AI agent choose retry, repair, or stop?

Fail closed for publication, deletion, credentials, shared state, and Git ref movement. A partial success must be recorded explicitly; do not collapse it into a generic failure that encourages a destructive retry.

## Verification

Run the narrowest relevant checks first:

1. `bash -n` on every touched Bash file.
2. The repository's ShellCheck or code-check command when configured; do not add a new lint dependency just for ceremony.
3. Focused tests for one accepted path and the nearest rejected boundary.
4. When relevant, tests for timeout, interruption, retry/idempotency, concurrent writers, paths with spaces, and partial failure.
5. Stop after the affected checks pass; the repository's default suite is not permission to expand the test scope.

Use temporary directories, local bare Git remotes, and boundary fakes that assert observable behavior. Do not mock repository-internal logic. Re-read the final diff and remove any line that does not improve required correctness, diagnostics, or operability.

## Delivery

Report the changed behavior, input/output contract, important failure semantics, and exact verification commands with results. State any unverified external dependency plainly; never report success over a failing or skipped required check.
<!-- reminders:start -->
<!-- reminders:end -->

© sno-ai · Apache-2.0 · sno-ai/sno-station-skills

Similar skills

All skills for Programming languages →

From the same set40

The whole set →
away-brief The away-brief Claude Code skill creates a short report on completed work, blockers, pending questions, and quota readings. It runs when someone asks what happened while they were away. CX Codex +1 ★ 869repo stars agentic-time-estimate agentic-time-estimate — a Claude Code skill that estimates an AI agent’s total runtime or remaining work from measured progress. It gets owner-facing clock times from sno report-time and never estimates human developer time. CX Codex +1 ★ 869repo stars ts-coder The ts-coder Claude Code skill guides TypeScript and TSX implementation and refactoring within an existing repository. It applies to work on types, APIs, and migrations. CX Codex +1 ★ 869repo stars test-writer test-writer — a skill for Claude Code writes and improves test code. It activates when Codex is asked to add or change tests. CX Codex +1 ★ 869repo stars rust-coder The rust-coder Claude Code skill implements and refactors Rust code using the project’s own conventions. It activates for feature work, migrations, and substantial edits to .rs files or Cargo.toml. CX Codex +1 ★ 869repo stars python-coder The python-coder skill for Claude Code guides Python implementation and refactoring, including work with FastAPI and Pydantic. It applies to async code and migration tasks. CX Codex +1 ★ 869repo stars owner-intent-audit The owner-intent-audit Claude Code skill checks plans, tests, and code against the project owner’s intent. Run it before approving or merging agent work. CX Codex +1 ★ 869repo stars less-is-more less-is-more — a skill for Claude Code that keeps code changes small and trims overbuilt solutions. It activates for coding, bug fixes, refactors, and diff reviews. CX Codex +1 ★ 869repo stars

Project sponsors

Companies that keep this analytics open