MCPInstall

groove-admin-claude-statusline

Install a rich Claude Code statusline into /.claude/hooks/ and /.claude/settings.json. Displays model, git context, token usage, effort level, 5h/7d usage limits, and active /loop count with next-fire time.

Installs
501
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/andreadellacorte/groove --skill groove-admin-claude-statusline
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads groove-admin-claude-statusline automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

groove-admin-claude-statusline

Install a rich single-line Claude Code statusline. Writes three scripts to ~/.claude/hooks/ and merges config into ~/.claude/settings.json.

Use --uninstall to remove. Use --list to show current status.

Outcome

~/.claude/settings.json has statusLine pointing to the statusline script, plus PostToolUse and SessionEnd hooks to track active /loop cron jobs. The statusline shows on every Claude Code turn.

What the statusline shows

claude-sonnet-4-6 | myrepo@main (+3 -1) | 42k/200k (21%) | effort: high | 5h 12% @8:00pm | 7d 3% @mar 16, 9:00am | 2 loops | check deployment @4:10pm
SectionDescription
ModelDisplay name of the active model
Repo@branchCWD folder name, git branch, staged diff +N -N
TokensUsed / total context, % used
EffortCurrent effort level (low / med / high)
5h / 7dRate-limit utilisation with reset time (cached 60s)
LoopsCount of active /loop crons + soonest-firing prompt and time

Steps

--list

Read ~/.claude/settings.json. Report whether statusLine is set, and whether each hook script exists in ~/.claude/hooks/. Exit.

--uninstall

Remove statusLine from ~/.claude/settings.json. Remove the three CronCreate|CronDelete / SessionEnd hook entries added by this skill. Do not remove hook scripts (leave for manual cleanup). Report changes. Exit.

Default (install)

  1. Create ~/.claude/hooks/ if absent.

  2. Write the three scripts below to ~/.claude/hooks/. Never overwrite without showing a diff and confirming.

  3. Make all three scripts executable (chmod +x).

  4. Read ~/.claude/settings.json (default {}). Merge in the statusLine entry and the two hook entries below. Preserve all other keys. Do not create duplicate entries.

  5. Write ~/.claude/settings.json.

  6. Report:

    ✓ statusline.sh         → ~/.claude/hooks/statusline.sh
    ✓ cron-state.sh         → ~/.claude/hooks/cron-state.sh
    ✓ cron-state-clear.sh   → ~/.claude/hooks/cron-state-clear.sh
    ✓ ~/.claude/settings.json updated
    Note: restart Claude Code for changes to take effect.
    

Scripts

The three shell scripts live in scripts/ per the Agent Skills specification:

ScriptInstalled toPurpose
scripts/statusline.sh~/.claude/hooks/statusline.shMain statusline renderer
scripts/cron-state.sh~/.claude/hooks/cron-state.shTracks /loop cron jobs in /tmp/claude/loops.json
scripts/cron-state-clear.sh~/.claude/hooks/cron-state-clear.shClears loop state on session end

Copy each script from scripts/ to ~/.claude/hooks/. Never overwrite an existing script without showing a diff and confirming.

~/.claude/settings.json entries

Merge these into the existing settings. Preserve all other keys. Do not create duplicates.

{
  "statusLine": {
    "type": "command",
    "command": "~/.claude/hooks/statusline.sh"
  },
  "hooks": {
    "PostToolUse": [
      {
        "matcher": "CronCreate|CronDelete",
        "hooks": [
          {
            "type": "command",
            "command": "~/.claude/hooks/cron-state.sh",
            "async": true
          }
        ]
      }
    ],
    "SessionEnd": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "~/.claude/hooks/cron-state-clear.sh",
            "async": true
          }
        ]
      }
    ]
  }
}

Constraints

  • Write to ~/.claude/hooks/ (user-global), not .claude/ (project-local)
  • Never overwrite an existing script without showing a diff and confirming
  • Never discard existing keys in ~/.claude/settings.json
  • Requires: jq, curl, python3, git (all standard on macOS/Linux)
  • The 5h/7d usage section requires a Claude Pro/Max OAuth session; it silently omits if no token is found
  • After install: restart Claude Code for the statusLine and hooks to take effect

FAQ

What does the groove-admin-claude-statusline skill do?

Install a rich Claude Code statusline into /.claude/hooks/ and /.claude/settings.json. Displays model, git context, token usage, effort level, 5h/7d usage limits, and active /loop count with next-fire time.

How do I install groove-admin-claude-statusline?

Run npx skills add https://github.com/andreadellacorte/groove --skill groove-admin-claude-statusline in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/groove-admin-claude-statusline/ (personal) or .claude/skills/groove-admin-claude-statusline/ (project).

Which AI agents can use groove-admin-claude-statusline?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is groove-admin-claude-statusline safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains groove-admin-claude-statusline?

It is published by andreadellacorte in andreadellacorte/groove. It has 501 recorded installs.

More from andreadellacorte/groove

View all →

groove

andreadellacorte/groove

Groove engineering workflow system. Top-level entry point. Use groove-daily-, groove-work-, groove-utilities-, groove-admin- for all workflow and admin commands.

groove-utilities-task-analyse

andreadellacorte/groove

Analyse task status and distribution across the configured backend.

groove-utilities-memory-install

andreadellacorte/groove

Set up memory backend and configuration.

Backend & APIs585 installs

groove-admin-install

andreadellacorte/groove

Install groove backends, companions, and AGENTS.md bootstrap. Run once per repo.

585 installs

groove-utilities-memory-log-daily

andreadellacorte/groove

Write the daily memory log entry. Use at end of day to record what happened.

581 installs

groove-utilities-task-install

andreadellacorte/groove

Set up task backend and configuration.

Popular code quality & workflow skills

View category →

grill-me

mattpocock/skills

A relentless interview to sharpen a plan or design.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

handoff

mattpocock/skills

Compact the current conversation into a handoff document for another agent to pick up.

domain-modeling

mattpocock/skills

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

codebase-design

mattpocock/skills

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

diagnosing-bugs

mattpocock/skills

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.