CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

63

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/tmux-cli/skills/tmux-cli/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

A tight, actionable skill body with good organization and a concrete executable example. Main gaps are mild redundancy in the intro and an unsequenced agent-chat workflow that is only referenced.

Suggestions

Tighten the opening paragraph and remove the 'This is useful for' bullet list, since those use cases are evident from the execute example.

Add a short sequenced workflow for the agent-chat path (send -> wait_idle -> capture) so it is actionable rather than only named, and note checking exit_code/-1 as an explicit validation checkpoint.

DimensionReasoningScore

Conciseness

The body is mostly lean and assumes Claude's competence, but the opening restates the description and the 'This is useful for' bullet list spells out obvious use cases that could be trimmed.

2 / 3

Actionability

Provides concrete, executable commands with real flags and expected JSON output, plus a copy-paste-ready install fallback — fully actionable.

3 / 3

Workflow Clarity

The execute flow is clear and distinguishes execute from agent-chat, but the send/wait_idle/capture agent-chat flow is only named without a sequenced workflow, and validation handling is implicit rather than an explicit checkpoint.

2 / 3

Progressive Disclosure

Under 50 lines with clean sectioning (Instructions / Key Commands / subsections) and a single one-level pointer to 'tmux-cli --help' for the full surface; appropriate for a simple single-purpose skill with no bundle files.

3 / 3

Total

10

/

12

Passed

Description

75%

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 concise, well-scoped description that clearly states both capability and trigger condition with low conflict risk. It could be strengthened by listing the concrete sub-actions and varying the trigger phrasing for broader natural coverage.

Suggestions

List the concrete actions the utility performs (e.g. send messages, wait for idle, capture output, execute commands) to lift specificity from 2 to 3.

Broaden trigger terms beyond the repeated 'communicate with other CLI Agents or Scripts in other tmux panes' to cover common user phrasings like 'talk to another pane' or 'run a command in another tmux pane'.

DimensionReasoningScore

Specificity

Names the domain ('communicate with other CLI Agents or Scripts in other tmux panes') and a single concrete action, but does not enumerate multiple specific actions (e.g. send, wait_idle, capture), so it stops short of the comprehensive anchor.

2 / 3

Completeness

Explicitly answers 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 communicate...'), satisfying the explicit-trigger anchor.

3 / 3

Trigger Term Quality

Includes relevant natural terms ('communicate', 'tmux panes', 'CLI Agents', 'Scripts') but the phrasing is repetitive and somewhat technical rather than a broad coverage of common user phrasings.

2 / 3

Distinctiveness Conflict Risk

Targets a clear niche (cross-pane tmux communication) with distinct triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

10

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
pchalasani/claude-code-tools
Reviewed

Table of Contents

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.