CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ble-opaque-binary

Control BLE Opaque Binary Device through the generated BLE device CLI.

Quality

66%

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-opaque/ble-opaque-binary/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 an efficient, copy-paste-ready setup guide with genuine validation checkpoints and error-recovery guidance for installation failures. Its main weakness is that the skill's stated purpose — controlling the device — is never demonstrated with a concrete command; only install, verification, and inspection commands appear, and the live-mode build instruction is underspecified.

Suggestions

Add one concrete control example (e.g., the CLI command that invokes a callable capability from 'capabilities --json' output) so the core task is executable, not just setup.

Replace 'build with -tags ble_live' with the actual build command (module path and output binary) or reference where the source is obtained.

Give the inspection/live-mode paragraph its own section header (e.g., '## Inspecting capabilities and live mode') so the operational guidance is not dangling after the prerequisites section.

DimensionReasoningScore

Conciseness

The body is lean and command-driven with no explanation of concepts Claude already knows — install command, verify step, PATH guidance, and inspection commands each earn their tokens. Minor trims are possible (e.g., the dense final paragraph bundling capabilities, status, live-mode, and session-IPC notes), so it fits 'Efficient; minor instances of over-explanation that could be trimmed' rather than anchor 5's every-token-counts ideal.

4 / 5

Actionability

Setup and inspection are concretely executable ('npx -y @mvanhorn/printing-press-library install ble-opaque-binary --cli-only', 'ble-opaque-binary-pp-cli --version', 'capabilities --json', 'status --json', 'doctor', 'scan --live'), and it even specifies install directories per OS. However, the skill's core purpose — controlling the device — has no example invocation, and 'build with -tags ble_live' is a hint, not an executable command. Missing key details for the main task fits 'Some concrete guidance but incomplete'.

3 / 5

Workflow Clarity

The install-verify workflow is well sequenced with an explicit validation checkpoint ('Verify: ble-opaque-binary-pp-cli --version', 'Do not proceed with skill commands until verification succeeds') and feedback loops for two failure modes (npx failure fallback; PATH 'command not found' remedy). It sits at anchor 4 rather than 5 because the sequence from setup to actually operating the device is left implicit.

4 / 5

Progressive Disclosure

At ~17 lines with no external files needed (no references/, scripts/, or assets/ exist in the bundle), this is a simple single-file skill that could merit a 5 under the simple-skill note. It lands at 4 because the usage/live-mode paragraph sits outside any section header — the body has only '## Prerequisites: Install the CLI', leaving the operational commands unsectioned.

4 / 5

Total

15

/

20

Passed

Description

48%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 identifies a clear, distinct niche (a specific BLE device driven via a generated CLI) but is thin as a trigger: it states only the generic action 'Control' with no concrete capability list and no 'use when' guidance. A user or Claude relying on description-based triggering has little to match beyond the device name itself.

Suggestions

Enumerate concrete capabilities in the description, e.g., 'Inspect callable BLE capabilities, check replay-backed status, scan for live devices, and control the BLE Opaque Binary Device via the generated ble-opaque-binary-pp-cli.'

Add an explicit trigger clause such as 'Use when the user mentions the BLE Opaque Binary Device, ble-opaque-binary, or asks to control/inspect it over BLE.'

Include natural synonyms (Bluetooth, Bluetooth Low Energy, BLE) so the description matches varied user phrasing.

DimensionReasoningScore

Specificity

The description names the domain ("BLE Opaque Binary Device", "generated BLE device CLI") but offers only the single generic action "Control" — matching the anchor 'Names the domain but actions are minimal or generic' (e.g., 'Processes PDF files'). It does not list 1-2 concrete actions like inspecting capabilities, checking status, or scanning for devices, so it does not reach anchor 3.

2 / 5

Completeness

The 'what' is clear ("Control BLE Opaque Binary Device through the generated BLE device CLI") but there is no 'when' — no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It is not anchor 4 because the when-clause is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Relevant keywords are present ("BLE", "Device", "CLI"), but common variations and synonyms are missing — no "Bluetooth", "Bluetooth Low Energy", or connect/pair phrasing a user might naturally say. This fits 'Some relevant keywords but missing common variations or synonyms' rather than anchor 4's good coverage.

3 / 5

Distinctiveness Conflict Risk

The uniquely named device and CLI give it a clear niche with minimal conflict risk against unrelated skills, fitting 'Mostly distinct; minor overlap risk.' It falls short of anchor 5 because there are no distinct trigger phrases and it could overlap with sibling skills in the same generated BLE CLI family.

4 / 5

Total

12

/

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-opaque/ble-opaque-binary/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.