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
extractors-and-featuresChoose LightGlue-supported feature extractors and validate feature dictionaries before matching.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when the task is to choose, configure, or sanity-check LightGlue-compatible local feature extractors, or when a user brings precomputed keypoints/descriptors and needs to format them for matching.
scales/oris rules in references/feature-schema.md.match_pair, visualization of matches, and extracting matched coordinates route to ../image-pair-matching/SKILL.md.LightGlue thresholds, adaptivity, filter_threshold, depth_confidence, width_confidence, FlashAttention, torch.compile, and raw matcher output interpretation route to ../matcher-configuration/SKILL.md.SuperPoint, DISK, ALIKED, SIFT, DoGHardNet, LightGlue, and match_pair.superpoint, disk, aliked, sift, doghardnet, plus raco-aliked for compatible 128-D precomputed features.SuperPoint, DISK, ALIKED, DoGHardNet, and feature-specific LightGlue matchers may download pretrained weights on first use. The default SIFT extractor path is the offline-safe choice when OpenCV exposes SIFT.SIFT and DoGHardNet features require scales and oris in addition to keypoints, descriptors, and image_size when used with their pretrained matcher presets.from lightglue import SIFT
from lightglue.utils import load_image
image = load_image("image.jpg")
extractor = SIFT(max_num_keypoints=1024).eval()
features = extractor.extract(image, resize=1024)
print(features.keys()) # keypoints, descriptors, image_size, scales, oris, usually keypoint_scores
For precomputed descriptors, validate the exact schema in references/feature-schema.md before calling any matcher.