Using a skill instead of an MCP server makes sense when the API already exposes the right operations and the real gaps are operational rules. The trade-off is that pagination limits, retry stop conditions, and secret handling are model-followed instructions rather than runtime-enforced behavior. A small eval suite across supported agents would show whether those rules survive model and harness differences, especially when the correct action is to stop rather than retry.