Co-Founder and COO of @Chilli_Cream. GraphQL TSC. Usually yes, occasionally no.

Switzerland
Hey @kzu 👋We published skillz, a .NET CLI for managing AI agent skills (`npx skills` but .net). Saw you own the unlisted `skills` package on NuGet. Would you be open to transferring it? Currently you can use skillz via `dnx skillz`, but `dnx skills` would make a lot more sense
2
1
3
174
Sure thing! I'd like to contribute too, it's been in my backlog for a while. Would you be ok co-owning the package? I've been wondering what could it offer that goes beyond being an "npx skills" clone ;).
1
60
Amazing! Yes, let's do it! We've got a some cool ideas. Distribution of agents skills together with the nuget packages is one :) My dm's are open - let's coordinate this and get started 🚀
1
10
Checkout the new MCP integration into our #graphql cockpit nitro 🚀
50
Pascal Senn 🌶 retweeted
What a great day at GraphQL Day Amsterdam! Thanks to everyone who joined us, and a huge shoutout to the team for all their hard work in making it happen. #GraphQL @APIdaysGlobal
3
8
1,957
With Fusion & HotChocolate 16, we're launching a new MCP adapter to expose GraphQL operations as MCP tools. We're also adding support for the MCP Apps standard for building agentic UI components. Check out the latest post for all the details: chillicream.com/blog/2026/05…
94
AI agents can call APIs, but can they actually understand them? @Pascal_Senn shows why #GraphQL is such a strong fit for agents when using semantic introspection for huge production schemas. This one is worth watching 👇 piped.video/2Ud1gxUpgrY
53
@michael_staib and me will be at GraphQL Day in Amsterdam on June 9th and 10th. We still have a few free tickets for you! Send me a DM if you are interested. See you there! Find out more: graphql.org/day/2026/amsterd…
1
1
109
fate 1.0: The first full Async React Metaframework New in 1.0: * Zero-Config Live Views via SSE * Drizzle Support * "Native" HTTP support (no tRPC) * Void Router * Vite plugin * Clientside Garbage Collection * Performance & scalability improvements fate.technology/posts/fate-1…
31
56
582
129,568
TBF requiring a GraphQL backend is a pretty big lift. And plenty of people would prefer the lack of compilation step, as well.
1
23
yes - but thats a backend problem... graphql and its patterns make a lot of sense on the client, but i'd argue you get even more benefits when you have a graphql backend. especially when client and backend talk the same language..
1
16
Replying to @Pascal_Senn
No. fate solves data management for the web. GraphQL is a transport protocol. Same as tRPC or any other JSON API. fate has a very simple protocol, it’s “just JavaScript”, http and batching.
1
1
165
sure - i meant more that the concept of fragments and composition is part of the graphql query language and this is leveraged by relay, apollo client, urql etc.
64
Replying to @Pascal_Senn
People who get to experience it love Relay, but not everyone likes GraphQL. With fate, you get the best client framework without having to buy in to a backend query language.
1
151
i see - already sending this through to folks that never got to experience relay so they can finally know what i am talking about 😅 so you'd say - fate partially solves a problem on a client that graphql solves higher up in the stack?
1
86
Finally someone did data fetching right
fate 1.0: The first full Async React Metaframework New in 1.0: * Zero-Config Live Views via SSE * Drizzle Support * "Native" HTTP support (no tRPC) * Void Router * Vite plugin * Clientside Garbage Collection * Performance & scalability improvements fate.technology/posts/fate-1…
6
2
222
53,989
hmm can you elaborate? isnt this pretty similar to a subscription and @appendNode and @deleteRecord ?
34
So essentially: just because the backend does not provide a GraphQL interface? also, I've read through the docs and I like fate, dont get me wrong.
1
125
Wrapping up another great API Days. Looking forward to seeing everyone next week at GraphQL Conf in California - registration is still open and free to attend. graphql.org/conf/2026/
54
Clauding (verb) — Relentlessly hammering prompts into Claude with zero strategy and full confidence. You don’t understand the output. Claude doesn’t understand the input. But eventually, somehow, it works.​​​​​​​​​​​​​​​​ #Claude
3
198
Keynote Speaker: “AI is revolutionizing healthcare research and will help us defeat cancer. At scale. Very soon.” Meanwhile, Engineers (prompt to ChatGPT): “Give me 5 better names for the variable _aggregatedContextualConfigurationOverrideValue.”
3
56