ss

Automated screenshot analysis works by loading the most recent image files from a configured folder and interpreting their visual content to drive actions. This mechanism handles configuration bootstrap, file reading checks, and permission safeguards to route intent to relevant debugging or review processes.

Automated visual analysis requires a configured folder directory containing screenshot files and appropriate read permissions. The system validates image existence during the bootstrap phase and enforces permission safeguards before loading files, ensuring a controlled environment for processing visual content.

Yes, screenshot analysis can route to sibling skills for explain, fix, or code-review actions based on interpreted visual content. The system enforces controlled routing with user confirmation, phase-safe interactions, and timeout handling to ensure appropriate downstream workflow execution.

Automated image processing handles configuration bootstrap, file reading checks, and timeout safeguards during visual content review. If screenshots are missing or permissions are insufficient, the system enforces controlled routing and validation checks to prevent processing failures and ensure phase-safe interactions.

Screenshot automation has limitations when files are missing from the configured folder, permissions are restricted, or timeouts occur during phase-safe interactions. The system enforces controlled routing and permission safeguards, requiring valid image existence and proper configuration bootstrap before processing visual content.

No dependencies are required to run the ss screenshot analysis skill. It operates independently with configuration bootstrap, image loading checks, and permission safeguards built into its core processing logic for retrieving and analyzing recent screenshots.