The author argues against Skills becoming the standard for LLM capabilities, favoring Model Context Protocol (MCP) instead. While Skills work well for pure knowledge and teaching LLMs to use existing tools, MCP is superior for actual service access because it provides zero-install remote usage, seamless updates, better authentication, true portability, and natural sandboxing. Skills that require CLIs create deployment complexity, secret management nightmares, and fragmented ecosystems. The ideal approach uses MCP as connectors for service interfaces and Skills as pure knowledge manuals for workflows and context.