glow
$ brew install glowMarkdown previews, terminal docs, and readmes from the terminal.
- glow fits git & github well, especially for markdown previews, terminal docs, and readmes from the terminal.
- 4,719 homebrew installs (30d).
- Easy to automate.
- Best treated as a human-first terminal tool.
- Output is mostly text-first, so verify results before scripting around it.
Glow guide
Markdown previews, terminal docs, and readmes from the terminal. Built by Charmbracelet.
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
- markdown previews, terminal docs, and readmes from the terminal.
- You work with docs and content and want a fast terminal interface.
- You need markdown previews.
- You need terminal docs.
- You need readmes.
Quick reference
brew install glowglow --versionglow README.mdOpen CLI × skills.sh
Open CLI integrates glow with the right skills.sh companions so you get the tool and the workflow together.
Technical Writing
Verified pairingOpen CLI integrates glow with this skills.sh skill because it is the clearest fit for how glow is usually used. Document commands, outputs, and workflows in a way other people can reuse.
$ npx skills add https://github.com/supercent-io/skills-template --skill technical-writingUse glow together with the Technical Writing skills.sh skill. Start with safe inspection commands, summarize what you find, and ask before any step with side effects.
Why this tool
- glow fits git & github well, especially for markdown previews, terminal docs, and readmes from the terminal.
- 4,719 homebrew installs (30d).
- Easy to automate.
Watch-outs
- Output is mostly plain text.
- Better for local use than CI.
Example workflow
1. glow README.mdSafe start
Install glow.
Run `glow --version` first.
Start with `glow README.md`.
Install the CLI and make sure it is on your PATH.