Despite thinking this is AI-generated, I agree but everything has a caveat.

Skills are good for instilling non-repeatable, yet intuitive or institutional knowledge.

MCP’s are great for custom, repeatable tasks. After 5-10 runs of watching my LLM write the same exact script, I just asked it to hardcode the solution and make it a tool. The result is runs are way faster and repeatable.

▲

ashraymalhotra 4 hours ago | parent | next [-]

You could hardcode the script as a file within a skill too right? Skills can contain code, not just markdown files.

▲

BenFrantzDale 4 hours ago | parent | prev | next [-]

> Skills are good for instilling non-repeatable, yet intuitive or institutional knowledge.

What about just putting that sort of thing in human-targeted documentation? Why call it a “skill” and hide it somewhere a human is less likely to look?

(Skills are nice for providing /shortcuts.)

▲

et-al 3 hours ago | parent | prev [-]

> Skills are good for instilling non-repeatable, yet intuitive or institutional knowledge.

Maybe I'm misinterpreting you, but can you explain this more? I've been using skills for repeatable tasks. Why an MCP instead?

	▲	robotobos 3 hours ago \| parent [-]
		If the model can figure it out with tokens, but my institutional knowledge MCP tool can do it with a few CPU cycles, it’s faster and deterministic and repeatable.