CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

camera-provider-tapo

TP-Link Tapo camera integration — RTSP streaming and ONVIF

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/camera-providers/tapo/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 exemplary in conciseness and reasonably well-structured, but it only covers environment setup and omits any workflow for actually using the declared capabilities, leaving actionability and workflow clarity incomplete.

Suggestions

Add a short usage section showing how to invoke the capabilities (e.g., running scripts/feed.py, discover.py, stream.py) with concrete commands.

Document the event/command protocol the scripts use (stdin JSON commands, emitted JSON events) so Claude knows how to drive them.

Reconcile the bundle: frontmatter references scripts/discover.py and scripts/stream.py and a requirements.txt that are absent from the bundle.

DimensionReasoningScore

Conciseness

The body is lean and efficient with zero concept over-explanation or padding — a one-line description and an executable setup block — so every token earns its place, matching the 'lean and efficient; assumes Claude's competence' anchor.

5 / 5

Actionability

It gives a concrete, executable setup command ('python3 -m venv ... && pip install -r requirements.txt') but no guidance on actually invoking the three capabilities, leaving key usage details missing; this fits 'some concrete guidance but incomplete'.

3 / 5

Workflow Clarity

Only a single setup step is sequenced with no usage workflow, capability invocation steps, or validation checkpoints, matching 'steps listed but validation gaps; checkpoints missing'; it is not a 2 because a concrete sequenced step is present.

3 / 5

Progressive Disclosure

At under 50 lines with well-organized sections and no nested references, structure is good and content is appropriately placed; it is not a 5 because the body does not clearly surface or navigate to the declared capabilities.

4 / 5

Total

15

/

20

Passed

Description

53%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 is concise and names a clear, specific niche with two concrete capabilities, but it omits any 'Use when...' trigger guidance, capping completeness and trigger quality. It is distinct yet too terse to fully guide when Claude should invoke it.

Suggestions

Add an explicit 'Use when...' clause naming user trigger phrases (e.g., 'Use when working with TP-Link Tapo cameras, RTSP streaming, or ONVIF discovery').

Broaden trigger terms with natural synonyms users say ('Tapo cam', 'RTSP stream', 'ONVIF camera discovery', model numbers).

Expand the capability list slightly to be more comprehensive (streaming, discovery, live preview) rather than just two protocols.

DimensionReasoningScore

Specificity

Names the domain ('TP-Link Tapo camera integration') and two concrete technical capabilities ('RTSP streaming and ONVIF'), matching the '1-2 concrete actions, not comprehensive' anchor; it does not list several actions so it is not a 4.

3 / 5

Completeness

It clearly states what the skill does but provides no 'Use when...' or equivalent explicit trigger guidance for when Claude should use it; per the guidelines a missing 'when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Natural terms a user would say are present ('TP-Link Tapo camera', 'RTSP streaming', 'ONVIF'), but coverage lacks common synonyms or variations, fitting the 'some relevant keywords but missing variations' anchor rather than a 4.

3 / 5

Distinctiveness Conflict Risk

The narrow, brand-specific niche ('TP-Link Tapo camera', 'RTSP', 'ONVIF') is clearly distinct with only minor overlap risk against other camera skills; it is not a 5 because the terse description lacks comprehensive distinct triggers.

4 / 5

Total

13

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

SharpAI/DeepCamera

Path

skills/camera-providers/tapo/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.