Unwire yet-another-statusline from Claude Code — removes statusLine.command from settings.json in CLAUDECONFIGDIR (default ~/.claude/) and deletes the renderer's runtime state.

BSD-3-ClauseAuto-check: notesDevelopment

Install Uninstall

skills CLI
$ npx skills add tmck-code/yet-another-statusline --skill uninstall -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install tmck-code/yet-another-statusline uninstall --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/tmck-code/yet-another-statusline.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/uninstall .claude/skills/uninstall && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
uninstall
GitHub stars
242
Token cost
~1.2k tokens
SKILL.md length
222 words
Files
1
Skills in repo
7
Repo updated
First seen
Licence
BSD-3-Clause

At a glance

Unwire yet-another-statusline from Claude Code — removes statusLine.command from settings.json in CLAUDECONFIGDIR (default ~/.claude/) and deletes the renderer's runtime state.

  • Works in 5 steps: Resolve config dir → Inspect the current statusLine → Back up, then remove the statusLine block → …
  • Development work in your project
  • SKILL.md covers Step 0: Resolve config dir, Step 1: Inspect the current…, Step 2: Back up, then remove… and Step 3: Delete runtime state, plus 1 more section
  • Calls jq, claude and make

What it does

Uninstall is an agent skill from tmck-code/yet-another-statusline. Unwire yet-another-statusline from Claude Code — removes statusLine.command from settings.json in CLAUDECONFIGDIR (default ~/.claude/) and deletes the renderer's runtime state. Run before (or after) claude plugin uninstall yas, which only deletes the plugin cache and leaves the statusLine config behind.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development. The repository describes itself as: A statusline for Claude Code inspired by terminal monitor programs. The licence is BSD-3-Clause.

When your agent uses it

  • Development work in your project

Example prompts

  • “/uninstall”

Requirements

  • Pre-approved tools (allowed-tools): Read, Write, Bash

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Resolve config dir
  2. Inspect the current statusLine
  3. Back up, then remove the statusLine block
  4. Delete runtime state
  5. Report

What it can do on your machine

Read from SKILL.md and the folder at commit 26dc47d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Bash

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • jq
    • claude
    • make

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Uninstall loads about 1.2k tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 222 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~80
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Write, Bash

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from tmck-code/yet-another-statusline at commit 26dc47d, republished under its BSD-3-Clause licence (© tmck-code). 222 words, ~1,240 tokens.

