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
image-pair-matchingMatch two images end-to-end with LightGlue and a selected local-feature extractor.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when you need to match two user-supplied images end-to-end with LightGlue, choose one public extractor head, and save the resulting visualization.
It distills the README minimal script and the demo notebook into a CLI-friendly flow:
load_image(...) to read and normalize RGB tensors,LightGlue(features=...) matching,rbd(...) when you handle the dictionaries manually,matches[..., 0] and matches[..., 1],viz2d saving for the final PNG.Use match_pair(...) when you want the compact helper equivalent; keep the explicit flow here when you need to inspect the intermediate feature/result dicts.
load_image.superpoint, disk, aliked, sift, or doghardnet.rbd when you are handling the dicts yourself.viz2d helpers.SuperPoint, DISK, ALIKED, DoGHardNet, and the feature-specific LightGlue heads may download pretrained weights on first use. SIFT avoids neural extractor downloads, but the SIFT LightGlue head still loads its own weights the first time it runs.
For concrete recipes, start with references/workflows.md and the CLI in scripts/match_image_pair.py.