Skip to content
Back to skills

Image Pair Matching

ASecurity

"Match two images end-to-end with LightGlue and a selected

  • 247 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 8, 2026
documentationperformance

Works with

  • cli

Security analysis

A100/100

Pro scans all 5 files and shows the line behind each finding

Scanned September 8, 2026

npx -y skills add VectorSpaceLab/AREX-Skill --skill image-pair-matching --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Image Pair Matching?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Image Pair Matching
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/vectorspacelab-image-pair-matching/badge)](https://www.skillsdirectory.com/skills/vectorspacelab-image-pair-matching)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: image-pair-matching
description: "Match two images end-to-end with LightGlue and a selected
  local-feature extractor."
disable-model-invocation: true
metadata:
  disco-role: operating
license: Apache 2.0
---

# image-pair-matching

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,
- device placement for the images, extractor, and matcher,
- `LightGlue(features=...)` matching,
- `rbd(...)` when you handle the dictionaries manually,
- coordinate indexing from `matches[..., 0]` and `matches[..., 1]`,
- and `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.

## Owned runtime assets
- [scripts/match_image_pair.py](scripts/match_image_pair.py)
- [references/workflows.md](references/workflows.md)
- [references/data-and-results.md](references/data-and-results.md)
- [references/troubleshooting.md](references/troubleshooting.md)

## Routed elsewhere
- Extractor choice and feature schema: [../extractors-and-features/SKILL.md](../extractors-and-features/SKILL.md)
- LightGlue thresholds and matcher config: [../matcher-configuration/SKILL.md](../matcher-configuration/SKILL.md)
- Broader plotting and benchmark helpers: [../performance-and-visualization/SKILL.md](../performance-and-visualization/SKILL.md)

## Typical flow
1. Load both images with `load_image`.
2. Move the image tensors, extractor, and matcher to the same device.
3. Build one supported pairing: `superpoint`, `disk`, `aliked`, `sift`, or `doghardnet`.
4. Extract features, run LightGlue, and strip the batch axis with `rbd` when you are handling the dicts yourself.
5. Index the keypoints with the match indices to recover coordinate arrays.
6. Save the visualization with the bundled CLI or the `viz2d` helpers.

## First-run note
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](references/workflows.md) and the CLI in [scripts/match_image_pair.py](scripts/match_image_pair.py).

Files in this skill

  • SKILL.md2.5 KB
  • references/data-and-results.md3.1 KB
  • references/troubleshooting.md2.5 KB
  • references/workflows.md3.5 KB
  • scripts/match_image_pair.py8.8 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.