cvat-pull
Skill8 starsChanged 8 months agoMITView on GitHub
Pull human-corrected annotations from CVAT into local YOLO dataset for training.
- Reads credentials
In this repository15 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- active-learningSkill
- analyze-resultsSkill
- annotateSkill
- auto-experimentSkill
- benchmarkSkill
- compare-modelsSkill
- cvat-deploySkill
- cvat-pushSkill
- explain-resultsSkill
- monitor-trainingSkill
- review-annotationsSkill
- review-datasetSkill
- setup-projectSkill
- training-loopSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Ask the user which CVAT task or project to pull
- Distinctive: line 38
If the user already has a local dataset:
- Distinctive: line 40
Check for new images vs corrections
- Distinctive: line 65
NEVER overwrite an existing dataset directory without user confirmation
- Distinctive: line 66
ALWAYS run yolo-validate after pulling
- Distinctive: line 68
If merge is needed, show the user what will change before executing
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Pull CVAT Annotations
Pull human-corrected annotations from CVAT into your local dataset.
Pre-Flight Checklist
yolo-project.yamlhascvat:section with url and project_idCVAT_ACCESS_TOKENenv var is set- CVAT instance is reachable (default: http://localhost:8080)
Workflow
1. Identify What to Pull
- Ask the user which CVAT task or project to pull
- Or read the default
project_idfromyolo-project.yaml
2. Pull Annotations
yolo-cvat pull --task <TASK_ID>
# or
yolo-cvat pull --project <PROJECT_ID>3. Validate the Downloaded Dataset
yolo-validate <output_path>Check for:
- Valid data.yaml with correct class names
- Image/label count matches expectations
- No annotation errors
4. Compare with Existing Dataset
If the user already has a local dataset:
- Compare class distributions
- Check for new images vs corrections
- Suggest merge strategy if combining
5. Merge if Needed
yolo-merge --sources <existing_labels> <pulled_labels> --output <merged>Decision Tree
Has existing local dataset?
├── Yes → Compare distributions → Suggest yolo-merge
└── No → Set as primary dataset
Validation warnings found?
├── Yes → Flag issues, ask before training
└── No → Ready to train
Class distribution changed?
├── Significantly → Warn user, may affect model balance
└── Minor → Proceed normallyGuardrails
- NEVER overwrite an existing dataset directory without user confirmation
- ALWAYS run yolo-validate after pulling
- Report class distribution changes clearly
- If merge is needed, show the user what will change before executing
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

