live-check
Skill10 starsChanged 20 days agoMITView on GitHub
Use to see a paneline change working in a real Claude Code session, and to read the colours the screen shows.
- Reads credentials
4 other projects use a version of this.
Adopted by
Most recently taken up by
- NahumLitvin/prismantistheir own version, first seen Nov 13, 2026
- Cohozen/magasins-u-mcp-servertheir own version, first seen Nov 8, 2026
- nadavnaveh/skillstheir own version, first seen Nov 1, 2026
- iamrohithrnair/mermantheir own version, first seen Nov 1, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- NahumLitvin/prismantis★ 426same name
- iamrohithrnair/merman★ 42same name
- nadavnaveh/skills★ 3same name
- Cohozen/magasins-u-mcp-server★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- add-pane-tabSkill
- visual-reviewSkill
- write-testSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Run the plugin from your worktree in a real session inside a private tmux server.
- Very specific: line 12
Always use your own tmux socket, tmux -L <name>.
- Very specific: line 14
Do not use bypassPermissions.
- Distinctive: line 27
Write a tmux config for truecolor, then start a wide session so the pane has room:
- Distinctive: line 34
Wait a few seconds, then read the screen:
- Very specific: line 41
When done, stop only your server: tmux -L pl-check kill-server.
- Very specific: line 43
Look at: widths of 60 and 120 columns, long names, empty state, the accent colour after /color red, the colours in each theme, and that …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Live check
Run the plugin from your worktree in a real session inside a private tmux server. Unit tests do not show layout or colour. This does.
Rules:
- Always use your own tmux socket,
tmux -L <name>. Never the default socket. Nevertmux kill-serverwithout-L <name>. - Load the plugin from the worktree you edit, and from nowhere else. An installed plugin with the same name loads first and warns, so do not rely on one.
- Do not use
bypassPermissions. - Below 144 columns a cold start may show no pane, because all sessions share one
askedlist (seedocs/engine-limits.md). A run that needs the pane sends/panelineafter start, or uses 144 columns or more. A missing pane there is not a product fault and not a reason to retry the start.
Steps:
- Pick a socket name, for example
pl-check. - Make an isolated config dir outside the repo, so
/themedoes not write your own~/.claude/settings.json:
This dir is not logged in. Log in there, or setS=<scratch dir>; mkdir -p $S/config $S/work echo '{"hasCompletedOnboarding":true,"lastOnboardingVersion":"2.1.289","projects":{"'$S/work'":{"hasTrustDialogAccepted":true}}}' > $S/config/.claude.json echo '{"theme":"dark"}' > $S/config/settings.jsonANTHROPIC_API_KEY, before you expect replies. - Write a tmux config for truecolor, then start a wide session so the pane has room:
Your shell may setprintf 'set -g default-terminal tmux-256color\nset -as terminal-features ",*:RGB"\n' > $S/tmux.conf tmux -L pl-check -f $S/tmux.conf new-session -d -s main -x 180 -y 50 -c $S/work \ "CLAUDE_CODE_PLUGIN_DIRS=<worktree> CLAUDE_CODE_TMUX_TRUECOLOR=1 COLORTERM=truecolor CLAUDE_CONFIG_DIR=$S/config CLAUDE_CODE_NO_FLICKER=1 claude --plugin-dir <worktree>"CLAUDE_CODE_PLUGIN_DIRSto the main checkout. The value above overrides it with the worktree. Without the tmux config andCLAUDE_CODE_TMUX_TRUECOLOR=1, captures show only38;5;Ncodes. - Wait a few seconds, then read the screen:
- Text:
tmux -L pl-check capture-pane -p -t main - With colours:
tmux -L pl-check capture-pane -e -p -t main. Colours show as escape codes, for example38;2;R;G;Bfor a truecolor foreground. The values depend on the theme.
- Text:
- Drive it with
tmux -L pl-check send-keys -t main "/paneline" Enter. Send a prompt to produce tool calls and replies. Tabs are clickable buttons: attach to the session in a real terminal withtmux -L pl-check attachand click. - Switch the theme: send
/themeand Enter to open the picker, move with the arrows (Auto, Dark, Light, Dark colorblind, Light colorblind, Dark ANSI, Light ANSI), then Enter. Capture again. Every paneline colour must change with the theme and nothing needs a reload. In an ANSI theme, a truecolor code (38;2or48;2) on screen means a hardcoded colour leaked. - Saving a file in the worktree reloads the hooks in the running session. Edit, wait, capture again.
- Headless alternative for checks that need no screen:
claude -p --setting-sources project --plugin-dir <worktree> "<prompt>". - When done, stop only your server:
tmux -L pl-check kill-server.
Look at: widths of 60 and 120 columns, long names, empty state, the accent colour after /color red, the colours in each theme, and that nothing flickers or grows while idle.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

