Individual skill
data-labeling
Design annotation pipelines that produce reliable training labels — guidelines, agreement measurement, and quality control.
skills/data-labeling/SKILL.md
Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 8, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 56
- Repository last updated
- Oct 10, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- ai-agents-automation Repository topic
- ai-skills Repository topic
- awesome Repository topic
- awesome-list Repository topic
- chatgpt Repository topic
- claude-skills Repository topic
- meta-ai Repository topic
- muse-ai Repository topic
- design Derived category
- data Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 6,607 bytes
Read excerpt
## Overview
Data labeling turns raw examples into training signal: class labels, preference
rankings, bounding boxes, span annotations, or structured judgments. The
uncomfortable truth of the field is that model quality is bounded by label quality
— a state-of-the-art architecture trained on noisy labels underperforms a simpler
model trained on clean ones. Professional labeling is not "pay people to click";
it's a measurement operation with guidelines as the spec, agreement metrics as the
QC, and adjudication as the error correction.
The pipeline has four parts: task design (what exactly is being labeled and what
the edge cases are), guidelines (the written contract between you and annotators),
the labeling pass itself (with redundancy for measurement), and quality control
(agreement metrics, gold questions, adjudication). Whether annotators are in-house