cli

l search engines over billions of satellite images, and developing full-stack embedded Rust IoT firmware with custom LoRa mesh networking for endurance races. I excel at taking systems from 0 to 1 and driving adoption developer experiences. I'm looking for Senior/Staff or Founding Engineer roles where I can tackle complex distributed systems or build secure, agent-first infrastructure.

d. (Inspired by the GWS cli: https://github.com/googleworkspace/cli). So you(r agent) can do things like: `nori-slack chat.postMessage --channel C123 --text "hi"` `nori-slack admin.users.list` `nori-slack bookmarks.add` etc. It's pretty easy to build a cli these days, so what makes this special? We spent a bunch of time thinking about what is necessary to make something 'agent first', which is I think the real value of this CLI: the design stuff. - Every response is a one line JSON on stdout, no colors or interactivity. - Every error includes a source field with the on-disk path to the CLI. When the agent is confused it can just go read the source (also useful for asking the agent to go add a feature on the fly) - (Re the above, we generally recommend downloading and running the cli from source on your machine!) - you can describe any method to get required/optional params, pagination support, and the docs URL without having your agent do additional webfetches - there's a list-methods function for discovery - the 'paginate' flag auto-cursors and merges pages into a single response - and my personal favorite: any unknown method will try and Levenshtein fuzzy match to surface other methods the agent may have meant We purposely wanted the CLI to match the bolt API 1:1 because we felt it critical that the agent had the capability of doing anything it needed. Scopes are managed via the tokens the cli has access to. Repo: https://github.com/tilework-tech/nori-slack-cli Would love to hear feedback about what works for other people when designing cli products for agents

it easy for automated systems to essentially pull users away from the actual platform. I guess they're focused on the short term incentives. And once they decide the party's over, promising upstarts and competition can get absorbed and it'll be business as usual. Idk, we'll see.

's [gws cli](https://github.com/googleworkspace/cli): ```bash npx skills add yogin16/better-cli ``` Then on Claude just one prompt: ```bash use better-cli skill and improve the cli as needed with best practices, no regression, ultrathink. ``` The gws cli is already nicely written for AI Agents, still it came up with [these changes](https://github.com/googleworkspace/cli/pull/297/changes) to improve error messages so that AI Agents using the cli knows what do with it. If you build CLIs (or suffer through them every day), I’d love your feedback. CLI is what the new software is becoming, at least for now. (API -> MCP -> CLIs) Hope this helps you better the CLIs for your software for agents.