CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

68

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 tight, self-contained skill with genuinely executable tmux and PTY harness examples plus sensible guardrails. Main gaps are placeholder-driven code blocks and the absence of an explicit failure-recovery path in the harness loop.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence: no explanations of what tmux, PTYs, or profilers are, and sections like 'Harness Options' and 'Profiling Recipes' are terse bullets that each instruct rather than pad.

5 / 5

Actionability

Provides an executable tmux command block and a complete Python PTY script with concrete select/read logic, but both rely on placeholders ('<command-under-test>', '<ready text>') so they are not fully copy-paste ready.

4 / 5

Workflow Clarity

The 8-step 'Harness Loop' is clearly sequenced with checkpoint behaviors ('Wait for a concrete screen pattern or prompt before the next action', 'Kill the session cleanly') and cleanup guardrails, but there is no explicit error-recovery loop for when a pattern never appears.

4 / 5

Progressive Disclosure

No bundle files exist and the body is organized into well-signaled sections with no content that clearly belongs in a separate file, though at ~105 lines with inline scripts it sits just above the size where sections alone would warrant a 5.

4 / 5

Total

17

/

20

Passed

Description

83%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 strong description: third-person, concise, with explicit what-and-when structure and natural trigger phrases. It is near the top anchors on all dimensions with only minor keyword-synonym and overlap-risk gaps.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('drive, inspect, and profile an interactive CLI or TUI'), with only minor coverage gaps (e.g., what inspecting entails).

4 / 5

Completeness

Explicitly answers both what ('Build or adapt a local harness to drive, inspect, and profile...') and when ('Use for CLI UX checks, startup regressions, memory leaks, hangs, prompt flows, or terminal demos') with concrete trigger phrases in third person.

5 / 5

Trigger Term Quality

'CLI UX checks, startup regressions, memory leaks, hangs, prompt flows, or terminal demos' are natural phrases users would say, though a few synonyms (recording, PTY, profiling) are missing.

4 / 5

Distinctiveness Conflict Risk

The local-harness-for-interactive-CLI/TUI niche is distinct, but terms like 'memory leaks' and 'startup regressions' carry minor overlap risk with general profiling or test-harness skills.

4 / 5

Total

17

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
cursor/plugins
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.