agent-cli-creator

You can generate a site-specific CLI for browser automation by triggering the phase-driven workflow, which handles requirements gathering, site archaeology, and implementation to replace manual ad hoc scripting.

Yes, you can build a Go-based CLI using the Cobra framework that reuses your real Chrome session via the kimi-webbridge daemon to perform both read and write actions on the target site.

The universal JSON contract is a standardized output format enforced during CLI implementation to ensure reproducible and consistent data exchange when the CLI reads, writes, or manages content on a target site.

The generated CLI handles login authentication by reusing your active Chrome browser session through the kimi-webbridge daemon, ensuring read and write actions are executed with your existing credentials.

Yes, the kimi-webbridge daemon is a required prerequisite, acting as the bridge that allows the generated CLI to control and interact with the target site through your active browser session.

The best way is to follow the phase-driven workflow covering prerequisites, site archaeology, and scaffold implementation, which also provides companion-skill creation guidance to operate the generated CLI later.