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

93%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

An unusually rigorous operational reference: concrete commands, exact tool parameters, and validation-heavy workflows with explicit error-recovery loops for batch uploads. Its main costs are a few overly dense paragraphs and heavy inline reference tables that could be split out.

DimensionReasoningScore

Conciseness

Dense tables and terse, non-obvious platform rules (limits, dedup IDs, screening behavior) with no explanation of concepts Claude already knows, but a few overloaded paragraphs — e.g., the single-paragraph upload-status rules covering videoIds caps, failedChunks, and search caveats — could be tightened or split. Efficient overall with minor trimming opportunities, matching the 4 anchor rather than the every-token-earns-its-place 5.

4 / 5

Actionability

Copy-paste ready commands (`roboflow import -w <workspace> -p <project-id> /path/to/dataset`, `project.version(1).download("yolov8")`) plus exact MCP tool names, parameters (`images_search(project_id, media_types=["video"])`), size limits, polling states, and concrete error strings fully specify the common upload, search, and versioning cases.

5 / 5

Workflow Clarity

Multi-step flows are explicitly sequenced with validation checkpoints and feedback loops: the 5-step version pipeline, "poll `image_upload_status` until it is `completed` or `failed`", inspecting `uploadErrors`/`annotationErrors` even on success, polling every returned videoId, and the failed-chunk retry guidance with expected duplicate-annotation errors. The batch-operation cap does not apply because validation is thorough.

5 / 5

Progressive Disclosure

Sections are well organized and labeling/cloud-storage detail is appropriately offloaded via clearly signaled one-level-deep `skill://` links in a Related Pages section (no bundle files exist alongside this SKILL.md to nest). However, a substantial amount of tabular reference material (augmentation, preprocessing, RoboQL filter tables) is inlined in a ~270-line body, leaving minor organization gaps versus the cleanly split 5 anchor.

4 / 5

Total

18

/

20

Passed

Description

95%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 strong description that merges explicit trigger guidance with concrete capability listing and clear product-specific distinctiveness. The only weakness is that some listed items (tags, splits, versions) are objects rather than stated actions.

DimensionReasoningScore

Specificity

Concrete verb phrases like "uploading images or videos, labeling, organizing datasets, creating Roboflow projects" name the domain and several specific actions, but trailing items "tags, splits, versions" are bare nouns without actions, leaving a minor gap versus the comprehensive all-verb-phrase anchor.

4 / 5

Completeness

The explicit "Use when…" clause answers when with concrete triggers, while the gerunds ("uploading…, labeling…, creating…") explicitly state what the skill does; both are clearly and concretely present, not merely implied as in the 4 anchor.

5 / 5

Trigger Term Quality

Comprehensive natural terms users would actually say — "uploading images or videos", "labeling", "organizing datasets" — plus type variations ("detection/segmentation/keypoint/classification") and product-specific "RoboQL search", matching the synonym-and-variation coverage of the top anchor.

5 / 5

Distinctiveness Conflict Risk

"Roboflow projects", "RoboQL", and the project-type variations pin a clear niche with distinct triggers and minimal conflict risk against generic data or file skills.

5 / 5

Total

19

/

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

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