screenshot-use

Quick Review

The skill provides a basic workflow for screenshot management in testing, but lacks crucial details for autonomous execution. The description is too terse for a CLI agent to reliably invoke without clarification (e.g., what constitutes 'right UI', where to replace the asset, what 'gate' means). Task knowledge is minimal - steps are outlined but lack specifics on verification criteria, replacement mechanics, or error handling. Structure is adequate for this simple skill with clear numbered steps. Novelty is moderate - while screenshot workflows are common, automating the pick-verify-replace-CI cycle has value, though the current implementation is too underspecified to realize that value. A CLI agent would need to ask multiple clarifying questions about file paths, verification criteria, and CI integration.