Download SKILL.mdSave it as .claude/skills/uninstall/SKILL.md (or your agent's skills folder).
name
uninstall
description
Unwire yet-another-statusline from Claude Code — removes statusLine.command from settings.json in CLAUDE_CONFIG_DIR (default ~/.claude/) and deletes the renderer's runtime state. Run before (or after) `claude plugin uninstall yas`, which only deletes the plugin cache and leaves the statusLine config behind.
allowed-tools
Read, Write, Bash
effort
low
model
haiku
<objective>

Reverse /yas:init. Remove the statusLine block from settings.json in $CLAUDE_CONFIG_DIR (default ~/.claude/), only when it points at this plugin's renderer, and delete the runtime logs and per-session payloads the renderer wrote.

claude plugin uninstall yas@yet-another-statusline only deletes the plugin cache — Claude Code keeps reading statusLine.command from settings.json and tries to run the now-missing script. This skill clears that config so the statusline actually stops.

Leaves untouched: a custom (non-yas) statusLine, the settings.json.bak-yas-* backups, the user's yas.toml config file, and any make install dev symlinks.

</objective>
<workflow>

Step 0: Resolve config dir

bash
CONFIG_DIR="${CLAUDE_CONFIG_DIR:-$HOME/.claude}"
SETTINGS="$CONFIG_DIR/settings.json"
printf "  Config dir: %s\n" "$CONFIG_DIR"

Step 1: Inspect the current statusLine

bash
if [ ! -f "$SETTINGS" ]; then
    printf "  No settings.json — nothing to unwire.\n"
    CFG_STATE="absent"
else
    CMD=$(jq -r '.statusLine.command // ""' "$SETTINGS" 2>/dev/null)  # timeout: 5000
    if [ -z "$CMD" ]; then
        printf "  No statusLine configured — nothing to remove.\n"
        CFG_STATE="none"
    elif printf '%s' "$CMD" | grep -q "statusline_command.py"; then
        printf "  Found yas statusLine: %s\n" "$CMD"
        CFG_STATE="yas"
    else
        printf "! statusLine points elsewhere — not a yas command:\n    %s\n  Leaving it untouched.\n" "$CMD"
        CFG_STATE="foreign"
    fi
fi

statusline_command.py is the signature of this project's renderer (used by both the plugin-cache path and the dev checkout path from the README). If CFG_STATE is anything other than yas, skip Step 2 — do not edit statusLine.

Step 2: Back up, then remove the statusLine block

Only when CFG_STATE is yas:

bash
BAK_TS=$(date -u +%Y%m%dT%H%M%SZ)
cp "$SETTINGS" "$SETTINGS.bak-yas-${BAK_TS}"  # timeout: 5000
printf "  Backed up → settings.json.bak-yas-%s\n" "$BAK_TS"

_result=$(jq 'del(.statusLine)' "$SETTINGS")  # timeout: 5000
[ $? -eq 0 ] && [ -n "$_result" ] || { printf "! jq failed — settings.json unchanged\n"; exit 1; }

_tmp=$(mktemp "$SETTINGS.XXXXXXXXXX")
printf '%s\n' "$_result" > "$_tmp" \
    || { rm -f "$_tmp"; printf "! write failed — settings.json unchanged\n"; exit 1; }
mv "$_tmp" "$SETTINGS"  # timeout: 3000

if jq empty "$SETTINGS" 2>/dev/null; then  # timeout: 5000
    printf "  Removed statusLine from settings.json\n"
else
    cp "$SETTINGS.bak-yas-${BAK_TS}" "$SETTINGS"
    printf "! Result was invalid JSON — restored from backup\n"
    exit 1
fi

Step 3: Delete runtime state

The renderer writes these as it runs. Safe to remove; they regenerate if the statusline is ever reinstalled. yas.toml is deliberately preserved — it is the user's own configuration, not YAS-generated state.

bash
# Consolidated state tree (current versions)
if [ -d "$CONFIG_DIR/yas" ]; then
    rm -rf "$CONFIG_DIR/yas" && printf "  Removed yas/\n"
fi

# Legacy flat paths (older versions, pre-migration)
for f in statusline-tokens.log statusline-token-rate.log statusline-render.log \
         statusline-theme terminal-width yas-last-prompt.json yas.toml.cache; do
    if [ -e "$CONFIG_DIR/$f" ]; then
        rm -f "$CONFIG_DIR/$f" && printf "  Removed legacy %s\n" "$f"
    fi
done

if [ -d "$CONFIG_DIR/statusline-output" ]; then
    rm -rf "$CONFIG_DIR/statusline-output" && printf "  Removed legacy statusline-output/\n"
fi

# Legacy: older versions wrote per-session info files here
for f in "$CONFIG_DIR"/statusline-info-*; do
    [ -e "$f" ] || continue
    rm -f "$f" && printf "  Removed legacy %s\n" "$(basename "$f")"
done

(Use the resolved $CONFIG_DIR — not a hardcoded ~/.claude.)

Step 4: Report

Count, but do not delete, the init/uninstall backups:

bash
N_BAK=$(ls -1 "$CONFIG_DIR"/settings.json.bak-yas-* 2>/dev/null | wc -l | tr -d ' ')
[ "$N_BAK" -gt 0 ] && printf "  Kept %s settings.json.bak-yas-* backup(s) in %s\n" "$N_BAK" "$CONFIG_DIR"

Then print a summary:

  Done. statusLine config and runtime state removed.

  Still installed (this skill does not remove these):
    • the plugin itself — run:  claude plugin uninstall yas@yet-another-statusline
    • your config — yas.toml
    • backups — settings.json.bak-yas-*  (delete by hand if you want)

  Reload Claude Code to clear the statusline.

If CFG_STATE was foreign, remind the user their custom statusLine was kept on purpose.

</workflow>

© tmck-code, BSD-3-Clause. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/uninstall of tmck-code/yet-another-statusline.

Open the folder on GitHubat commit 26dc47d

Compare with similar skills

Uninstall next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Uninstall compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Uninstall this skilltmck-code/yet-another-statusline242—~1.2kAutomated safety check: NotesBSD-3-Clause
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Typescript Advanced Typesrolling-scopes/rsschool-app10k24 repos~4.2kAutomated safety check: PassMPL-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT
Greplooponyx-dot-app/onyx32k4 repos~3.3kAutomated safety check: PassMIT

Similar skills

  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • Typescript Advanced Types

    rolling-scopes/rsschool-app

    Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.

    10k GitHub starsUsed in 24 repos~4.2k tokens
    DevelopmentAuto-check passed
  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed
  • Guidelines

    akash-network/node

    Behavioral guidelines to reduce common LLM coding mistakes. An agent skill from akash-network/node.

    1.1k GitHub starsUsed in 22 repos~577 tokens
    DevelopmentAuto-check passed

More from tmck-code/yet-another-statusline

  • Yas Demo Text

    tmck-code/yet-another-statusline

    Convert make demo/img statusline snapshots into ANSI-stripped plain text for diffing and PR embedding.

    242 GitHub stars~649 tokensUpdated 3 days ago
    Auto-check passed
  • Yas PR Screenshots

    tmck-code/yet-another-statusline

    Generate before/after PNG screenshots for a YAS branch's rendering changes, push them to the yas-pr-screenshots repo, and hand back a markdown before/after table for the PR description.

    242 GitHub stars~1.2k tokensUpdated 3 days ago
    Auto-check passed
  • Tmck Code Statusline

    tmck-code/yet-another-statusline

    Edit the Claude Code statusline renderer safely. An agent skill from tmck-code/yet-another-statusline.

    242 GitHub stars~3k tokensUpdated 3 days ago
    Auto-check passed
  • Yas PR

    tmck-code/yet-another-statusline

    Assemble a pull request that follows this repo's PR template, then open it as a draft.

    242 GitHub stars~1.1k tokensUpdated 3 days ago
    Auto-check passed
  • Config

    tmck-code/yet-another-statusline

    Reconfigure yet-another-statusline — re-runs the interactive install wizard (glyph mode, theme, labels, token soft-limit, and Python version) against the already-installed plugin and re-wires…

    242 GitHub stars~254 tokensUpdated 3 days ago
    Auto-check: notes
  • Init

    tmck-code/yet-another-statusline

    Wire yet-another-statusline into Claude Code — writes statusLine.command to settings.json in CLAUDECONFIGDIR (default ~/.claude/).

    242 GitHub stars~185 tokensUpdated 3 days ago
    Auto-check: notes

Categories

Questions about Uninstall

What does Uninstall do?

Unwire yet-another-statusline from Claude Code — removes statusLine.command from settings.json in CLAUDECONFIGDIR (default ~/.claude/) and deletes the renderer's runtime state. Uninstall is an agent skill from tmck-code/yet-another-statusline.claude/) and deletes the renderer's runtime state.

When should I use Uninstall?

Uninstall fits situations like: development work in your project.

How do I install Uninstall in Claude Code?

Run `npx skills add tmck-code/yet-another-statusline --skill uninstall -a claude-code`. Or copy the skill folder (skills/uninstall in tmck-code/yet-another-statusline) into .claude/skills/uninstall in your project. Claude Code loads it when a task matches its description.

How do I install Uninstall in Codex?

Run `npx skills add tmck-code/yet-another-statusline --skill uninstall -a codex`. Or copy the skill folder (skills/uninstall in tmck-code/yet-another-statusline) into .agents/skills/uninstall in your project. Codex loads it when a task matches its description.

Can I use Uninstall in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tmck-code/yet-another-statusline --skill uninstall -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/uninstall, .gemini/skills/uninstall, .github/skills/uninstall and .opencode/skills/uninstall in your project.

What does Uninstall need to run?

Going by SKILL.md and its folder, Uninstall needs the command-line tools its instructions call (jq, claude and make). Its frontmatter pre-approves these tools: Read, Write, Bash.

Does Uninstall access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Uninstall safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Uninstall use?

Uninstall is published under the BSD-3-Clause licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Uninstall use?

About 1.2k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Uninstall?

Skills that share tags, products or a category with Uninstall: Finishing a Development Branch (obra/superpowers, 296k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars) and Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Uninstall?

tmck-code (a GitHub user) maintains it in tmck-code/yet-another-statusline, which has 242 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 4, 2026.

Source: tmck-code/yet-another-statusline on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.