toolbelt
Reference for haru's preferred modern CLI tools — when and how to use eza/bat/fd/ripgrep/sd, xh, dasel, procs, doggo, hexyl, duckdb/psql/sqlx-cli, hyperfine/oha. Invoke when a task involves searching files, editing text, HTTP/API calls, data/SQL work, DNS or process debugging, hex inspection, or benchmarking, and you want the idiomatic tool + flags instead of the classic Unix default.
What this skill does
# Toolbelt Skill haru's machines (managed by `harus-nix` Home Manager) ship a curated set of modern CLIs. **Prefer these over the classic Unix tools by default** — fall back to the classic only when the modern tool is genuinely unavailable. This skill is **self-contained** — it carries both the substitution rules and the usage recipes so it works on any device, even one whose global `~/.claude/CLAUDE.md` isn't synced or differs. Treat it as the portable source of truth; if the local global config disagrees, the local config wins for that machine, but these defaults travel with you. Rule of thumb: classic tools for piping inside scripts that must be portable; modern tools for interactive/agent work where clarity and ergonomics win. ## Substitution table (always-on) Reach for the right-hand tool by default; fall back to the classic only when the modern one is absent. | Instead of | Use | For | | -------------------- | --------------------------------------- | ------------------------------- | | `ls` / `cat` / `du` | `eza` / `bat` / `dust` | listing, viewing, disk usage | | `grep` / `find` | `ripgrep` (`rg`) / `fd` | search | | `sed` (substitute) | `sd` | find & replace | | `ps` / `dig` / `xxd` | `procs` / `doggo` / `hexyl` | processes, DNS, hex | | `curl` (API testing) | `xh` | HTTP requests | | `jq` for non-JSON | `dasel` | YAML/TOML/XML/CSV query+convert | | ad-hoc SQL | `duckdb`, `psql` (postgres), `sqlx-cli` | data + migrations | | benchmarking | `hyperfine` (CLI), `oha` (HTTP) | perf checks | | `python` / `pip` / `pipx` | `uv` / `uvx` | Python runtime, deps, tools | | `node` / `npm` / `npx` | `bun` / `bunx` | JS/TS runtime, deps, tools | ## Tooling discipline (carried from global defaults) These hold across all of haru's projects and are restated here so the skill stands alone: - **Nix-first** — tools come from the project devShell (`nix develop`); use `mise` only for language runtimes, not general tooling. - **`make` is the task runner** — reference `make <target>` everywhere; `make check` before commits, `make validate` before PRs (hook-enforced). - **JSON → `jq`** — always `jq` for JSON processing; never `python3 -c` or inline Python. Reach for `dasel` the moment the format isn't JSON. - **`rtk` proxy** — if present, `rtk` transparently rewrites git and other commands for token savings; don't fight it. - **Conventional commits, 2-space config indent, no emojis** — per global CodingStyle. ## Runtimes & package managers Prefer the fast modern runner over the legacy one by default — they're drop-in for the common paths and far faster. - **`uv`** — Python runtime + dependency + project manager (replaces `python`/`pip`/`venv`/`pipx`/`poetry`): - `uv run script.py` (auto-resolves deps), `uv run pytest` (run a tool in the project env) - `uv add httpx` / `uv remove httpx` (manage `pyproject.toml`), `uv sync` (install lockfile) - `uv venv` (create env), `uv pip install -r req.txt` (pip-compatible shim) - **`uvx`** — run a Python CLI tool one-off without installing: `uvx ruff check`, `uvx [email protected] format`. - **`bun`** — JS/TS runtime + package manager + bundler (replaces `node`/`npm`/`npx`/`yarn`/`pnpm`): - `bun run script.ts` (runs TS directly, no compile step), `bun test` - `bun install` (fast install), `bun add zod` / `bun remove zod` - **`bunx`** — run a package one-off without installing: `bunx prettier --write .`, `bunx tsx file.ts`. Caveats: stick to `python3`/`node` + `pip`/`npm` when a project's toolchain or CI pins them, when a native addon/wheel isn't yet `bun`/`uv`-compatible, or inside a Nix devShell that already provides the interpreter (per Nix-first, `mise` handles runtimes there). For everything ad-hoc and interactive, reach for `uv`/`bun` first. ## Search & navigate | Task | Tool | Idiom | | ---------- | ---------------- | ------------------------------------------------------------- | | Find text | `ripgrep` (`rg`) | `rg -n "pattern"`, `rg -t rust foo`, `rg -l pat` (files only) | | Find files | `fd` | `fd -e nix`, `fd -t f name`, `fd -H` (include hidden) | | List dir | `eza` | `eza -la --git`, `eza --tree --level=2` | | View file | `bat` | `bat file`, `bat -p` (plain, no decorations for piping) | | Disk usage | `dust` | `dust -d 2` (depth 2) | | Jump dirs | `zoxide` | `z proj` after visiting once | Prefer `rg`/`fd` over `grep -r`/`find` — faster, respects `.gitignore`, sane defaults. When piping `bat` output, add `-p` to strip line numbers/borders. ## Edit text - **`sd`** — find & replace, literal-friendly, real regex (no `sed` escaping pain): - `sd 'foo' 'bar' file.txt` (in-place, no `-i` needed) - `sd -p 'foo' 'bar' file.txt` (preview diff, don't write) - `sd '(\w+)@(\w+)' '$2.$1' file` (capture groups with `$1`) - Reach for `sed` only for stream edits in portable scripts. ## HTTP / API debugging - **`xh`** — httpie-style client, faster than `curl` for hand-driven requests: - `xh get https://api.example.com/users` (auto-pretty JSON) - `xh post api.local/login name=haru pass=secret` (JSON body from `k=v`) - `xh -f post url field=val` (form), `xh --headers get url` (headers only) - `xh get url Authorization:"Bearer $TOK"` (header with `:`) - Use `curl` in scripts / when exact wire control or `--resolve` is needed. - **`oha`** — load testing: `oha -n 1000 -c 50 https://api.local/health`. ## Data & SQL - **`dasel`** — one tool to query/convert JSON/YAML/TOML/XML/CSV: - `dasel -f config.yaml '.services.web.port'` - `dasel -f data.json -r json -w yaml` (convert JSON→YAML) - Use `jq` for pure-JSON pipelines (it's still the default for JSON); reach for `dasel` the moment the format isn't JSON. - **`duckdb`** — fast analytical SQL over files, no server: - `duckdb -c "select * from 'data.csv' limit 5"` - `duckdb -c "select count(*) from read_parquet('*.parquet')"` - **`miller`** (`mlr`) — CSV/TSV/JSON record processing: - `mlr --csv cut -f a,b then sort -nr b data.csv` - **`psql`** (from `postgresql`) — Postgres client: - `psql "$DATABASE_URL" -c '\dt'`, `psql -h host -U user db` - **`sqlx-cli`** — Rust SQL toolkit / migrations: - `sqlx database create`, `sqlx migrate add <name>`, `sqlx migrate run` - `sqlx migrate revert`, `cargo sqlx prepare` (offline query cache) ## Debug & inspect - **`procs`** — modern `ps`: - `procs` (all), `procs nginx` (filter by name), `procs --tree` - `procs --sortd cpu` (sort by CPU desc), shows ports/TTY/user. - **`doggo`** — modern `dig` for DNS debugging: - `doggo example.com`, `doggo MX example.com` - `doggo example.com @1.1.1.1` (specific resolver), `--json` for parsing. - **`hexyl`** — colored hex viewer: - `hexyl file.bin`, `hexyl -n 64 file` (first 64 bytes), inspect encodings/headers. - **`tailspin`** (`tspin`) — auto-highlight logs: `tspin app.log` or `cmd | tspin`. - **`btop`** — interactive system monitor. ## Benchmark - **`hyperfine`** — CLI command benchmarking with stats: - `hyperfine 'rg foo' 'grep -r foo .'` (compare), `--warmup 3`. - **`oha`** — HTTP load (see above). ## When NOT to substitute - Portable shell scripts that may run on minimal/other machines → stick to POSIX (`grep`, `sed`, `find`, `curl`) so they don't depend on this toolbelt. - Pure-JSON pipelines → `jq` remains the default (per global CLAUDE.md). - If a tool isn't installed (`command -v <too
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.