<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Agent Skills on vsz@ | Kubernetes, AI, tech stuff</title><link>https://victorszalvay.com/tags/agent-skills/</link><description>Recent content in Agent Skills on vsz@ | Kubernetes, AI, tech stuff</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Victor Szalvay — All rights reserved</copyright><lastBuildDate>Tue, 16 Jun 2026 09:00:00 -0700</lastBuildDate><atom:link href="https://victorszalvay.com/tags/agent-skills/index.xml" rel="self" type="application/rss+xml"/><item><title>GKE autoscaling, as an agent skill: two for design and diagnosis</title><link>https://victorszalvay.com/gke-autoscaling-agent-skills/</link><pubDate>Tue, 16 Jun 2026 09:00:00 -0700</pubDate><guid>https://victorszalvay.com/gke-autoscaling-agent-skills/</guid><description>&lt;p&gt;I&amp;rsquo;ve spent the last couple of posts trying to get autoscaling knowledge out of my
head and onto the page — &lt;a href="https://victorszalvay.com/gke-compute-classes-primer/" &gt;the ComputeClasses primer&lt;/a&gt;,
then &lt;a href="https://victorszalvay.com/computeclasses-curate-or-auto-create/" &gt;the curate-or-auto-create follow-up&lt;/a&gt;.
And every time I finish one, I run into the same wall: a blog post is something you
&lt;em&gt;read&lt;/em&gt;. It sits there. The person who actually needs it is three Slack threads deep
at 11pm with pods stuck &lt;code&gt;Pending&lt;/code&gt;, and they are not going to stop and read a primer.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://victorszalvay.com/gke-autoscaling-agent-skills/art-cover-gke-autoscaling-agent-skills.svg"/></item></channel></rss>