CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ble-temperature-sensor

Control BLE Temperature Sensor 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/ble-temperature-sensor/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 provides a well-validated, executable install/verification workflow with good error-recovery guidance, and it stays lean. Its main weaknesses are the absence of any example of the primary device-control operation and a final paragraph that bundles five distinct topics without section structure.

Suggestions

Add a short usage example showing the primary operation, e.g. the actual command to read temperature from the sensor (replay and live variants), since the skill's stated purpose is controlling the device.

Split the closing paragraph into sections such as '## Inspecting capabilities' and '## Live device control' so commands are discoverable instead of buried in one dense block.

Clarify or trim the conditional fallback sentence about the public-library category and the session-IPC note, which read as speculative and consume tokens without actionable value.

DimensionReasoningScore

Conciseness

The body is dominated by concrete commands with no explanation of concepts Claude already knows, but contains trimmable edge-case asides ("If the `npx` install fails before this CLI has a public-library category... after publish", "Session IPC scaffolding is generated only when the device spec enables device-session support") and a dense closing paragraph, matching the 'efficient; minor instances of over-explanation' anchor. It is not a 5 because those asides and the run-on final paragraph do not each earn their tokens.

4 / 5

Actionability

Commands are concrete and executable ("npx -y @mvanhorn/printing-press-library install ble-temperature-sensor --cli-only", "ble-temperature-sensor-pp-cli --version", "capabilities --json", "doctor", "scan --live"), but the core operation the skill exists for — actually reading or controlling the temperature sensor — is never shown with a command or example, matching 'missing key details'. It is not a 4 because that gap is central, not minor.

3 / 5

Workflow Clarity

The prerequisites are a numbered sequence with explicit validation ("You must verify the CLI is installed before invoking any command", "Do not proceed with skill commands until verification succeeds") and error-recovery paths for both PATH failure and npx install failure, matching the anchor-4 example. It is not a 5 because no sequenced workflow exists for the actual device-control task (e.g. live-mode setup: doctor → scan → connect → read).

4 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files and no external references needed, so per the simple-skill note it can score on organization alone; however, only one section header exists and capabilities, status, live-mode, doctor, scan, and session-IPC notes are all crammed into a single dense closing paragraph, matching 'good structure; minor organization gaps'. It is not a 5 because that closing paragraph is not well-organized sectioned content.

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 specific, distinctive device niche but is too thin: a single generic verb ("Control") with no concrete capability listing and no 'when to use' guidance. Trigger terms are relevant but lack synonyms, and the missing use-when clause caps its completeness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when reading or controlling a BLE temperature sensor, checking sensor status, or scanning for Bluetooth devices.'

Replace the generic 'Control' with 2-3 concrete actions the CLI performs (e.g. read temperature readings, inspect capabilities, scan for devices, check live readiness).

Include natural synonyms such as 'Bluetooth' and 'BLE' together so users phrasing it either way trigger the skill.

DimensionReasoningScore

Specificity

The description names the domain ("BLE Temperature Sensor", "the generated BLE device CLI") but its only action is the generic "Control" — no concrete operations such as reading temperature, scanning, or connecting are listed, matching the 'names the domain but actions are minimal or generic' anchor rather than the 1-2-concrete-actions anchor at 3.

2 / 5

Completeness

The 'what' is stated (control the sensor through the CLI), but there is no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3. It is not a 2 because the 'what' names a specific device and mechanism rather than being extremely vague.

3 / 5

Trigger Term Quality

"BLE" and "Temperature Sensor" are natural keywords a user might say, but common variations and synonyms ("Bluetooth", "read temperature", "thermometer") are absent, matching the 'some relevant keywords but missing common variations' anchor. It is not a 4 because keyword coverage is thin, and not a 2 because the included terms are genuinely natural rather than generic filler.

3 / 5

Distinctiveness Conflict Risk

"BLE Temperature Sensor" plus "the generated BLE device CLI" defines a clear niche with minimal conflict risk, but the templated 'Control X through the generated BLE device CLI' phrasing could overlap with sibling device-CLI skills and no distinct trigger terms are provided, placing it between the 4 and 5 anchors.

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/ble-temperature-sensor/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.