catalan-adobe/cmux-setup
BEFORE manually calling cmux set-status or writing chpwd hooks for workspace coloring, use this skill. Manages workspace color rules that auto-apply based on directory patterns. Handles config creation, zsh hook installation, rule management, and on-demand workspace coloring via cmux set-status. Triggers on "cmux setup", "workspace colors", "color this workspace", "add color rule", "project colors", or any request to visually differentiate cmux workspaces.
77
97%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly defines its niche around cmux workspace color management. It provides specific actions, explicit trigger terms, and a clear 'when to use' clause. The opening 'BEFORE manually calling...' line adds helpful context about when this skill should be preferred over manual approaches.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: manages workspace color rules, handles config creation, zsh hook installation, rule management, and on-demand workspace coloring via cmux set-status. | 3 / 3 |
Completeness | Clearly answers both 'what' (manages workspace color rules, config creation, zsh hook installation, rule management, on-demand coloring) and 'when' (explicit 'Triggers on...' clause with specific trigger phrases, plus a 'BEFORE manually calling...' preamble that clarifies when to prefer this skill). | 3 / 3 |
Trigger Term Quality | Includes a rich set of natural trigger terms users would say: 'cmux setup', 'workspace colors', 'color this workspace', 'add color rule', 'project colors', plus contextual phrases like 'visually differentiate cmux workspaces' and 'directory patterns'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche around cmux workspace coloring, directory-pattern-based color rules, and zsh hook installation. Unlikely to conflict with other skills due to the specific tool (cmux) and domain (workspace color management). | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that provides clear, actionable guidance for managing cmux workspace colors. It efficiently covers two usage modes, provides executable commands throughout, and includes a helpful conversational request mapping table. The only minor weakness is that all content is inline with no bundle files provided to support the referenced script, though the overall length is manageable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It avoids explaining what cmux is, what zsh hooks are, or how JSON works. Every section serves a clear purpose and there's minimal filler text. The conversational request table is compact and useful. | 3 / 3 |
Actionability | Provides fully executable bash commands for every operation, a concrete script location resolution block, specific CLI flags, and a complete JSON config example. The two modes (persistent vs on-demand) give clear, copy-paste-ready instructions including the direct cmux fallback command. | 3 / 3 |
Workflow Clarity | Mode 1 (Persistent Setup) is a clearly numbered 5-step workflow with a logical sequence: gather info → add rules → install hook → apply → inform user about sourcing. Mode 2 provides clear branching (existing config vs ad-hoc). The rule management table maps conversational requests to specific actions. No destructive batch operations require missing validation steps. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections, but it's all inline in a single file. The script location, config format, and rule management table could potentially be separated, though the total length is moderate enough that this is acceptable. No bundle files are provided to reference, and the skill references a script (cmux-setup.js) that isn't included in the bundle for evaluation. | 2 / 3 |
Total | 11 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Reviewed
Table of Contents