Hacker News Reader

I have no clue how you’re running your agents or what you’re building, but giving the raw password string to a the model seems dubious?

Otherwise, why not just keep the password in an .env file, and state “grab the password from the .env file” in your Postgres skill?

View on HN

I am thinking of distributing skills that I build to my clients. As my clients are mostly non-technical users I need this process of distribution to be as easy as possible. Even adding a .env file would probably be too much for most of them. With skills I can now finally distribute my logic easily, just send the raw files and tell them to put it into a folder - done. But there is no easy way for them to "setup" the credentials in those skills yet. The best UX in my opinion would be for Codex (or Claude, doesn't matter) to ask for those setup-parameters once when first using the skill and process the inputs in a secure manner, i.e. some internal secret storage

That’s exactly what I do.

Reply on news.ycombinator.com