# A Hive AI agent skill and a modern CLI (built for the AI age) I know ...I’m terrible at posting consistently, and it’s been a long time since my last post. Yesterday someone pointed out it’s been over 2 years (thanks @livinguktaiwan 🙏). About time to fix that 😊 Going forward the focus will be on **what I’m building** and working on. Hopefully the words will come easier. ## A command‑line wrapper for power users *and* agents The original idea was to create a [skill](https://skills.sh/) so AI agents could interact with the Hive blockchain. After a couple attempts it became obvious the existing tools weren’t ideal for automation, so I started from the bottom: a new wrapper around `hive-tx` (huge kudos to @mahdiyari) that could be a solid foundation for agent workflows. ![AI generated image by an AI agent](https://files.peakd.com/file/peakd-hive/asgarth/23sweHqWsaJ74xWgEu5UuxX1EqVicbSbFcmCjKRR6AGjxpzLvUW7jikDLg7nGNXhgADSs.png) A few hours later we had a working prototype for **[hive‑tx‑cli](https://github.com/asgarth/hive-tx-cli)**, a clean command‑line wrapper around Hive’s APIs. "We" here is me + OpenCode + Codex. Codex 5.2 got stuck near the finish line, so I swapped to Kimi 2.5 to close it out. ## The agent skill built on top Once the CLI was usable, we wrapped it into an AI agent skill. A skill is essentially a set of instructions (mostly Markdown) that teaches an agent how to interact with an external system, a tool or a specific domain. This part is mostly an AI task with light guidance from me. We used the popular [skill‑creator](https://skills.sh/anthropics/skills/skill-creator) (yep, there’s a skill to create a skill). Thanks to this, the agent can **inspect chain data, publish content, and automate workflows** without ever touching the network directly. Seeing it in action: ![image.png](https://files.peakd.com/file/peakd-hive/asgarth/EogFe6Pgv4N3Dvxhcx7V7QNTsKQjif46e4rMw5eCNHCtAJDUMrtRdFXNb3Addc9CkvL.png) Install: ```bash npx skills add https://github.com/asgarth/skills --skill hive ``` Or simply download the folder and copy the files in the correct location for the agent you use. Skill repo: https://github.com/asgarth/skills/tree/main/skills/hive --- --- 🤖 The rest of the post is AI‑generated. A recap of how to use the CLI and some tech details. 🤖 ### Why this new CLI exists Hive already has powerful APIs, but workflows are fragmented. I wanted a tool that: - **Queries** accounts, blocks, posts, and raw endpoints in seconds - **Broadcasts** votes, comments, posts, transfers, and custom JSON - **Uploads images** to Hive image hosters - Keeps secrets safe with **locked‑down local config** (600 permissions) or env variables - Works great in **automation and agent workflows** ## What’s under the hood (highlights) A few things we intentionally engineered: - **Interactive configuration** with safe defaults and explicit key scopes (posting vs active) - **Raw RPC access** for power users (you’re not boxed into a limited DSL) - **Environment variable overrides** for CI/automation workflows - **Modern Node.js 22 + TypeScript** for correctness and maintainability - **Extensible command structure** that won’t fight you when you add new ops Install: ```bash npm install -g @peakd/hive-tx-cli # or pnpm add -g @peakd/hive-tx-cli ``` Quick taste: ```bash hive config hive status hive account peakd hive vote --author --permlink --weight 100 ``` Repository: https://github.com/asgarth/hive-tx-cli ## Credits where it’s due This project is powered by **hive‑tx**, the excellent underlying library by **@mahdiyari**. Repository: https://github.com/mahdiyari/hive-tx ## What’s next - Expand CLI command coverage - Add more guided "agent‑friendly" recipes - Keep reducing friction between Hive power‑users and autonomous tooling If you’re building on Hive or experimenting with agent workflows, give it a spin. Feedback and PRs are welcome.</div> </div>