I've thought that skills and small scripts > MCP for quite a while now, tried out MCP in the early days (official ones, ones i made for scripts i already had), but they always end up using more tool calls/tokens than if i had just written a script + skill for claude.

▲

eikenberry 2 hours ago | parent [-]

MCP seems like what you'd do when you want to encapsulate and share a skill+script in a standard way.

▲

zvoque 2 hours ago | parent | next [-]

personally if i have the need to move a skill/script, etc. to another one of my machines, i'll make a git repo for them (if they aren't already on git)

▲

speff an hour ago | parent [-]

This was one of the first ideas me and my team had for sharing skills and scripts. The problem is this is a very "why Dropbox and not FTP" answer.

The second you utter the word git, you may have lost 90% of your audience - depending on their background, of course. MCPs are a lot more non-tech friendly

	▲	zvoque an hour ago \| parent [-]
		yeah it 100% depends on who you'll be sharing them with, for me its just myself and a couple agents i have on a dedicated machine so git is ideal to keep versions matching when i update something on my daily driver

▲

noodletheworld 2 hours ago | parent | prev [-]

You can share a skill by copy pasting the text file to someone in slack.

Its not that hard.