plugins-claude/statusline/skills/config/SKILL.md
View or edit status line configuration
npx skillsauth add st0nefish/claude-toolkit configInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
View or modify the claude-statusline configuration file.
Config location: ${XDG_CONFIG_HOME:-$HOME/.config}/claude-statusline/config.json
| Setting | Type | Default | Description |
|---------|------|---------|-------------|
| segments | array | ["user","dir","git","model","context","session","weekly","extra","cost"] | Ordered list of segments to display. Remove items to disable them. |
| separator | string | " \| " | String displayed between segments |
| cache_ttl | number | 300 | API usage cache TTL in seconds |
| git_cache_ttl | number | 5 | Git status cache TTL in seconds |
| path_max_length | number | 40 | Max characters for directory display |
| show_host | string | "auto" | Show hostname: "auto" (SSH only), "always", "never" |
| git_backend | string | "auto" | Git backend: "auto", "daemon" (gitstatusd only), "cli" (git only) |
| label_style | string | "short" | Label format: "short" (Ctx, Ses, Wk) or "long" (Context, Session, Week) |
| cost_thresholds | array | [5, 20] | Dollar values for green/yellow/red cost coloring |
| extra_hide_zero | boolean | true | Hide extra credits segment when $0 used |
| extra_only_burning | boolean | false | Only show extra segment when session or weekly is at 100% |
| currency | string | "$" | Currency symbol prefix |
| colors | object | (see below) | 256-color codes or keywords (dim, bold, default) for each element |
low, mid, high, separator, git_branch_feature, git_branch_primary, git_staged, git_unstaged, git_untracked, git_ahead, git_behind, label, model, user, user_root, host, dir, reset_time, cost
Read the config file at ${XDG_CONFIG_HOME:-$HOME/.config}/claude-statusline/config.json. If it does not exist, tell the user to run /statusline:setup first.
Show the user the current configuration.
Ask what they want to change using AskUserQuestion.
Edit the config file with the requested changes using Edit.
Let the user know the changes take effect automatically on the next status line refresh (no restart needed).
development
Start work from your description — explore the codebase and plan
data-ai
Multi-phase, multi-agent feature workflow: spec → plan → refine → divide → execute → review. Invoke when the user escalates a session-start/session-issue flow to orchestration, or asks to run a non-trivial feature (multiple files, design ambiguity, cross-cutting concerns, correctness-critical paths) through the full multi-agent workflow. For small fixes, prefer session-start.
tools
Browse open issues, pick one, and start work on it
tools
Review, clean up, and open a PR to finalize the work