Acerca de
Esta habilidad configura flujos de trabajo sistemáticos de etiquetado de datos utilizando herramientas como Label Studio, incluyendo control de calidad y concordancia interanotadores. Ayuda a integrar datos etiquetados en pipelines de aprendizaje automático para texto, imágenes, audio o video cuando se inicia un aprendizaje supervisado o cuando el rendimiento del modelo está limitado por etiquetas insuficientes. También soporta aprendizaje activo para priorizar ejemplos valiosos para etiquetar.
Instalación rápida
Claude Code
Recomendadonpx skills add pjt222/agent-almanac -a claude-code/plugin add https://github.com/pjt222/agent-almanacgit clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/label-training-dataCopia y pega este comando en Claude Code para instalar esta habilidad
Documentación
Label Training Data
See Extended Examples for complete config files + templates.
Systematically label data for supervised ML w/ QC + efficient workflows.
Use When
- Start supervised ML needing labeled data
- Model perf limited by insufficient examples
- Label text, images, audio, video
- Measure + improve annotation quality
- Team of annotators w/ diff expertise
- Active learning → prioritize valuable examples
- Track progress + costs
- Consistent labels across multi annotators
In
- Req: Unlabeled dataset (images, text, audio, video)
- Req: Label schema (classes, attributes, annotation types)
- Req: Labeling guidelines doc
- Opt: Pre-existing labels (quality compare)
- Opt: Model predictions for pre-annotation
- Opt: Budget + timeline
- Opt: Domain expert availability
Do
Step 1: Install + Config Label Studio
Setup labeling platform.
# Install Label Studio
pip install label-studio
# Or use Docker for production
docker pull heartexlabs/label-studio:latest
# Create project directory
mkdir -p labeling-project/{data,exports,config}
cd labeling-project
# Initialize Label Studio
label-studio init my_project
# Start Label Studio server
label-studio start my_project --port 8080
Access http://localhost:8080 (default creds: create on first visit).
Prod deploy w/ Docker:
# docker-compose.yml
version: '3.8'
services:
label-studio:
image: heartexlabs/label-studio:latest
ports:
- "8080:8080"
# ... (see EXAMPLES.md)
docker-compose up -d
→ Label Studio running + accessible, PostgreSQL DB init for prod.
If err: Port 8080 busy → change port in config. Docker fails → check daemon running. Ensure disk space for data vols. Firewall allows 8080.
Step 2: Design Interface + Schema
Create labeling config for task type.
# labeling-project/config/labeling_config.py
"""
Label Studio configuration templates for common tasks.
"""
# Text Classification (single label)
TEXT_CLASSIFICATION = """
<View>
# ... (see EXAMPLES.md)
→ Interface configured w/ appropriate controls for task type, data imported, interface accessible to annotators.
If err: Validate XML config w/ Label Studio validator. Check data file format (JSON / CSV). Ensure image/audio URLs accessible if external storage. Verify API key perms.
Step 3: Prepare Data + Sampling Strategy
Format data for import + prioritize for labeling.
# labeling-project/prepare_data.py
import pandas as pd
import json
import random
from typing import List, Dict
from sklearn.cluster import KMeans
import numpy as np
# ... (see EXAMPLES.md)
→ Data formatted for Label Studio import, sampling prioritizes informative examples, tasks include metadata for tracking.
If err: Verify JSON w/ jq / Py json.load(). Check URLs accessible if remote images. Ensure no special chars break JSON. Validate column names match config.
Step 4: QC + IAA Measurement
Setup processes to measure + improve quality.
# labeling-project/quality_control.py
import pandas as pd
import numpy as np
from sklearn.metrics import cohen_kappa_score, confusion_matrix
from typing import Dict, List, Tuple
import logging
logging.basicConfig(level=logging.INFO)
# ... (see EXAMPLES.md)
→ IAA measured (Cohen's Kappa > 0.6 = moderate, >0.8 = good), difficult tasks ID'd for review, annotator perf tracked.
If err: Kappa very low (<0.4) → review guidelines for clarity, retrain annotators, simplify schema, check ambiguous examples, consider expert annotators for gold std.
Step 5: Export + Integrate Labeled Data
Export labels + prep for ML training.
# labeling-project/export_labels.py
import requests
import pandas as pd
import json
from typing import List, Dict
import logging
logger = logging.getLogger(__name__)
# ... (see EXAMPLES.md)
→ Annotations exported training-ready format, label distribution balanced / documented, data quality validated before training.
If err: Verify API key perms. Check export format compat w/ ML framework. Handle missing annotations gracefully. Validate JSON matches expected.
Step 6: Continuous Labeling Pipeline
Automate workflow w/ active learning.
# labeling-project/active_learning_pipeline.py
import schedule
import time
import logging
from datetime import datetime
from prepare_data import DataSampler, prepare_label_studio_format
from export_labels import LabelStudioExporter, convert_to_training_format
import pandas as pd
# ... (see EXAMPLES.md)
→ Active learning selects informative examples auto, batches prep weekly, model retrained when sufficient new labels avail.
If err: Uncertainty sampling doesn't improve model → try diversity sampling. Annotators can't keep up → reduce batch size. Monitor queue length, backpressure if queue grows.
Check
- Label Studio accessible + responsive
- Interface intuitive (test w/ sample annotator)
- Data import successful w/ correct format
- IAA (Cohen's Kappa) > 0.6
- QC IDs problematic tasks
- Labels export training-ready
- Distribution matches expected (or intentionally imbalanced)
- Active learning pipeline runs w/o manual intervention
- Throughput meets timeline
Traps
- Unclear guidelines: Ambiguous → inconsistent labels. Invest detailed guidelines + examples.
- Insufficient overlap: Can't measure IAA w/o multi annotators per task. 10-20% overlap.
- Ignore difficult cases: Edge cases often skipped, critical for robustness. Flag for expert review.
- Batch effects: Annotator fatigue / learning → temporal inconsistency. Randomize task order.
- No quality feedback: Annotators don't improve w/o feedback. Regular accuracy reports.
- Wrong sampling: Random wastes budget on easy. Use uncertainty / diversity sampling.
- Labeling in isolation: Domain experts needed for complex tasks. Pair novices w/ experts initially.
- Not tracking costs: Labeling expensive. Monitor time per task + budget consumption.
→
version-ml-data— version control for labeled datasetstrack-ml-experiments— track model perf as labels added
Repositorio GitHub
Frequently asked questions
What is the label-training-data skill?
label-training-data is a Claude Skill by pjt222. Skills package instructions and resources that Claude loads on demand, so Claude can perform label-training-data-related tasks without extra prompting.
How do I install label-training-data?
Use the install commands on this page: add label-training-data to Claude Code as a plugin, or clone its repository into your skills directory, then restart Claude so it picks up the skill.
What category does label-training-data belong to?
label-training-data is in the Design category, tagged ai and data.
Is label-training-data free to use?
Yes. label-training-data is listed on AIMCP and free to install. It runs inside Claude, so no separate service account is required to use the skill itself.
Habilidades relacionadas
Utilice la habilidad executing-plans cuando tenga un plan de implementación completo para ejecutar en lotes controlados con puntos de revisión. Esta habilidad carga y revisa críticamente el plan, luego ejecuta tareas en pequeños lotes (por defecto 3 tareas) mientras reporta el progreso entre cada lote para la revisión del arquitecto. Esto asegura una implementación sistemática con puntos de control de calidad integrados.
Esta habilidad despacha un subagente revisor de código para analizar los cambios en el código frente a los requisitos antes de proceder. Debe usarse después de completar tareas, implementar funciones principales o antes de fusionar con la rama principal. La revisión ayuda a detectar problemas de forma temprana al comparar la implementación actual con el plan original.
Esta habilidad proporciona una guía integral para que los desarrolladores conecten servidores MCP a Claude Code mediante transportes HTTP, stdio o SSE. Cubre la instalación, configuración, autenticación y seguridad para integrar servicios externos como GitHub, Notion y APIs personalizadas. Úsala al configurar integraciones MCP, al configurar herramientas externas o al trabajar con el Protocolo de Contexto del Modelo de Claude.
Esta habilidad ayuda a los desarrolladores a elegir entre las interfaces web y CLI de Claude Code mediante el análisis de tareas, y luego permite la teletransportación fluida de sesiones entre estos entornos. Optimiza el flujo de trabajo gestionando el estado y el contexto de la sesión al cambiar entre web, CLI o móvil. Úsala para proyectos complejos que requieren diferentes herramientas en varias etapas.
