Hacker News Reader

Comment by saberience | Hacker News Reader

Sounds like both of these tools could be one shot by either Claude or Codex.

Or alternatively, just be a skill versus a tool.

My “agents” already demo stuff all the time by just being prompted to do so. I have notations in my standard Agents.md for how I want my documentation, testing etc.

View on HN

They kind of were one-shotted by Claude. The value is in coming up with a consistent design and good enough --help that you can prompt:

  Run uvx showboat --help and
  uvx rodney --help and use those
  tools to demo the feature you built

The help text effectively doubles as a skill.

I guess it would still make sense to have "demo" and "browser-use" skills, so that the agent can reach for them proactively? I always try to remove as much friction as possible for myself, one little bit at a time.

My problem is that I work in dozens of different repos generally using Claude Code for web, which doesn't have a way to install extra global skills yet.

I don't want to duplicate my skills into all those repos (and keep them updated) so I prefer the "uvx tool --help" pattern.

That's actually one of the things that has kept me from using Claude Code web (that, and I often need a Chrome browser for the agent). But they must be working on it.

I saw an MCP I've set up on claude.ai show up in my local Claude Code MCP list the other day, it seems inevitable that there will be skills integration across environments as well at some point.

In working on Rodney I found out that the Claude Code for web environment has a Chrome browser installed already. It's a shame you can't see its output directly - even if it takes a screenshot there's no easy way to view it other than having it commit and push that to a branch in GitHub.

Oooh, I didn't know that.

Reply on news.ycombinator.com