Skip to content
Back to skills

Data Labeling And Training Datasets

ASecurity

"Frame extraction, label checks, training dataset and shuffle

  • 247 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 8, 2026
dataapi

Works with

  • api

Security analysis

A100/100

Pro scans all 5 files and shows the line behind each finding

Scanned September 8, 2026

npx -y skills add VectorSpaceLab/AREX-Skill --skill data-labeling-and-training-datasets --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Data Labeling And Training Datasets?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Data Labeling And Training Datasets
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/vectorspacelab-data-labeling-and-training-datasets/badge)](https://www.skillsdirectory.com/skills/vectorspacelab-data-labeling-and-training-datasets)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: data-labeling-and-training-datasets
description: "Frame extraction, label checks, training dataset and shuffle
  creation, data conversion, and tiny DeepLabCut-style fixtures."
disable-model-invocation: true
metadata:
  disco-role: operating
license: LGPL 3.0
---

# Data Labeling And Training Datasets

Use this sub-skill when the current DeepLabCut task is about turning project videos and annotations into valid DeepLabCut labeled-data and training-dataset artifacts.

## Covers

- Extracting frames with `deeplabcut.extract_frames` for existing projects.
- Checking labels with `deeplabcut.check_labels` after GUI labeling, external import, or conversion.
- Understanding and repairing DeepLabCut `labeled-data/` annotation tables for standard and multi-animal projects.
- Creating shuffles and train/test splits with `create_training_dataset`, `create_training_dataset_from_existing_split`, `create_training_model_comparison`, and `mergeandsplit`.
- Converting annotation files with `convertcsv2h5` and converting older single-animal labels into maDLC-style labels with `convert2_maDLC`.
- Creating tiny safe standard or multi-animal fixture projects with the bundled script.

## Route elsewhere

- New-project creation, installation, package imports, environment preparation, and initial `config.yaml` project setup: use `install-and-project-setup`.
- Training, evaluation, model selection for real training runs, inference, analyzing videos, and exported model runtime: use `pytorch-training-evaluation-inference`.
- Tracklet conversion, stitching, identity tracking, and multi-animal temporal assembly after inference: use `multi-animal-tracking`.
- Filtering predictions, outlier-frame refinement, 3D workflows, labeled-video export, trajectory plots, and other post-prediction outputs: use `postprocessing-3d-video-exports`.

## Read in order

1. [Data formats](references/data-formats.md) for the exact folder/table layouts and trainset metadata expected by DeepLabCut.
2. [Workflows](references/workflows.md) for API sequences, safe arguments, and boundary decisions.
3. [Troubleshooting](references/troubleshooting.md) when labels are not found, shuffles collide, CSV/HDF conversion fails, or multi-animal columns are malformed.
4. [Tiny fixture script](scripts/create_tiny_dlc_project.py) when a small local standard or multi-animal project is needed for format or routing checks without GUI, training, downloads, or network access.

## Operating reminders

- Treat `config.yaml` as the authority for scorer, project path, videos, body parts, individuals, training fractions, iteration, and engine.
- Do not start training from this sub-skill. Stop after label validation and dataset/shuffle creation, then route to training/evaluation.
- In non-interactive automation, avoid prompts by setting `userfeedback=False` only after confirming that the target output may be overwritten or is disposable.
- Keep annotation paths portable: rows should identify images under `labeled-data/<video-stem>/...`, and the project path in `config.yaml` should point at the project root on the machine where the operation is being run.

Files in this skill

  • SKILL.md3.1 KB
  • references/data-formats.md8.1 KB
  • references/troubleshooting.md9.8 KB
  • references/workflows.md10.5 KB
  • scripts/create_tiny_dlc_project.py17.3 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.