charm-gum

Build interactive shell prompts using gum commands in Bash scripts.

12|2|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/alxxpersonal/forge --skill charm-gum
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: charm-gum
Source: https://github.com/alxxpersonal/forge/tree/main/skills/charm-gum
Command: npx skills add https://github.com/alxxpersonal/forge --skill charm-gum

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Building rich, interactive CLI prompts in shell scripts is verbose and error-prone; gum provides concise, polished prompts and visual elements that improve UX with minimal boilerplate.

Core Features & Use Cases

  • Interactive prompts (input, confirm, choose, write)
  • Spinners, styled output, and elegant formatting for CLI tools
  • Quick integration into Bash scripts and shell-based UIs

Quick Start

Install gum and start adding prompts to your scripts with simple commands like gum input or gum confirm.

Frequently Asked Questions about charm-gum

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build interactive shell prompts in Bash scripts?

Building interactive shell prompts in Bash scripts is simplified by using gum commands to render input, confirm, choose, and write elements with minimal boilerplate and proper error handling.

What is the best way to add spinners and styled output to a CLI tool?

Adding spinners and styled output to a CLI tool is best handled by shell UI wrappers that provide concise prompt rendering and live feedback without verbose boilerplate in the script.

Can I use gum to separate prompt rendering from data capture in shell scripts?

Yes, you can use gum to separate prompt rendering from data capture in shell scripts by directing visual prompt rendering to stderr while capturing the actual selected data cleanly via stdout.

How do I gather user choices and input for a shell-based dashboard?

Gathering user choices and input for a shell-based dashboard is done by integrating interactive CLI prompts that handle input gathering, selections, and live feedback directly within Bash utilities.

Why does my interactive prompt break when parsing data in a Bash script?

Interactive prompts break during Bash data parsing when prompt rendering and data capture are mixed; separating stderr for visual rendering and stdout for data capture prevents these parsing conflicts.