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.

75

Quality

92%

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

85%

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

The body is highly actionable with executable tmux/PTY harnesses, profiling recipes, and a clear sequenced loop with checkpoints. The only real weakness is mild redundancy between the description's triggers and the "What It Is Used For" section.

Suggestions

Trim overlap with the description: compress the "What It Is Used For" list to cases not already named in the frontmatter "Use for" clause, or fold it into the intro sentence.

Add one explicit error-recovery note in the Harness Loop (e.g., what to do if the expected screen pattern never appears) to strengthen the existing checkpoint.

DimensionReasoningScore

Conciseness

The body is mostly efficient with no concept explanations Claude already knows, but the "What It Is Used For" list and intro restates several triggers from the description (startup regressions, memory leaks, hangs, prompt flows, terminal demos) and could be tightened. It is leaner than the verbose level-1 anchor but does not fully meet "every token earns its place."

2 / 3

Actionability

Executable tmux and PTY code blocks plus concrete profiling recipes give copy-paste-ready guidance; placeholders like <command-under-test> are explicitly justified by the guardrails (adapt to the current repo), so this is not mere pseudocode. It clears the level-2 pseudocode bar.

3 / 3

Workflow Clarity

The 8-step Harness Loop is clearly sequenced with an explicit checkpoint ("Wait for a concrete screen pattern or prompt before the next action") and a clean-kill final step. Because driving a CLI is not a destructive/batch operation, the absence of a validate-retry loop does not cap the score.

3 / 3

Progressive Disclosure

It is a single well-organized file with clear sections and no nested/deep references; no bundle files exist, and the scope fits one file. This matches the level-3 well-organized-sections guidance for skills that need no external references.

3 / 3

Total

11

/

12

Passed

Description

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.

The description is strong: it names concrete actions, gives explicit "Use for" triggers with natural terms, and carves out a distinctive local-CLI-harness niche. Voice is appropriately third person/imperative with no first/second person.

DimensionReasoningScore

Specificity

"Build or adapt a local harness to drive, inspect, and profile an interactive CLI or TUI" lists multiple concrete actions (build/adapt, drive, inspect, profile), matching the level-3 anchor. It is not merely naming a domain, so it clears the level-2 bar.

3 / 3

Completeness

It states what ("Build or adapt a local harness to drive, inspect, and profile...") and an explicit when ("Use for CLI UX checks, startup regressions..."), satisfying both halves. It is not missing the when clause, so it is above level 2.

3 / 3

Trigger Term Quality

"CLI UX checks, startup regressions, memory leaks, hangs, prompt flows, or terminal demos" plus "interactive CLI or TUI" gives good coverage of natural terms a user would actually say. It is not technical jargon-only, so it is above level 2.

3 / 3

Distinctiveness Conflict Risk

The niche is clear — a local CLI/TUI harness "without external services" — with distinct triggers unlikely to fire for unrelated skills. It is more specific than the level-2 "Works with document files" style overlap.

3 / 3

Total

12

/

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
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.