control-cli

Build or adapt a local harness to drive, inspect, and profile an interactive CLI or TUI without external services. Use for CLI UX checks, startup regressions, memory leaks, hangs, prompt flows, or terminal demos.

Quality

88%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

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 a strong description that clearly communicates what the skill does (building local test harnesses for CLI/TUI applications) and when to use it (specific scenarios like memory leaks, hangs, startup regressions). It uses third person voice, includes natural trigger terms, and occupies a distinct niche that minimizes conflict with other skills.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'drive, inspect, and profile an interactive CLI or TUI', and enumerates specific use cases like 'CLI UX checks, startup regressions, memory leaks, hangs, prompt flows, terminal demos'.	3 / 3
Completeness	Clearly answers both what ('Build or adapt a local harness to drive, inspect, and profile an interactive CLI or TUI without external services') and when ('Use for CLI UX checks, startup regressions, memory leaks, hangs, prompt flows, or terminal demos') with explicit trigger guidance.	3 / 3
Trigger Term Quality	Includes strong natural keywords users would say: 'CLI', 'TUI', 'memory leaks', 'hangs', 'startup regressions', 'prompt flows', 'terminal demos', 'UX checks'. These cover a good range of terms a user might naturally use when needing this skill.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche: local harness for interactive CLI/TUI testing and profiling. The combination of 'interactive CLI or TUI', 'without external services', and specific concerns like 'startup regressions, memory leaks, hangs' makes it highly distinct and unlikely to conflict with general testing or coding skills.	3 / 3
	Total	12 / 12 Passed

Implementation

77%

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

This is a solid, actionable skill with executable code examples for both tmux and PTY harnesses, a clear workflow loop, and sensible guardrails. Its main weakness is moderate verbosity—some sections like 'What It Is Used For' and the high-level profiling recipes add length without proportional value. The content would benefit from splitting detailed harness implementations into separate files for better progressive disclosure.

Suggestions

Consider moving the PTY harness and profiling recipes into separate referenced files (e.g., PTY_HARNESS.md, PROFILING.md) to keep the main skill leaner and improve progressive disclosure.

Trim or remove the 'What It Is Used For' section—Claude can infer use cases from the skill content itself, and this list largely restates the skill description.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient but includes some sections that could be tightened. The 'What It Is Used For' bullet list is somewhat redundant given the description, and the 'Profiling Recipes' section is fairly high-level without adding much executable value. However, the code examples are lean and the guardrails are concise.	2 / 3
Actionability	Both the tmux and PTY harness examples are fully executable, copy-paste ready code blocks with concrete commands. The profiling recipes, while higher-level, describe specific sequences of actions. The harness loop provides a clear step-by-step process.	3 / 3
Workflow Clarity	The 'Harness Loop' provides a clear 8-step sequence with explicit validation checkpoints (step 6: wait for a concrete screen pattern before next action). The workflow includes cleanup (step 8), error-aware progression, and the guardrails section reinforces deterministic waits over sleeps. The profiling recipes also follow clear sequences.	3 / 3
Progressive Disclosure	The content is well-organized with clear section headers and a logical progression from overview to specific harness types to profiling to guardrails. However, the PTY harness and profiling recipes could benefit from being in separate referenced files, as the skill is fairly long. No bundle files exist to offload detail into, and no references to external docs are provided.	2 / 3
	Total	10 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: cursor/plugins
Commit: 7dd9fea

Reviewed: about 21 hours 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.