Hygiene patterns for any OpenCV + dlib vision pipeline: camera index probing + macOS init quirks, warmup that verifies real frames, frame-skip policy for expensive inference.
96
93%
Does it follow best practices?
Impact
100%
1.36xAverage score across 6 eval scenarios
Passed
No known issues
{
"context": "Tests plugin-specific knowledge for multi-camera kiosk deployment on macOS: the critical constraint that only one process can hold the camera, the capture_to_disk pattern where the parent captures and workers read from disk, and the DJI Osmo resolution constraint. Baseline agents try to open cameras in worker subprocesses and fail.",
"type": "weighted_checklist",
"checklist": [
{
"name": "No VideoCapture in subprocess workers",
"description": "Worker functions (any code running in multiprocessing Pool, Process, or subprocess) do NOT call cv2.VideoCapture(). Only the parent process opens the camera. This is the key macOS constraint — one process holds the camera.",
"max_score": 30
},
{
"name": "capture_to_disk pattern",
"description": "Uses the capture_to_disk pattern: the parent process captures frames and writes them to disk, worker processes read frame files from disk for processing. Either via the capture_to_disk() helper or equivalent custom implementation.",
"max_score": 25
},
{
"name": "Comment explains single-process camera constraint",
"description": "An inline comment or docstring explains WHY workers read from disk instead of opening the camera: macOS restricts camera access to a single process. The knowledge of this constraint is what the plugin teaches.",
"max_score": 20
},
{
"name": "No cap.set resolution on DJI Osmo",
"description": "Script does NOT call cap.set(cv2.CAP_PROP_FRAME_WIDTH) or cap.set(cv2.CAP_PROP_FRAME_HEIGHT) anywhere. On DJI Osmo cameras, setting resolution resets the zoom and causes erratic behavior.",
"max_score": 25
}
]
}