writing-clean-shell
Skill0 starsChanged 3 months agoNo licenceView on GitHub
Expert in organizing shell scripts so anyone can read, update, and maintain them. Use this skill whenever you write or create any shell script (bash, zsh, sh, or PowerShell, on Linux, macOS, or Windows), and whenever you edit, refactor, clean up, or reorganize an existing script, make a script readable or maintainable, add flags, options, or a help screen to a script, structure a main function or orchestrator, or split a monolithic script into functions - even if the user never mentions organization or clean code, and even for a quick one-off script. The skill also runs a full cleanup checklist (commands/cleanup.md) that checks every rule and fixes violations when the user asks to clean up, review, or validate a shell script. Covers function extraction, verb-first naming, guard clauses, sequential orchestrators, print_usage help screens, and consistent output vocabulary. This is an organization skill, not a syntax skill: the principles apply to any shell on any platform.
In this repository11 other files it gives its agents.
- ai-documentationSkill
- commit-messageSkill
- mom-test-coachSkill
- mono-repo-typescriptSkill
- orchestrating-ts-agentsSkill
- planning-storiesSkill
- plantuml-diagrammingSkill
- speed-datingSkill
- writing-clean-tsSkill
- writing-tech-specsSkill
- writing-woodpecker-ciSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

