268 karma · joined January 22, 2019
https://code.claude.com/docs/en/gateways
Seems like a good way to govern usage to an alternate model provider
My point is that this sounds more like a general AGENTS.md use case, similar to defining tone of voice, output format, etc.
It just seems skills is the only way to distribute certain "behavior" as of today. But not everything is a skill IMHO, and not this is not one of them.
On the other hand, maybe we're seeing an evolution of what skills are becoming.
You buy something one day, and it starts to deteriorate and become janky after a year, and you'll have a buy a new one. All products have gone through spreadsheet cost optimizations.
It wasn't always like that. If you're lucky to get your hands on an old IKEA bookshelf (Billy), it's sturdy and will last forever.
"We don't know why we're doing it - it's just mandatory".
I've been trying to explain to compliance employees that if the majority of PR reviews anyway is just "LGTM - Just merge" (I don't care), what's the actual value of PRs? It's just facade.
On a different note, we're looking into artifact attestations and admissions through Sigstore, which is solves many of the same challenges but through different means.
Now you trust a single GH user rather than a company. Fair enough. I just think it's very paradoxical.
The article refers to their GH repo and that was all cherry and sunshine up until just recently, where it is redirected to https://github.com/LobsterTrap/lola.
No mention of it anywhere. "Did it get compromised?" was my initial thought. Still in the fog here.
From my experience, unfortunately, people who manage policies are much less competent that those who implement them.
Ref: https://www.reddit.com/r/technology/comments/1r1tphx/microso...
In technology, there are known problems and unknown problems. Expiring TLS certificates is a known problem which has an established solution.
Imagine if only some of the requests failed because a certificate is about to expire. That would be a debugging nightmare.