Open CLI

btm

observability
$ brew install bottom
Summary

System monitoring, cpu, and process inspection from the terminal.

  • btm fits infra well, especially for system monitoring, cpu, and process inspection from the terminal.
  • 1,524 homebrew installs (30d).
  • Verify with `btm --version` first.
  • Best treated as a human-first terminal tool.
  • Output is mostly text-first, so verify results before scripting around it.
infra-btm-SKILL.md

Btm guide

System monitoring, cpu, and process inspection from the terminal. Built by Clement Tsang.

Open CLI packages the install path, verify step, and safe-start workflow so this tool can move from “interesting CLI” to something you can actually use. It also integrates with skills.sh so each CLI comes with the right companion skills, not just a binary and a docs link.

When to apply

  • system monitoring, cpu, and process inspection from the terminal.
  • You work with observability and want a fast terminal interface.
  • You need system monitoring.
  • You need cpu.
  • You need process inspection.

Quick reference

Installbrew install bottom
Verifybtm --version
First real commandbtm

Open CLI × skills.sh

Open CLI integrates btm with the right skills.sh companions so you get the tool and the workflow together.

Monitoring & Observability

Recommended pairing

Open CLI recommends this skills.sh skill because it fits observability workflows. Use metrics, traces, and health checks to understand what your CLI changed.

View on skills.sh
$ npx skills add https://github.com/supercent-io/skills-template --skill monitoring-observability
Starter prompt

Use btm together with the Monitoring & Observability skills.sh skill. Start with safe inspection commands, summarize what you find, and ask before any step with side effects.

Also useful from skills.sh
Log Analysisskills.shDebuggingskills.sh

Why this tool

  • btm fits infra well, especially for system monitoring, cpu, and process inspection from the terminal.
  • 1,524 homebrew installs (30d).
  • Verify with `btm --version` first.

Watch-outs

  • Automation can be brittle.
  • Output is mostly plain text.
  • Better for local use than CI.

Example workflow

1. btm

Safe start

Step 1

Install btm.

Step 2

Run `btm --version` first.

Step 3

Start with `btm`.

Step 4

Install the infra CLI and verify kubeconfig, Docker context, or cloud credentials.

Alternatives worth considering

datadog-ci

CI tests, source maps, and deploy markers from the terminal.

k6

Load testing, performance, and http tests from the terminal.

duf

Disk free, filesystem status, and readable df from the terminal.