nori-slack-cli: A CLI for the Slack Web API designed for coding agents.

In the realm of sophisticated automation and AI coding agents, interoperability is everything. Nori-Slack-CLI addresses a significant pain point: the struggle of connecting autonomous systems to robust, complex services like Slack. Unlike purpose-built wrappers that might curate a 'best-of' subset of methods, Nori-Slack-CLI is engineered as a raw, high-fidelity conduit to the full Slack Web API. This makes it exceptionally valuable for advanced agent development where access to every single API endpoint—from `chat.postMessage` to niche `conversations` methods—is critical. The technical implementation shines in its deliberate minimalist design. It bypasses the conversational layer, transmitting everything as standard JSON on stdout and handling errors via JSON on stdout and a clear line on stderr. This deterministic output structure is gold standard for coding agents, which require predictable, parseable streams of data to function reliably. By treating the underlying API structure as its ground truth, Nori-Slack-CLI avoids the pitfalls of API versioning or internal abstraction changes within its own code base, offering longevity and stability to consuming agents. For developers building agents, the security model is particularly noteworthy. The CLI does not impose method-level limitations; instead, it defers capability enforcement entirely to the Slack bot token scopes (`SLACK_BOT_TOKEN`). This strict adherence to OAuth permissions means that if an agent has access to a specific endpoint, the CLI will attempt it, and the underlying Slack API will handle the necessary scope rejection, providing a transparent and controllable boundary. The use of `--dry-run` also allows agents to plan and validate complex interaction chains without incurring API costs or sending actual messages. In short, Nori-Slack-CLI is not just another tool; it's an architectural decision that prioritizes developer control and functional completeness. It shifts the complexity from the CLI wrapper to the established, stable contract of the Slack Web API itself, making it a superior choice for any agent ecosystem needing exhaustive, reliable, and easily debuggable access to Slack’s functionality. The inclusion of self-locating error fields further enhances agent debugging capabilities, allowing the consuming code to pinpoint the exact source of failure within the CLI itself.