This skill should be used when the user asks to "create a statusline", "customize the status line", "add a custom prompt", or mentions Claude Code statusline. Also suggest when the user wants to display git branch, context usage, model name, or session costs at the bottom of Claude Code.
Create custom status lines that display contextual information at the bottom of Claude Code.
You MUST read the reference files for detailed schemas and examples:
Add to .claude/settings.json:
{
"statusLine": {
"type": "command",
"command": "~/.claude/statusline.sh",
"padding": 0
}
}| Field | Description |
|---|---|
model.display_name | Model name (e.g., "Opus") |
workspace.current_dir | Current working directory |
workspace.project_dir | Original project directory |
cost.total_cost_usd | Session cost in USD |
cost.total_lines_added | Lines added this session |
cost.total_lines_removed | Lines removed this session |
context_window.context_window_size | Max context tokens |
context_window.current_usage | Current token usage object |
See JSON Schema for complete structure.
#!/bin/bash
input=$(cat)
# Extract values using jq
model=$(echo "$input" | jq -r '.model.display_name')
dir=$(echo "$input" | jq -r '.workspace.current_dir')
# Colors via tput
blue=$(tput setaf 4)
reset=$(tput sgr0)
echo "${blue}[$model]${reset} ${dir##*/}"Make executable:
chmod +x ~/.claude/statusline.shtput for portable ANSI colorsecho '{"model":{"display_name":"Test"}}' | ./statusline.shAfter creating or modifying statuslines, inform the user:
No restart needed. Statusline changes take effect immediately - Claude Code reads settings fresh on each update.
Based on Claude Code Status Line Configuration.
92f335c
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.