Use the Skills API to make all your agents and platforms smarter.
Think of it as the npm registry for agent capabilities and extensibility. Free and open.
10:37 AM · Jun 5, 2026 · 67.8K Views
Sentiment
Sentiment building, check back later.
Cluster Engagement
Posts from X
Most Activity
Most Activity
VIEWS12.9KBOOKMARKS16LIKES65RETWEETS2REPLIES4
Guillermo Rauch@rauchg
Shoutout to @andrewqu founder and CEO of http://skills.sh 😁 you can just ship things
23hViews 12.9KLikes 65Bookmarks 16
Cooper@cooperawaken
@rauchg this is such a solid dev tool upgrade already claimed my cursor handle what kind of customizations are you rolling out for profiles next
23hViews 3Likes 1Bookmarks 1
David Oladapo@oladapodev
@rauchg @andrewqu Using this already 👍
22hViews 383Likes 2
cole murray@colemurray
@rauchg > Think of it as the npm registry
20hViews 76Likes 3
Charlie Molthrop@CharlieMolthrop
@rauchg Any favorites?
23hViews 21
Muruganantham K Mani@mmuruganandam
The npm analogy cuts both ways: registries gave us typosquatting and supply-chain attacks, and a skill is a hotter payload than a package — it's instructions injected straight into your agent's context. Treat skill installs like prod deploys: pin, review, eval. Exactly the failure mode we design around in @ozthra_ai Relay.
22hViews 95
- ben -@Benny_Jiang_
I was seriously thinking of building this and i had a quick prototype. I didn't further spending energy on this cuz of 3 issues 1. most skills are reused: at beginning i install a lot of skills at user level, and then just keep using what's working for me. searching from public space is less of a strong need. 2. skill ranking is hard. think of google works because of page rank. i figure semantic search + github star is much more noisy. you probly need to do really expension batch eval to verify what works or have enough traffic to do ranking. therefore, vercel has a much higher chance to make it work 3. internal skill >> public skills. skill is much more value if people within the same company use it to share the tribal knowledge.
still very happy Vercel did it otherwise i would always be curious how good it could be
20hViews 57
Maximiliano Moxarella@maxi_moxa
@rauchg @andrewqu shipping things is the only personality trait left in this industry
22hViews 55
Element Dong@elementdsj
@rauchg registry makes sense. but npm packages are deterministic. skills aren't. same version, different model, different reasoning.
22hViews 53
Tech News@tech_summaries
@rauchg npm won because installing beat writing from scratch. 600k skills at GA means agents hit that threshold on day one
23hViews 53
Spencer Dusebout@sdusebout
@rauchg Cool to see Vercel sees themselves as much more than just infrastructure.
23hViews 47
Guillermo Rauch@rauchg
@CharlieMolthrop Biased but the React and Next skills just keep getting better and better
23hViews 12Likes 1
Maximiliano Moxarella@maxi_moxa
@rauchg calling it the npm of anything is a threat not a feature
22hViews 34
Jessin Sam S@jessinvibe
@rauchg Let’s gooo
23hViews 31
Jangra@jxngrx
@rauchg So I can finally stop reinventing a 'fetch‑url' skill for every bot? Guess my agent will stop asking me for a coffee break. 😂💀
22hViews 29
Daniel Smidstrup@DanielSmidstrup
@rauchg Very fascinating point!
20hViews 27
Muhammad Ahtasham@ahtashammuzamal
@rauchg This is huge
http://Skills.sh API as the “npm registry for agents” is exactly what the ecosystem needs.
One unified way to make every agent massively more capable. Free & open is the cherry on top.
Smart move, Vercel. Already thinking of ways to use it
23hViews 27
Andrew Kordampalos@ckor
@rauchg I confirm!
23hViews 26
amunoz@alexmunoz1_
@rauchg I'd actually thought about this idea a while back a system to fetch skills' context via HTTP request, without having to install them through the CLI. Thanks a lot!
22hViews 23
Ferbin@Ferbin08
@rauchg shipping forces the real conversations. I run trading bots. The live market tells you what matters in an hour. Backtesting gets you confident but wrong. You have to deploy to actually learn.
22hViews 19
Load more posts