CtrlK
BlogDocsLog inGet started
Tessl Logo

cli-anything

Use when the user wants Codex to build, refine, test, validate, or list CLI-Anything harnesses for GUI applications or source repositories. Adapts the full CLI-Anything methodology to Codex without changing the generated Python harness format.

77

1.55x
Quality

Does it follow best practices?

Impact

95%

1.55x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

50%

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

The skill body is well-organized with a clear resource map and mode structure, but it leans heavily on reference files and scripts that are not present in the bundle, and its workflows lack explicit validation feedback loops. It reads as a routing overview rather than a self-contained, executable guide.

Suggestions

Ship the referenced bundle (references/HARNESS.md, references/commands/*.md, references/guides/, scripts/repl_skin.py, etc.) so the signaled one-level references actually resolve.

Add explicit validate-then-retry feedback loops to the Build and Test workflows, especially around destructive/batch operations like session mutations and installed-command subprocess coverage.

Replace the directory-tree structure block with concrete, copy-pasteable scaffolding commands or point to a real template file that exists in the bundle.

DimensionReasoningScore

Conciseness

Sections are organized and avoid explaining basics, but the six-step fallback ladder and the document path-remapping table add length that could be tightened.

2 / 3

Actionability

Concrete specifics exist (find_namespace_packages, CLI_ANYTHING_FORCE_INSTALLED=1, --dry-run, _resolve_cli()), but core build steps delegate to reference files and the structure block is a directory tree rather than executable code.

2 / 3

Workflow Clarity

Modes are clearly delineated with an ordered read-first sequence, but build/test workflows lack explicit validate-then-fix feedback loops; per the rubric, missing feedback loops for batch/destructive ops caps this at 2.

2 / 3

Progressive Disclosure

The body is well structured with a Resource Map and clearly signaled one-level references, but the referenced files (references/*, scripts/*.py, scripts/templates/*) are absent from the bundle and the fallback ladder reaches for an external repo, leaving navigation partly broken.

2 / 3

Total

8

/

12

Passed

Description

85%

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 lists concrete actions, gives an explicit use-trigger, and carves out a distinctive niche. Its only weakness is trigger-term breadth, which depends on the domain proper noun rather than a range of natural synonyms.

Suggestions

Broaden trigger-term coverage with natural synonyms users might say, e.g. "generate a CLI", "wrap a GUI app in commands", or "create a command-line harness".

Consider naming the output artifact a user would recognize (e.g. "a pip-installable cli-anything-<software> command") so the trigger reads more concretely.

DimensionReasoningScore

Specificity

Enumerates five concrete actions ("build, refine, test, validate, or list") against named targets ("CLI-Anything harnesses for GUI applications or source repositories"), matching the multiple-specific-actions anchor.

3 / 3

Completeness

Answers both what (build/refine/test/validate/list harnesses) and when via an explicit "Use when the user wants Codex to..." trigger clause, satisfying the both-what-and-when anchor.

3 / 3

Trigger Term Quality

The action verbs (build/test/validate/list harnesses) are natural, but noun-domain coverage leans on the single proper noun "CLI-Anything" without broader synonyms a user might say (e.g. "make a CLI"), so common variations are missing.

2 / 3

Distinctiveness Conflict Risk

"CLI-Anything harnesses for GUI applications or source repositories" is a narrow, distinctive niche unlikely to trigger for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 26 missing, 14 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository
HKUDS/CLI-Anything
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.