Skills Aren't Just Knowledge. They're Commands.
2026-07-25claude-code, practice
You've caught yourself typing "and don't forget to run the linter" for the fourth time this week. That's the tell.
Most people treat skills as documents the model reads when relevant, but they can be workflows that take arguments instead, closer to a function call than a note.
Set the skill to manual invocation only, and put $ARGUMENTS (a placeholder that gets replaced with whatever you type after the command) in the body. Now /fix-issue 1234 runs the whole pipeline: pull the issue with the CLI, find the relevant files, implement, test, lint, commit, open the pull request.
That's the difference: a process that runs identically every time, instead of one that runs approximately every time depending on how you phrased it.
