1. Skills Superior to MCPs/Tools
Skills praised for simplicity, context efficiency, composability, and on-demand loading vs. token-heavy MCPs.
"much bigger deal long-term than e.g. MCP" (cube2222); "This is much better than MCP, which also stuffs every session's precious context with potentially irrelevant instructions" (wahnfrieden); "Skills are much simpler than mcps, which are hopelessly overengineered" (Sammi).
2. Practical Use Cases & Customization
Custom skills for workflows (e.g., DB access, PRs, testing, niche tools) enable reusability and team sharing.
"the ones I create myself... very specific and proprietary. For instance, a skill on how to write a service in my back-testing framework" (frankc); "skills: writing tests, fetching sentry info, using playwright... submitting a PR according to team conventions" (JamesSwift); "a skill to access your database for testing purposes" (jonrosner).
3. Verifiability & Token Concerns
Free-form Markdown hinders evaluation; index bloats context despite on-demand promise.
"free-form nature of the 'body' part... lead to an inevitably unverifiable process?" (mikaelaast); "skill descriptions are all essentially prompt injections... add to your input tokens on every agentic turn" (btown); "the index seems as much a liability as a boon. Keeping the context clean... is one of the most important things" (Sammi).