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
operation-referenceChoose and configure Augmentor operations, validation ranges, and custom Operation subclasses.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when a task is about selecting image augmentation operations, setting operation parameters, recovering from operation validation errors, or adding a custom Augmentor.Operations.Operation subclass to a pipeline.
references/api-reference.md.references/operation-selection.md.references/troubleshooting.md.scripts/augmentor_operation_probe.py in an environment where Augmentor, Pillow, and NumPy are installed.Augmentor.Pipeline before sampling or processing; operation order is the execution order.0 < probability <= 1. A probability of 1 is the normal choice for deterministic resizing, greyscale conversion, and other required transforms.Operation.perform_operation(images) receives a list of PIL Images and must return a list of PIL Images. This list contract matters for future mask/ground-truth workflows.Pipeline convenience methods for built-in operations. Mention lower-level classes such as HSVShifting and Mixup only as manual Operation classes; they are not top-level Pipeline convenience workflows.sample(), process(), seeding, and multithreading to pipeline-augmentation.masks-and-arrays.generators-and-frameworks.