configure_skill

Overview

This skill helps you discover, inspect, and update statusline components either globally or per-project. It follows a strict conversational workflow: show current state, list available components, ask what to change, then apply the requested changes. The skill writes an incremental JSON config that controls which components are enabled and their order.

How this skill works

It starts by running a discovery script to list all components and groups them by namespace. If the user wants to configure, the skill determines scope (global or project), reads the current config, and displays enabled/disabled components alongside available ones with short descriptions. The user replies in natural language; the skill parses enable/disable or absolute requests, merges changes into add/remove arrays, writes the config file, and reports what changed and where it was saved.

When to use it

• You want to list all available statusline components.
• You want to enable or disable components globally or for the current project.
• You need to change the order of enabled components (by editing the add array).
• You prefer making incremental changes based on current state (enable X, disable Y).
• You want the skill to handle natural-language requests like “just X and Y” or “enable version”.

Best practices

• Always start by letting the skill discover components; do not assume a fixed set.
• Specify scope if you mean global or project to skip the scope question.
• Use clear enable/disable language (enable/add vs disable/remove); use “just” or “only” to set absolute state.
• When ambiguous names occur (e.g., “model”), clarify the intended component if prompted.
• Restart Claude Code after changes for them to take effect; reorder components by editing the add array in the saved JSON.

Example use cases

• User asks “what statusline components are available?” — skill lists components grouped by namespace and stops.
• User: “Help me configure the global statusline” — skill discovers components, shows current state, asks which to enable/disable, applies changes, saves global JSON.
• User: “Just directory and model” in a project — skill interprets as absolute state, enables only those and disables others in project config.
• User: “Enable version, disable model” — skill updates add/remove arrays, preserves order, and reports saved file location.