CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

annotation-data

Dataset annotation management — COCO labels, sequences, export, and Kaggle upload

Quality

74%

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

Quality

Content

80%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 compact, well-structured protocol spec with concrete JSONL message examples and no padding. Its main weakness is the absence of any validation/verification guidance for the destructive and batch operations it exposes, which caps workflow clarity.

DimensionReasoningScore

Conciseness

The body is lean — a one-line summary plus compact JSONL message examples with no padding or explanation of concepts Claude already knows — matching the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

Concrete JSONL examples for each command (e.g. '{"command": "export_coco", "dataset": "my_dataset", "request_id": "req_007"}') give mostly executable, copy-paste-ready message formats; not a 5 only because payload arrays use '[...]' placeholders rather than complete concrete payloads.

4 / 5

Workflow Clarity

The content is a message-protocol reference rather than a sequenced workflow, and destructive/batch commands like 'delete_dataset' and 'save_dataset' appear without any validation or verification checkpoints, so per the rubric's destructive-operations cap workflow_clarity cannot exceed 3.

3 / 5

Progressive Disclosure

At ~28 body lines with clear section headers (## Protocol, ### Aegis → Skill, ### Skill → Aegis) and no nested external references, this fits the simple-skill exception where well-organized sections earn a 5 without external file references.

5 / 5

Total

17

/

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 gives a concrete, domain-specific 'what' with several named actions but omits any explicit 'when to use' trigger guidance, which caps completeness. Trigger-term coverage is decent but lacks synonyms and file extensions.

Suggestions

Add an explicit 'Use when ...' clause naming natural trigger phrases (e.g. 'Use when managing annotation datasets, exporting COCO-format labels, or uploading datasets to Kaggle').

Include synonyms and file extensions in the description (e.g. '.json', 'COCO format', 'label files') to broaden trigger-term coverage.

Rephrase 'sequences' more concretely (e.g. 'image-sequence annotation') to sharpen specificity and distinctiveness.

DimensionReasoningScore

Specificity

Quotes 'COCO labels, sequences, export, and Kaggle upload' list four concrete actions within the dataset-annotation domain, matching the 'lists several specific actions; minor gaps' anchor; not a 5 because 'sequences' is somewhat generic and coverage of the full CRUD lifecycle implied by the body is not all surfaced here.

4 / 5

Completeness

A clear 'what' is present ('Dataset annotation management — COCO labels, sequences, export, and Kaggle upload') but there is no 'Use when...' or equivalent trigger guidance, so per the rubric a missing explicit 'when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Terms like 'COCO labels', 'export', and 'Kaggle upload' are relevant to the niche but missing common synonyms or file extensions (e.g. .json, COCO format), fitting the 'some relevant keywords but missing common variations' anchor rather than 4's broader coverage.

3 / 5

Distinctiveness Conflict Risk

The annotation/COCO/Kaggle niche is specific and mostly distinct with minor overlap risk against general dataset skills; not a 5 because the trigger phrasing is not distinctive enough to fully rule out overlap with related data-export skills.

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-management/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.