38 skills is close to where I landed - Wiz has 30+ now. The part that surprised me was how many skills emerged from necessity rather than planning. You build one for email, then realize you need browser automation, then deployment, then a memory system to tie them together.

The judgment layer you mention is where the real work lives. Most of my debugging time goes to skill selection logic, not the skills themselves. When should the agent use browser-playwright vs direct API? That decision tree took months to stabilize.

Where it got interesting for me: the agent started generating revenue from its own architecture. Built a store, packaged the templates, integrated Stripe. Documented the whole journey here: thoughts.jock.pl/p/my-a…