CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

roboflow-custom-weights-upload

Use when uploading locally trained model weights (YOLO, RF-DETR, YOLO-NAS, PaliGemma, Florence-2) to Roboflow — the client-side Python SDK upload flow, safe API key handling, per-family packaging requirements, and verifying the upload.

Quality

92%

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

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 excellent, highly actionable skill body that concentrates on genuinely non-obvious operational detail with strong validation gates and error-recovery loops. The only weaknesses are mild redundancy around key-scoping, and all content living inline in SKILL.md rather than splitting per-family detail into reference files.

Suggestions

State the deploy-scope caveat once: the preflight section repeats step 2's point that the preflight does not exercise model:deploy — merging these into a single note would trim tokens without losing the warning.

Move the per-family requirements and the size/dependency mismatch recovery detail into a references/ file (e.g. PACKAGING.md) linked from a short summary section, keeping SKILL.md as a lean overview.

DimensionReasoningScore

Conciseness

Nearly all content is non-obvious operational knowledge (SDK version pins, key scoping, the interactive-prompt EOFError behavior), but the deploy-scope caveat is repeated in both step 2 ("the preflight below only confirms the key and the workspace read, not the deploy scope") and the preflight section, and the ".env" sourcing discussion could be tightened — minor over-explanation matching anchor 4 rather than the lean anchor 5.

4 / 5

Actionability

Copy-paste-ready code for both workspace and versioned deploys, an executable preflight snippet, a dotenv loader, exact shell commands (uv venv, pip pins), and a concrete headless workaround ("printf 'y\\n' | python upload.py") cover the common cases, matching the fully-executable anchor 5; the verify step names specific MCP tools and a URL rather than being vague.

5 / 5

Workflow Clarity

The sequence (install → key → confirm destination → preflight → package/upload → verify) has an explicit validation gate ("Only package and upload after all three pass"), batched gap reporting, error-type-based recovery loops for the y/n prompt, and a user-confirmation checkpoint for the hard-to-undo registration — matching the feedback-loop anchor 5.

5 / 5

Progressive Disclosure

Sections are well-organized with no nested references and clear navigation, but the ~185-line body is entirely inline with no bundle files; per-family requirements and the mismatch-recovery detail could be split into reference files, fitting anchor 4's "most content appropriately placed; minor organization gaps" rather than the split-content anchor 5 (and the 50-line simple-skill exception does not apply).

4 / 5

Total

18

/

20

Passed

Description

92%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 with an explicit trigger clause, third-person voice, and a concrete capability list. The only gap is a few missing natural synonyms ("checkpoint", ".pt") that would broaden keyword matching.

DimensionReasoningScore

Specificity

"the client-side Python SDK upload flow, safe API key handling, per-family packaging requirements, and verifying the upload" lists four concrete capabilities with comprehensive coverage of the skill's actions, matching the top anchor rather than the minor-gaps level of 4.

5 / 5

Completeness

The description opens with an explicit "Use when uploading ... to Roboflow" trigger clause and separately enumerates what the skill covers, clearly answering both what and when; the 4 anchor would require a weaker or less explicit when-clause.

5 / 5

Trigger Term Quality

Natural terms like "uploading locally trained model weights", "Roboflow", and all five model family names (YOLO, RF-DETR, YOLO-NAS, PaliGemma, Florence-2) are present, but common synonyms such as "checkpoint" and file extensions like ".pt"/".pth" are missing, which fits anchor 4 rather than the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

The combination of Roboflow plus named model families carves out a clear niche with distinct triggers, making accidental activation of unrelated skills (e.g., generic training or inference skills) unlikely.

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

skills/roboflow-custom-weights-upload/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.