Hi, I'm Paul- James and I built Ingot because skill changes felt like copy-paste, and are difficult to track across large orgs. Ingot versions them and requires human review. It can also optimize them using real agent traces. We'd love to know how others are solving the skill control & versioning problem
HN user
laul_pogan
5 karma
Posts2
Comments6
Show HN: Ingot, evidence-gated optimization and version control for agent skills 8 hours ago
My tool has a public-good relay and the ability to chat between environments, so it's important to resolve ID to operator or company
Oh wow! I had no idea. Even with a service worker? I'll switch over to this- it works just as well for insertion and .env replacements in claude code?
How is this different than OP CLI with a service account?
Hey Xia! Super excited for this- good talking to you a few weeks ago and best luck with the launch :)
I find that the real problem tends to be identity and trust across sessions- ideally there are ways to enable zero-knowledge trust between two agents in different environments.
I develop a similar tool open source tool called wire (wireup.net) https://github.com/SlanchaAi/wire