erhe-headless-verify

Automates headless Vulkan editor verification via MCP server management and screenshots.

896|86|Updated May 1, 2021
One-click install
npx skills add https://github.com/tksuoran/erhe --skill erhe-headless-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: erhe-headless-verify
Source: https://github.com/tksuoran/erhe/tree/main/.claude/skills/erhe-headless-verify
Command: npx skills add https://github.com/tksuoran/erhe --skill erhe-headless-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the verification and testing of the headless Vulkan editor without a display, ensuring that runtime changes behave as expected.

Core Features & Use Cases

  • Headless Editor Build: Builds the headless Vulkan editor for automated testing.
  • MCP Server Management: Manages the editor's embedded MCP server for remote commands.
  • Scene Query & Mutation: Executes commands on the editor, such as scene queries and mutations.
  • Screenshot Capture: Captures screenshots of the editor's output for visual verification.
  • Clean Up: Ensures resources are properly cleaned up after testing.
  • Use Case: When a change in the editor code is made, this Skill can be used to automatically verify that the editor still behaves correctly.

Quick Start

Run the script to build the headless editor and start the verification process: cmake --build build_vs2026_vulkan_headless --target editor --config Debug

Frequently Asked Questions about erhe-headless-verify

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

FAQPage Schema
How do I automate testing for a headless Vulkan editor without a display?

Automate headless Vulkan editor testing by building the editor, managing its embedded MCP server, driving it with scripts, capturing screenshots, and cleaning up resources automatically.

What is an MCP server used for in editor testing?

An MCP server in editor testing manages remote commands sent to the headless editor, enabling automated scene queries and mutations during the verification process.

How do I capture screenshots during automated 3D graphics editor testing?

Capture screenshots during automated 3D graphics editor testing by running scripts that drive the headless editor via its MCP server and collect visual output for verification.

Can I use this approach to verify runtime changes in a Vulkan editor?

Yes, you can verify runtime changes in a Vulkan editor by building the headless target, executing scene mutations through the MCP server, and checking captured screenshots.

What is the best way to build a headless Vulkan editor for automated verification?

Build a headless Vulkan editor for automated verification by running the cmake build command targeting the editor in Debug configuration, then start the embedded MCP server.

Does headless editor testing support scene queries and mutations?

Headless editor testing supports scene queries and mutations by executing remote commands through the editor's embedded MCP server during the automated verification process.