CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

yolo-detection-2026

YOLO 2026 — state-of-the-art real-time object detection

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 ./skills/detection/yolo-detection-2026/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 well-structured, mostly lean and executable overview of the YOLO detection skill with a clear deployment/runtime sequence. Its main weakness is progressive disclosure: it is a single-file monolith with broken or missing references to files that should sit alongside it.

Suggestions

Fix the `env_config.py` reference to point at its real bundle location (e.g. `scripts/env_config.py`) instead of `../../lib/env_config.py`.

Either include `deploy.sh` and the per-backend `requirements_*.txt` files in the bundle or mark the requirements table as generated by deploy.sh so the references are not dangling.

Consider splitting the protocol/spec detail into a short referenced file once the skill grows, keeping SKILL.md as a concise overview with clearly signaled one-level-deep links.

DimensionReasoningScore

Conciseness

The body is lean, table-driven, and assumes competence (no "what is YOLO" filler); only minor stretches like the perf_stats JSONL block and the Apple Silicon callout could be trimmed, fitting the efficient-with-minor-over-explanation anchor.

4 / 5

Actionability

It gives concrete, executable artifacts — the `./deploy.sh` command, full JSONL protocol messages with real fields, and the xyxy bbox format — with only minor gaps (no example detect.py invocation); matches the mostly-executable-with-minor-gaps anchor.

4 / 5

Workflow Clarity

The numbered "How It Works" sequence (detect hardware → install deps → pre-convert → load cached model → fall back to PyTorch) is clearly ordered and includes an error-recovery fallback, fitting the clear-sequence-with-most-checkpoints anchor; not 5 because explicit validation checkpoints are absent.

4 / 5

Progressive Disclosure

Sections are well-organized but everything is inlined into one ~100-line file with no working external references: the `env_config.py` link points to `../../lib/env_config.py` (outside the bundle; the real file is in scripts/), and `deploy.sh`/`requirements_*.txt` are referenced but absent from the bundle, matching the some-structure / references-not-clearly-signaled anchor.

3 / 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 is a concise, distinctive tagline that names the domain but lacks concrete capability detail and any explicit "Use when..." trigger guidance. It reads as marketing copy rather than an activation-oriented skill description.

Suggestions

Add concrete capabilities, e.g. "Detects 80+ COCO object classes and outputs bounding boxes with labels and confidence scores."

Append an explicit trigger clause such as "Use when the user needs real-time object detection, bounding-box localization, or camera-frame analysis."

Include natural trigger synonyms ("object detection", "detect objects", "bounding boxes", "computer vision") so users' phrasings match.

DimensionReasoningScore

Specificity

The description "state-of-the-art real-time object detection" names the domain and one generic action but lists no concrete capabilities (e.g. bounding boxes, class labels, confidence scores), matching the anchor that names the domain with minimal actions.

2 / 5

Completeness

It states a clear "what" (real-time object detection) but has no "Use when..." or equivalent trigger clause, so per the missing-trigger-guidance cap it cannot exceed 3; it matches the "clear what, missing when" anchor.

3 / 5

Trigger Term Quality

"object detection" and "YOLO" are natural terms a user might say, but the description omits common variations/synonyms like "detect objects", "bounding boxes", or "computer vision", fitting the anchor for some relevant keywords with missing variations.

3 / 5

Distinctiveness Conflict Risk

Naming "YOLO 2026" carves a clear niche (real-time object detection) with minimal overlap against unrelated skills, fitting the "mostly distinct, minor overlap risk" anchor; not a 5 because the tagline is too short to fully establish distinct triggers.

4 / 5

Total

12

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

14

/

16

Passed

Repository

SharpAI/DeepCamera

Path

skills/detection/yolo-detection-2026/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.