Skills as "intelligent" shell scripts

Almost every dev team has them: small shell scripts for routine tasks. They work great, as long as everything is exactly the way the author imagined back then.

A typical example from our day-to-day work:

"Grab the highest-priority ticket from project X and create a branch for it."

As a shell script, that means: knowing the exact project ID, calling the API, parsing JSON, sorting, turning the ticket title into a valid branch name (umlauts! special characters!), checking for uncommitted local changes first … You quickly end up with 80 lines of Bash, and it still breaks on the first edge case.

As a skill, the call looks like this:

/ticket-branch webshop

Behind it is a SKILL.md with a few sentences of plain text, roughly:
"Find the project in the ticket system that best matches $ARGUMENTS. Take the open ticket with the highest priority. Check that the working tree is clean. Create a branch following the pattern feature/<ticket-number>-<short-title> and briefly summarize the ticket."

Claude accesses the ticket system via an MCP connection. Everything else is description instead of programming.

Why "intelligent"?

🔍 Fuzzy input: "webshop" also finds "Webshop Relaunch 2026". Multiple matches? Claude asks instead of failing.

🧩 Edge cases handled with judgment: Two tickets with the same priority? Uncommitted changes? Branch already exists? Claude recognizes the situation and responds sensibly.

✍️ More than just execution: deriving a clean branch name from the title, summarizing the ticket, and on request proposing a first implementation plan right away.

📝 Maintainable for everyone: changing the workflow means editing a sentence in Markdown, not debugging Bash.

To be fair: shell scripts aren't obsolete. They're deterministic, fast, and cost zero tokens.

My rule of thumb:

• Exactly the same steps every time, no decisions needed? Script.
• Fuzzy input, edge cases, judgment required? Skill.

The best part: it's not either/or. A skill can bundle and call its own scripts. The script handles the tedious parts reliably, Claude takes care of everything that requires thinking.

Which of your shell scripts would you turn into a skill first? I'd love to hear your ideas in the comments

Join the discussion on LinkedIn →