Skip to content
Skills Library
Programming · Tool integration

setup

/setup

Turn on the statusline-kit status line. Use when the user asks to set up, enable, switch on or fix the status line from the statusline-kit plugin, or to show or hide its git information.

Licence
MIT
Last repository change
13.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 13.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Turn on the statusline-kit status line. Use when the user asks to set up, enable, switch on or fix the status line from the statusline-kit plugin, or to show or hide its git information.

Original author description

Turn on the statusline-kit status line. Use when the user asks to set up, enable, switch on or fix the status line from the statusline-kit plugin, or to show or hide its git information.

How it works

  1. Steps
  2. Do not
Original SKILL.md headings · 40 lines, 277 words
SKILL.md preview
---
name: setup
description: Turn on the statusline-kit status line. Use when the user asks to set up, enable, switch on or fix the status line from the statusline-kit plugin, or to show or hide its git information.
---

# Turn on the status line

The plugin's hooks already record every run. The status line itself is the one thing a plugin
cannot switch on: Claude Code reads `statusLine` only from the user's own settings. This skill
adds that entry.

## Steps

1. Check `jq` is installed (`command -v jq`). The status line and the hooks need it. If it is
   missing, tell the user how to install it (`brew install jq`, `apt install jq`) and stop.
2. Check the script exists: `${CLAUDE_PLUGIN_DATA}/statusline.sh`. The plugin copies it there at
   the start of every session, so it survives plugin updates. If it is missing, copy it now:
   `mkdir -p "${CLAUDE_PLUGIN_DATA}" && cp "${CLAUDE_PLUGIN_ROOT}/statusline.sh" "${CLAUDE_PLUGIN_DATA}/statusline.sh"`.
3. Read `~/.claude/settings.json`. If it already has a `statusLine` entry that is not this one,
   show it to the user and ask before replacing it.
4. Ask whether to show git information: nothing, everything (`--git`), or a comma list of
   `repo`, `branch`, `worktree` (`--git repo,branch`).
5. Set the entry, keeping everything else in the file as it is:

   ```json
   "statusLine": {
     "type": "command",
     "command": "bash \"${CLAUDE_PLUGIN_DATA}/statusline.sh\"",
     "refreshInterval": 2
   }
   ```

   Append the git option inside the command when the user chose one, for example
   `bash \"${CLAUDE_PLUGIN_DATA}/statusline.sh\" --git branch`.
6. Tell the user the status line appears after the next message, and that `/statusline-kit:setup`
   can be run again to change the git option.

## Do not

- Do not also run the kit's `install.sh`: it installs the same hooks into `~/.claude`, and every
  run would then be recorded twice. If `~/.claude/hooks/subagent-stop.sh` exists, tell the user
  that both are installed and that one of them has to go.
- Do not write anywhere except `~/.claude/settings.json`.

Versions

RepositoryScoreLicence
This page · endorphin-ai/hasbrains-agent-kit100MIT
HwangSlater/harness-fit100MIT
nesquikm/dev-process-toolkit100MIT
userKael/rastro100MIT
als-apg/osprey100BSD-3-Clause
dedujeong/gemba100Apache-2.0
eigenwise/eigenwise-toolshed100MIT
awrshift/agent-memory-kit100MIT
lifecycle-innovations-limited/claude-ops100MIT

Database snapshot: 13.11.2026 · package version 13189f8b07b6 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100setup-statusline
    Powerlineスタイルのステータスラインをセットアップする。「ステータスライン設定」「statusline setup」「ステータスバー」などのリクエスト時に使用。
  • 100statusline
    Configure a custom status line in the CLI. Use when the user mentions status line, statusline, statusLine, CLI status bar, prompt footer customization, or wants to add session context above the prompt.
  • 100claude-statusline
    Guide for creating and configuring the Claude Code status line. Use when building a custom status bar, configuring statusLine in settings.json, scripting token/model/git readouts, or debugging status-line output.
  • 100statusline
    Use when installing or uninstalling Groundwork's optional statusline configuration
  • 100init-claude-code-statusline
    初始化、更新或覆盖 Claude Code 状态栏配置文件(.claude/settings.json 和 .claude/statusline.sh)。用于在任何项目中快速搭建 Claude Code 状态栏显示功能, 展示目录、Git 分支、模型、版本和上下文窗口使用情况。
  • 100claude-code-statusline-development
    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.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.