CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dataset-annotation

AI-assisted dataset annotation with COCO export — bbox, SAM2, DINOv3 methods

Quality

67%

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/annotation/dataset-annotation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 concise and well-structured with a concrete I/O protocol and executable setup, but the actual annotation mechanics stay abstract and the batch workflow lacks validation checkpoints.

Suggestions

Add an explicit validation checkpoint to the Annotation Loop (e.g., verify bbox/mask validity and COCO schema before emitting 'dataset_saved', with a fix-and-retry loop on failure) to lift workflow clarity above 3.

Reference the bundled script inline (e.g., 'Annotation logic: see scripts/annotate.py') or include a minimal executable snippet showing how one frame is annotated, so the core action is concrete rather than bullet-described.

Tighten the opening paragraph to avoid restating the frontmatter description, which would push conciseness toward a 5.

DimensionReasoningScore

Conciseness

The body is lean and sectioned with no over-explanation of concepts Claude already knows; the only minor trim is the opening line, which restates the frontmatter description.

4 / 5

Actionability

Concrete, copy-pasteable JSONL protocol examples and an executable setup block are present, but the core annotation operations are described as bullets ('draw bounding boxes, AI auto-suggests') rather than executable code, and the bundled annotate.py is never shown or referenced in the body.

3 / 5

Workflow Clarity

A clear 5-step Annotation Loop sequence is given, but it has no validation or verification checkpoint for what is a batch dataset operation, which per the guidelines caps workflow clarity at 3.

3 / 5

Progressive Disclosure

At under 50 lines the content is well-organized into clearly signaled sections; the one gap is that the existing bundle script scripts/annotate.py is wired only in frontmatter and is not pointed to from the body.

4 / 5

Total

14

/

20

Passed

Description

58%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 specific and distinct, naming concrete annotation methods and the COCO export target, but it omits any explicit 'when to use' trigger guidance, which limits its completeness and trigger quality.

Suggestions

Add a 'Use when ...' clause naming natural triggers (e.g., 'Use when annotating images or video frames for detection datasets, exporting COCO/YOLO, or when the user mentions bounding boxes, segmentation masks, or image labeling').

Soften model jargon by pairing 'SAM2'/'DINOv3' with user-facing synonyms ('click-to-segment masks', 'visual grounding / find-similar-objects').

Consider spelling out the concrete actions per method ('draw bounding boxes', 'click to segment into masks', 'click a patch to find similar objects') to lift specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the domain (dataset annotation) plus several concrete methods — 'COCO export', 'bbox, SAM2, DINOv3 methods' — giving multiple specific actions, though the per-method operations themselves are named by method rather than spelled out.

4 / 5

Completeness

The description gives a clear 'what' but no 'when'/Use-when clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

'dataset annotation', 'COCO export', and 'bbox' are natural user terms, but 'SAM2'/'DINOv3' are model-specific jargon and common synonyms like 'image labeling' or 'bounding boxes' are missing.

3 / 5

Distinctiveness Conflict Risk

The combination of annotation plus COCO export plus SAM2/DINOv3 methods carves a clear niche with minor overlap risk, though the lack of explicit trigger phrases keeps it just below a 5.

4 / 5

Total

14

/

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/annotation/dataset-annotation/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.