reversa-visor

Extract components, navigation flows, and screen states from screenshots.

Updated Feb 27, 2026
One-click install
npx skills add https://github.com/luisgustavooliveira/skills --skill reversa-visor-luisgustavooliveira
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-visor
Source: https://github.com/luisgustavooliveira/skills/tree/main/reversa-visor
Command: npx skills add https://github.com/luisgustavooliveira/skills --skill reversa-visor-luisgustavooliveira

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the documentation of a legacy system's interface from screenshots, saving time and effort by eliminating the need for the system to be running.

Core Features & Use Cases

  • Automated Interface Documentation: Extracts components, layouts, navigation flows, and screen states from screenshots.
  • Use Case: When screenshots of the system interface are available, use this Skill to generate detailed documentation without the need for the system to be operational.

Quick Start

Use the reversa-visor skill to document the system interface from the screenshots you have.

Frequently Asked Questions about reversa-visor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document a legacy system interface from screenshots?

Automated interface documentation from screenshots extracts components, layouts, navigation flows, and screen states, eliminating the need for the legacy system to be running during the documentation process.

Can I generate system documentation without direct access to the application?

Yes, you can generate system documentation without direct access by processing pre-saved screenshots, allowing you to document legacy systems even when they are completely offline.

What screen elements can be extracted during screenshot analysis for interface documentation?

Screenshot analysis for interface documentation extracts UI components, layouts, navigation flows, and screen states to map the complete structure and behavior of the interface.

Do I need image processing capabilities to automate interface documentation from screenshots?

Yes, automated interface documentation from screenshots requires image processing capabilities to accurately detect and extract interface components and navigation flows from the provided images.

What is the best way to document screen states for legacy systems?

The best way to document screen states for legacy systems is by analyzing pre-saved screenshots to capture interface conditions and navigation flows without requiring the system to be operational.

Why use screenshot analysis for system documentation instead of direct code inspection?

Screenshot analysis is used for system documentation instead of direct code inspection when dealing with legacy systems where direct access is impossible, relying on pre-saved screenshots to capture the interface.