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
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 ;).
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 🚀
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
Today we're shipping Skillz: a .NET CLI for discovering, installing, updating, and authoring Agent Skills.
Run it one-shot with dnx, just like npx:
💻 dnx skillz add dotnet/skills
🤓 chillicream.com/blog/2026/06…#dotnet#agenticai
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…
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
@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…
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…
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..
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.
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.
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.
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?
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…
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/
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
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.”