bevy-eyes-on

Capture Bevy application screenshots via state-gated BRP scenarios or timed fallback.

Updated Feb 10, 2026
One-click install
npx skills add https://github.com/OilProducts/agent-skills --skill bevy-eyes-on
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bevy-eyes-on
Source: https://github.com/OilProducts/agent-skills/tree/main/bevy-eyes-on
Command: npx skills add https://github.com/OilProducts/agent-skills --skill bevy-eyes-on

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill ensures you can capture precise screenshots of your Bevy application, whether you need to document specific game states or simply grab a visual at a particular moment.

Core Features & Use Cases

  • State-Gated Capture: Uses Bevy's Remote Procedure Call (BRP) to trigger screenshots only when specific game states are met, ensuring accuracy for gameplay or UI elements.
  • Timed Capture Fallback: If BRP hooks aren't available, it falls back to a simple timed delay for capturing screenshots.
  • Use Case: When testing a new UI feature in your Bevy game, use this Skill to capture a screenshot precisely when the settings menu is open, or when a specific item is highlighted on screen.

Quick Start

Use bevy-eyes-on to capture a screenshot of the Bevy application named 'MyGame' after the BRP sequence defined in 'scenario.jsonl' is complete.

Frequently Asked Questions about bevy-eyes-on

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

FAQPage Schema
How do I capture screenshots of a Bevy application during specific game states?

You can capture Bevy application screenshots during specific game states by using state-gated BRP scenarios. This triggers image capture only when defined application states are met, ensuring accurate visual documentation for gameplay or UI testing.

What is the best way to automate visual testing for Bevy game development?

Automating visual testing for Bevy game development is best handled by leveraging BRP communication to trigger screenshots at precise moments. This allows you to reliably document UI features or gameplay elements without manual intervention.

Does bevy-eyes-on work if my Bevy project doesn't have BRP hooks enabled?

Yes, bevy-eyes-on works without BRP hooks by falling back to a timed capture method. If BRP sequences are unavailable, the Skill uses a simple timed delay to capture screenshots as a reliable alternative.

How do I take a targeted screenshot of a UI element in a Bevy game?

To take a targeted screenshot of a UI element in a Bevy game, define a BRP sequence in a scenario file. The Skill waits for that specific state, like a settings menu opening, to capture the exact visual.

Can I capture full-display screenshots of my Bevy application using Python scripts?

Yes, you can capture full-display screenshots of your Bevy application using Python scripts. The Skill leverages Python for BRP communication and image capture, supporting both targeted and full-display screenshot outputs.

What are the limitations of using timed delays for Bevy screenshot capture?

Timed delays for Bevy screenshot capture lack state-awareness, meaning they might trigger before the application reaches the desired visual state. Using state-gated BRP scenarios is recommended for precise accuracy over timed fallbacks.