CtrlK
BlogDocsLog inGet started
Tessl Logo

kumar/tessl-agent

Working reference for agents using the Tessl CLI — create and publish plugins/skills, install from the registry, update, lint, and run evals.

68

Quality

86%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Risky

Do not use without reviewing

Overview
Quality
Evals
Security
Files

Quality

Content

65%

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

An extremely actionable CLI reference with excellent command coverage and a useful failure table, but it is a long monolithic single-file catalog with repeated flag variants and no validation checkpoints around destructive operations. It is well-structured yet could benefit from offloading detail and tightening repetition.

Suggestions

Consolidate repeated per-flag command variants (e.g. publish, install) into a single command plus a flag table to trim length without losing actionability.

Add explicit validation/confirmation checkpoints before destructive and batch operations — e.g. run `tessl plugin lint` and confirm before `plugin unpublish`/`archive`, and verify membership before `workspace delete` or `uninstall`.

Move the exhaustive command catalog into a referenced bundle file (e.g. references/cli-reference.md) so SKILL.md stays a concise overview with one-level-deep links, improving progressive disclosure.

DimensionReasoningScore

Conciseness

The body is mostly efficient — concrete commands with little conceptual padding and no explaining of basics Claude already knows — but ~480 lines repeat the same command across many one-flag-differing variants (e.g. eight `tessl plugin publish` lines, eight `tessl install` lines) that could be tightened into flag tables.

2 / 3

Actionability

Hundreds of concrete, executable, copy-paste-ready commands with specific flags and a Common Failures error→cause→fix table; fully actionable rather than descriptive.

3 / 3

Workflow Clarity

Typical Agent Workflows give clear numbered sequences with a lint checkpoint, but destructive/batch operations (unpublish, archive, workspace delete, uninstall) are listed as bare commands without validation or confirmation checkpoints, which caps this dimension at 2 per the rubric.

2 / 3

Progressive Disclosure

Section headings are clear and well-organized, but the skill is a ~480-line single-file command reference with no bundle files and no offloaded reference docs; content that would fit a separate reference file is kept inline, matching the score-2 anchor.

2 / 3

Total

9

/

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.

A strong, specific, third-person-voice trigger description that clearly states what the skill does and when to invoke it, with a rich set of natural trigger phrases. It satisfies every dimension at the top of the scale.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'publishing plugins or skills, installing from the registry, running evals, linting, bumping versions, running reviews, launching skills, managing workspaces' — rather than vague language, matching the score-3 anchor.

3 / 3

Completeness

Explicitly answers both 'what' (the enumerated Tessl operations) and 'when' via the 'Use when working with Tessl' clause plus the explicit 'Triggers on:' list.

3 / 3

Trigger Term Quality

The 'Triggers on:' clause gives many natural phrases a user would actually say ('publish this skill', 'install a skill', 'run evals', 'bump the version', 'lint the skill', 'run a review', 'check tessl status'), giving strong coverage.

3 / 3

Distinctiveness Conflict Risk

Scoped to a specific toolchain ('Tessl', 'tessl plugin', 'the registry', 'what tessl tools are available') with distinct triggers unlikely to collide with unrelated skills.

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.

Reviewed

Table of Contents