executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
conversionConvert common annotation and detector-output formats into mAP evaluator text files.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when the user needs annotation or detector-output files transformed into the evaluator's required per-image text files before running mAP/AP evaluation.
ground-truth/*.txt rows.ground-truth/*.txt rows using a class list and image dimensions.detection-results/*.txt rows.result.txt detector output to detection-results/*.txt rows.evaluation sub-skill.data-validation sub-skill.| User request | Route |
|---|---|
| "Convert VOC XML annotations" | voc-xml-gt workflow in references/workflows.md. |
| "Convert YOLO labels for ground truth" | yolo-gt workflow; require class list plus image dimensions. |
| "Convert darkflow JSON detections" | darkflow-json-dr workflow. |
| "Convert darknet result.txt" | darknet-result-dr workflow. |
| "Convert keras-yolo3 annotations" | keras-yolo3 --gt or keras-yolo3 --dr; choose flat or recursive output layout. |
Successful conversion produces evaluator-ready .txt files in an explicit output directory. Each output file represents one image. Ground-truth and detection-result files should later have matching basenames before evaluation; checking and repairing that intersection belongs to data-validation.