Skills can be about as deterministic. Consider GitHub MCP vs skill for GH CLI.
It might use the view_pr tool, or `gh pr view`, but in the end it's still performing a deterministic action.
The benefit might be that the GH skill can contain more domain specific information about GitHub, and you only pay the context cost when the skill is read.
Personally I generally avoid MCP and have skills for CLIs -- if one doesn't exist, then I author one. For example I have a CLI for Grafana, Discord, Sentry, etc.
If "fine" is what you need, then ok. It can stumble its way to everything eventually.
With a proper skill it can one-shot even complex commands that require poking to gh api because the basic command set doesn't work. Or it knows how to track a running CI workflow efficiently without having to try three different methods.
reply