Status line setup doesn't check for required dependencies (e.g. jq)

Description

When using /statusline to configure a status line, Claude Code generates a shell script that depends on jq for JSON parsing. If jq is not installed on the system, the status line silently fails with no error output — it just doesn't render.

Steps to Reproduce

1. Use /statusline to set up a status line (e.g. "show model name and context percentage with a progress bar")
2. Claude Code generates a bash script that uses jq to parse the JSON piped via stdin
3. If jq is not installed, the status line silently produces no output
4. No warning or error is surfaced to the user

Additional Context

When asking Claude Code to debug the broken status line, it also failed to identify the missing dependency as the root cause — it attempted various fixes to the script logic without checking whether jq was actually available on the system.

Suggestion

• The /statusline setup could check if required tools (jq, etc.) are installed before generating a script that depends on them
• Alternatively, generate scripts that use built-in tools (e.g. pure bash/python parsing) or fall back gracefully
• Surface stderr from the status line command so failures aren't completely silent

Environment

• Platform: WSL2 (Debian) on Linux
• Shell: bash