- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add sno-ai/sno-station-skills --skill shellscript-coder -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add sno-ai/sno-station-skills --skill shellscript-coder -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add sno-ai/sno-station-skills --skill shellscript-coder -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add sno-ai/sno-station-skills --skill shellscript-coder -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/sno-ai/sno-station-skills/tree/HEAD/plugins/sno-station-standalone/skills/shellscript-coderFrom the publisher
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.
eval or construct executable commands in strings. Use functions and arrays.set -Eeuo pipefail unless a documented caller contract makes one option incompatible. Handle expected nonzero statuses locally instead of globally weakening failure behavior.-- before user-controlled paths, [[ ... ]] for tests, and printf rather than echo for data.local, pass values explicitly, and avoid hidden mutable globals. Constants are uppercase and readonly where practical.flock or the repository's existing lock for shared state. Keep the critical section narrow and define what a lock timeout means.Design messages as operational evidence, not narration.
--json is supported, stdout contains exactly one valid JSON result and no decoration.0 for success and a small nonzero set; do not invent dozens of codes.--help, reject missing inputs immediately, and never wait silently for a terminal response.ok, operation, target, and either result or error; include recorded commits, digests, or state paths when they are the proof a controller needs.jq or another repository-standard encoder, never by string concatenation.For every external command or multi-step mutation, answer:
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.
Run the narrowest relevant checks first:
bash -n on every touched Bash file.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.
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.
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.
---name: shellscript-coderdescription: Implement and refactor production shell scripts, command-line tools, automation, process wrappers, and Git or…---# plugins/sno-station-standalone/skills/shellscript-coder/SKILL.mdFAQ
Download plugins/sno-station-standalone/skills/shellscript-coder/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/sno-ai/sno-station-skills.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.