RashadAnsari/myagents / plugins/albino/skills/statusline
statusline
VerifiedConfigure the Claude Code statusline to show current directory, git branch and dirty state, model, context usage, and time. Writes the statusline script and updates ~/.claude/settings.json.
Configure the Claude Code statusline by doing the following steps in order:
-
Ask the user where to install using AskUserQuestion with these options:
- Global: writes to
~/.claude/settings.json, applies to all projects - Project: writes to
.claude/settings.local.jsonin the current working directory, applies only to this project (gitignored, personal)
- Global: writes to
-
Find the albino plugin install directory. Check these locations in order and use the first that exists:
~/.myagents/plugins/albino- The value of the
CLAUDE_PLUGIN_ROOTenvironment variable
The statusline script is at
scripts/configure-statusline.shinside that directory. -
Based on the user's choice, determine the target settings file:
- Global:
~/.claude/settings.json - Project:
.claude/settings.local.json(relative to current working directory: create.claude/if it does not exist)
- Global:
-
Read the target settings file. If it does not exist, treat it as an empty JSON object
{}. -
Add or update the
statusLinefield with:{ "statusLine": { "type": "command", "command": "<absolute-path-to-configure-statusline.sh>", "refreshInterval": 30 } }Preserve all other existing fields. Write the result back to the target settings file.
-
Confirm to the user: statusline is configured (global or project, as chosen). It shows current directory, git branch and dirty state, model, color-coded context usage, and time. It refreshes every 30 seconds. Changes take effect on the next Claude Code interaction.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |