tmux-cli

CLI utility to communicate with other CLI Agents or Scripts in other tmux panes; use it only when user asks you to communicate with other CLI Agents or Scripts in other tmux panes.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A concise, mostly actionable body for a simple skill: the execute command is documented with executable examples and output semantics, and structure is appropriate for its size. The main gap is that the agent-to-agent workflow (send/wait_idle/capture) is referenced but never shown, leaving the second advertised use case without concrete guidance.

Suggestions

Add a short example block for the agent-chat path, e.g. tmux-cli send 'run the tests' --pane=ops:1.3, tmux-cli wait_idle --pane=ops:1.3, tmux-cli capture --pane=ops:1.3, so both advertised workflows are actionable.

Trim the 'This is useful for:' bullet list — the use cases are already inferable from the command and exit-code semantics.

Dimension	Reasoning	Score
Conciseness	The body is lean with executable examples and no explanation of concepts Claude already knows ('tmux-cli execute "make test" --pane=2'). Not 5 because the 'This is useful for:' bullet list and the install aside add mild padding that could be trimmed.	4 / 5
Actionability	The execute section gives copy-paste-ready commands with flags, JSON output shape, and exit-code semantics. Not 5 because 'send + wait_idle + capture' — the agent-to-agent path — is named with no example, and detail is deferred to '--help' rather than shown.	4 / 5
Workflow Clarity	For this simple skill, execute usage is unambiguous with concrete pane and timeout flags. Not 5 because the second workflow (agent chat via send/wait_idle/capture) is only named, with no sequence or guidance; not 3 since the primary action needs no validation loop.	4 / 5
Progressive Disclosure	The skill is under 50 lines, needs no external reference files, and content is organized into clear Instructions and Key Commands sections with an appropriate pointer to 'tmux-cli --help' for the full surface. This matches the simple-skill exception for a 5.	5 / 5
	Total	17 / 20 Passed

Description

73%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A distinctive, correctly-scoped description with an explicit use-when clause. Its main weaknesses are a tautological trigger clause that adds no new trigger vocabulary and a lack of concrete action verbs describing what the utility actually does.

Suggestions

Replace the tautological trigger clause with distinct concrete triggers, e.g. 'Use when the user asks to send commands or messages to an agent in another tmux pane, coordinate multiple Claude Code instances, or run a command in a specific pane and check its exit code.'

List the concrete capabilities in the what-clause, e.g. 'CLI utility to execute commands in other tmux panes with exit-code detection, and send/wait/capture messages to other CLI Agents or Scripts in those panes.'

Add natural synonyms users might say, such as 'tmux window', 'agent-to-agent', or 'multi-agent', to broaden trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('communicate with other CLI Agents or Scripts in other tmux panes') and one concrete capability, but lists no specific actions like execute, send, or capture. Anchor 3 fits: domain plus 1-2 concrete actions, not comprehensive; not 4 because several specific actions are absent.	3 / 5
Completeness	Both what ('CLI utility to communicate with other CLI Agents or Scripts in other tmux panes') and when ('use it only when user asks you to...') are present. Not 5 because the when-clause is a tautological restatement of the what rather than distinct concrete trigger phrases.	4 / 5
Trigger Term Quality	'communicate', 'CLI Agents', 'Scripts', and 'tmux panes' are natural phrases a user would say. Not 5 because the trigger clause repeats the capability clause verbatim, offering no synonyms or variations like 'send commands to another pane' or 'agent-to-agent'.	4 / 5
Distinctiveness Conflict Risk	The tmux-pane inter-agent communication niche is highly specific with distinct triggers ('tmux panes', 'CLI Agents'), giving minimal conflict risk with other skills. Not 4 because no plausible overlapping skill shares these triggers.	5 / 5
	Total	16 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: pchalasani/claude-code-tools
Path: plugins/tmux-cli/skills/tmux-cli/SKILL.md
Commit: 0ca7320

Reviewed: 13 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.