CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

roboflow-data-management

Use when uploading images or videos, labeling, organizing datasets, creating Roboflow projects (detection/segmentation/keypoint/classification), tags, splits, versions, or RoboQL search.

Quality

87%

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

SKILL.md
Quality
Evals
Security

Quality

Content

81%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.

A dense, highly actionable reference with exemplary validation and error-recovery workflows for batch uploads and versioning. Its main weakness is redundancy: the upload-method selection logic is stated three times and several paragraphs could be tightened, and the sheer inlined detail keeps it from being a lean overview with split-out references.

Suggestions

State the upload-method selection logic (host-assisted vs signed-URL vs CLI) once — e.g., in a decision table in the "MCP Image and Video Upload" section — and have the Methods table and "Video Upload" section refer to it instead of restating the conditions.

Break the long video-polling and annotation-group paragraphs into short bulleted rules (poll each videoId, use final videoId, report failed-chunk counts as unverified) so they are scannable rather than run-on prose.

Move the upload edge-case detail (screening verdicts, dedup ID handling, chunk retry semantics) into a reference file like upload-details.md linked from the main body, keeping SKILL.md as a tighter overview.

DimensionReasoningScore

Conciseness

Tables are token-efficient and nearly every sentence carries unique operational facts, but the upload-method selection guidance and signed-URL fallback conditions are repeated across the Methods table, "Video Upload", and "MCP Image and Video Upload" sections, and paragraphs like the video-polling and annotation-group ones are long run-ons that could be tightened.

3 / 5

Actionability

Fully executable guidance throughout: copy-paste CLI and SDK snippets ("roboflow import -w <workspace> -p <project-id> /path/to/dataset", "project.version(1).download(\"yolov8\")"), exact limits ("Max 20 MB per image", "up to 100 files / 1 GB per call"), concrete RoboQL examples ("class:helmet AND NOT (tag:v1 OR tag:v2)"), and specific tool names and status values covering the common cases.

5 / 5

Workflow Clarity

Multi-step batch upload flows carry explicit validation and feedback loops: poll "image_upload_status" until "completed" or "failed", per-video "video_upload_status" polling, a safe chunk-failure retry procedure with expected duplicate errors, screening verdict handling, and a numbered version-creation pipeline; irreversible class changes carry a warning with a non-destructive alternative.

5 / 5

Progressive Disclosure

Clear section organization with a well-signaled, one-level-deep "Related Pages" section (labeling.md, cloud-storage SKILL.md), but at ~250 lines the body reads as a full reference rather than an overview — the upload edge-case deep-dives (screening, dedup IDs, chunk retries) could be split into a reference file.

4 / 5

Total

17

/

20

Passed

Description

87%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.

A concise, well-targeted description with explicit trigger guidance, concrete actions, and strong brand-based distinctiveness. Its only weaknesses are minor coverage gaps (annotations, export) that keep specificity and trigger-term quality just below comprehensive.

DimensionReasoningScore

Specificity

Lists several concrete actions ("uploading images or videos", "labeling", "organizing datasets", "creating Roboflow projects", "RoboQL search") but omits body capabilities like export and analytics, matching anchor 4's minor gaps in coverage rather than comprehensive coverage.

4 / 5

Completeness

"Use when..." provides explicit, concrete trigger guidance while the enumerated activities clearly state what the skill covers, explicitly answering both what and when; the when-clause is specific, not merely implied as at anchor 4.

5 / 5

Trigger Term Quality

Good coverage of natural phrases ("uploading images", "labeling", "tags", "splits", "versions") plus project-type synonyms ("detection/segmentation/keypoint/classification"), but common user terms like "annotate/annotations" and "export/download dataset" are missing.

4 / 5

Distinctiveness Conflict Risk

"Roboflow projects" and "RoboQL" are brand-specific triggers carving a clear computer-vision data-management niche with minimal conflict risk against other skills.

5 / 5

Total

18

/

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

roboflow/computer-vision-skills

Path

skills/roboflow-data-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.