agentsclimarketplace
Sign in

Install harness statusline

Skill woditschka/agentic-coding-reference/.claude/skills/install-harness-statusline

Install or update the harness-stats tooling — harness-statusline.sh, cache-report.sh, and the cache-report skill — from this repo's tools/harness-stats/ into the user's ~/.claude/ directory. Thin front-end for tools/harness-stats/install.sh: run its check mode to show drift, apply only on the user's approval. Use when the user asks to install the cache tooling, set up the statusline, update the harness-stats scripts, or reconfigure cache reporting. Examples: "set up the statusline", "install harness-stats", "update the cache tooling".From its SKILL.md

Install
npx -y skills add woditschka/agentic-coding-reference --skill install-harness-statusline

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 15 stars15 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.8 KB, as published. Nobody here has run it

install-harness-statusline

The mechanics live in tools/harness-stats/install.sh (source of truth: this repo's tools/harness-stats/). The skill adds the approval gate: never apply without the user's explicit OK.

Process

  1. Detect drift. Run from the repo root (the script reads sources relative to itself; if not in this repo, stop and say so):

    tools/harness-stats/install.sh check

    It prints one status per target — identical, drift (N lines), or missing — for the three files and the statusLine block in ~/.claude/settings.json.

  2. Show the table and get approval. Present the drift; for drifted rows, offer the unified diff on request. Do NOT edit without explicit approval ("apply", "go ahead", "install"). If everything is identical, report that and stop — nothing to do.

  3. Apply:

    tools/harness-stats/install.sh apply

    It copies the three files, preserving the executable bit. It merges the statusLine block into ~/.claude/settings.json with jq — other keys untouched, a replaced statusLine.command echoed for recovery. It then runs two smoke tests: statusline against the latest transcript, and cache-report.sh --list. A smoke-test failure exits non-zero: do not declare success; report the exact output. Likely culprits: missing jq or awk, or a stat call that fell through both GNU and BSD paths.

  4. Report. What changed, the smoke-test results, and the reminder that Claude Code must restart for the statusline and skill to load.

What this skill does NOT do

  • Uninstall — the user deletes the targets and the statusLine key manually.
  • Tune thresholds — the color-coding constants live at the top of harness-statusline.sh and cache-report.sh; edit the sources in tools/harness-stats/, then re-run.
  • Pull from upstream — the source of truth is this repo.
  • Survive across machines — ~/.claude/ is per-machine and shared by every project on it; run once per machine.
  • Run the report — that is the installed cache-report skill.
  • Partial installs — apply refreshes all targets; per-file selection is a manual copy.

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.