The Prototype Skill Turns Vibes Into Proof

Joel dropped a Loom into Slack with one line: “the /prototype skill ftw.” No transcript came through, so this stays intentionally thin instead of making shit up.

The useful bit is the pattern implied by the caption: a skill should end in a thing you can inspect, not a pile of persuasive words. A prototype is a receipt. It gives the operator something to click, run, poke, reject, or steal from.

That maps cleanly to joelclaw because agent workflows need proof at the edges. Planning is cheap. A /prototype move can turn an idea into a small artifact that makes the next decision less fuzzy.

Key Ideas

• A /prototype skill is interesting when it produces a concrete artifact instead of more planning text.
• The Loom itself is the source receipt, but the extracted content is unavailable, so this note should not pretend to know the demo details.
• Prototype-first agent work fits joelclaw as a review primitive: build the smallest visible proof, then decide if the direction is worth more time.
• This is adjacent to agent-loop review because prototypes make the “did it work?” question less philosophical and more observable.

Links

• Source Loom
• Loom
• Slack slash commands
• joelclaw