CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ble-desk-lamp

Control BLE Desk Lamp through the generated BLE device CLI.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./testdata/golden/expected/generate-device-ble-control/ble-desk-lamp/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a compact, highly actionable setup guide: a well-gated install/verify workflow with explicit error-recovery guidance followed by a catalog of concrete CLI commands. Its weaknesses are minor — an unheaded, run-on final command paragraph and a live-control path described but not given as an executable command.

Suggestions

Break the final run-on paragraph into a headed "## Commands" section with one command per line (or a short list), so each capability (capabilities, status, doctor, scan, toggle) is scannable.

Provide the concrete build command for live control instead of only describing it, e.g. the `go build -tags ble_live` invocation followed by the `--live` usage example.

DimensionReasoningScore

Conciseness

The body is lean — install command, verify step, PATH note, two targeted error-recovery notes, and a command catalog — with no explanations of concepts Claude already knows. It is not a 5 because the final paragraph packs six commands into a single unbroken run-on block and the sentence "If the `npx` install fails before this CLI has a public-library category... after publish" is convoluted and time-sensitive; not a 3 because there is no genuine padding or over-explanation.

4 / 5

Actionability

Commands are concrete and copy-paste ready throughout: `npx -y @mvanhorn/printing-press-library install ble-desk-lamp --cli-only`, `ble-desk-lamp-pp-cli --version`, `capabilities --json`, `status --json`, `doctor`, `scan --live`, `toggle --dry-run --json`. It is not a 5 because the core live-control path ("build with `-tags ble_live` and pass `--live`") is described but never given as an executable build command, leaving a minor gap in the most common use case.

4 / 5

Workflow Clarity

The prerequisites form a numbered install → verify → PATH sequence with an explicit validation gate ("Do not proceed with skill commands until verification succeeds") and feedback loops for both install failure and the command-not-found case. It is not a 5 because post-install usage is presented as a flat command catalog with no recommended order rather than a sequenced control workflow; not a 3 because validation checkpoints and error-recovery loops are explicitly present for the risky setup step.

4 / 5

Progressive Disclosure

This is a single-file skill under 50 lines with no bundle files (no references/, scripts/, or assets/ directories exist) and one clear section header for prerequisites, so nothing is inlined that belongs elsewhere. It is not a 5 because the trailing command catalog has no heading of its own, leaving the last paragraph organizationally orphaned; not a 3 because the content is short, appropriately placed, and easy to navigate.

4 / 5

Total

16

/

20

Passed

Description

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

The description names a highly specific, distinctive niche but is underdeveloped: it uses one generic action verb ("Control") with no enumerated capabilities and provides no "Use when..." trigger guidance. It scores at the anchor-3 cap for completeness and would benefit most from an explicit trigger clause and a short capability list.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user mentions their desk lamp, turning the Bluetooth/BLE lamp on or off, or controlling the ble-desk-lamp device."

Enumerate concrete capabilities instead of the generic verb "Control", e.g. "Toggle power, check lamp status, scan for devices, and inspect callable BLE capabilities via the generated CLI."

Include common user phrasings such as "Bluetooth" and "smart lamp" as trigger synonyms alongside "BLE".

DimensionReasoningScore

Specificity

"Control BLE Desk Lamp through the generated BLE device CLI" names the domain precisely, but the only action is the generic verb "Control", matching the anchor 'Names the domain but actions are minimal or generic'. It is not a 3 because no concrete capability (toggle, status, scan) is enumerated; not a 1 because the domain and tool are explicitly named rather than abstract.

2 / 5

Completeness

The 'what' is clear ("Control BLE Desk Lamp through the generated BLE device CLI") but the 'when' is entirely absent — there is no "Use when..." clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3. Not a 4 because no usage trigger is present even implicitly.

3 / 5

Trigger Term Quality

"BLE Desk Lamp" is a specific, natural keyword for this niche, but common variations a user would say are missing ("Bluetooth", "smart lamp", "turn on/off", "light"), matching the anchor 'Some relevant keywords but missing common variations or synonyms'. Not a 4 because synonym coverage is thin; not a 2 because the keyword present is specific rather than generic.

3 / 5

Distinctiveness Conflict Risk

A named device ("BLE Desk Lamp") driven through a specific generated CLI is a clear niche with distinct triggers and minimal conflict risk with any other skill. Not a 4 because the device name itself is the trigger and there is no meaningful overlap with related skills.

5 / 5

Total

13

/

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

mvanhorn/cli-printing-press

Path

testdata/golden/expected/generate-device-ble-control/ble-desk-lamp/SKILL.md

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.