Skip to content
Back to skills

Segmentation

ASecurity

"Use this YOLOv5 sub-skill for instance-segmentation training,

  • 247 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 9, 2026
devopsgoflask

Security analysis

A100/100

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

Scanned September 9, 2026

npx -y skills add VectorSpaceLab/AREX-Skill --skill segmentation --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Segmentation?

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

Security grade badge for Segmentation
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/vectorspacelab-segmentation-4785c449/badge)](https://www.skillsdirectory.com/skills/vectorspacelab-segmentation-4785c449)

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: segmentation
description: "Use this YOLOv5 sub-skill for instance-segmentation training,
  validation, prediction, mask data, segmentation checkpoints, and mask
  troubleshooting."
disable-model-invocation: true
metadata:
  disco-role: operating
license: AGPL 3.0
---

# YOLOv5 Segmentation

Use this route for YOLOv5 instance segmentation workflows involving `segment/predict.py`, `segment/train.py`, `segment/val.py`, `*-seg.pt` checkpoints, segmentation YAMLs, polygon labels, masks, or mask-specific failures.

## Choose the workflow

- **Predict masks**: read `references/workflows.md` for segmentation prediction command shapes, `--retina-masks`, output directories, and source handling. Use `scripts/plan_segmentation_command.py` before running commands.
- **Train masks**: use the training section for `coco128-seg.yaml`, custom segmentation labels, pretrained vs scratch segmentation configs, DDP, and output planning.
- **Validate masks**: use the validation section for mask metrics, `--overlap`, `--mask-ratio`, confidence/IoU, and exported-format validation handoff.
- **Data formats**: read `references/data-formats.md` before converting detection labels or assuming a dataset is segmentation-ready.

## Common decisions

- Use segmentation checkpoints such as `yolov5s-seg.pt`; do not use plain detection checkpoints for mask workflows unless the task explicitly builds a new segmentation model.
- Use `models/segment/yolov5*-seg.yaml` when training from scratch.
- Treat full COCO segments as large; prefer `coco128-seg.yaml` or a tiny local fixture for smoke work.
- Keep `--project` and `--name` explicit because prediction/training/validation write run artifacts.
- Use CPU for parser/import checks and CUDA for realistic training or high-resolution prediction.

## Handoffs

- Read root `references/datasets-and-weights.md` for segmentation checkpoint names and dataset download risks.
- Route detection-only boxes to `../detection/SKILL.md` and classification to `../classification/SKILL.md`.
- Route export/deployment formats for a segmentation checkpoint to `../export/SKILL.md`.
- Route Flask serving to `../serving/SKILL.md` only if the service itself is the user's task.

Files in this skill

  • SKILL.md2.2 KB
  • references/data-formats.md1.9 KB
  • references/troubleshooting.md1.5 KB
  • references/workflows.md2.5 KB
  • scripts/plan_segmentation_command.py3.2 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.