ue-engine-mount

Mount the Unreal Engine source tree at /engine for read-only header inspection.

2|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/buchananwill/ue-claude-scaffold --skill ue-engine-mount
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ue-engine-mount
Source: https://github.com/buchananwill/ue-claude-scaffold/tree/main/skills/ue-engine-mount
Command: npx skills add https://github.com/buchananwill/ue-claude-scaffold --skill ue-engine-mount

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tells container agents where the Unreal Engine source tree is mounted inside the container, enabling them to grep and read engine headers to verify API signatures and class hierarchies.

Core Features & Use Cases

  • Mount-point at /engine inside the container for read-only access to the Unreal Engine source.
  • Enables header inspection to verify API signatures and class hierarchies during containerized workflows.
  • Ensures safety by preventing write access to the mounted engine tree.

Quick Start

Mount the Unreal Engine source tree inside the container at /engine and grep headers to verify API signatures.

Frequently Asked Questions about ue-engine-mount

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

FAQPage Schema
How do I inspect Unreal Engine headers inside a container to verify API signatures?

To inspect Unreal Engine headers inside a container, you mount the engine source tree at the /engine path as a read-only volume, allowing agents to safely grep and read headers for API verification.

Can I mount the Unreal Engine source tree as read-only in a containerized workflow?

Yes, you can mount the Unreal Engine source tree as read-only in a containerized workflow by designating /engine as the mount point to ensure safe header inspection without risking source modification.

Why do I need a read-only mount for checking UE class hierarchies in containers?

A read-only mount is needed for checking UE class hierarchies to ensure safety by preventing write access to the mounted engine tree, guaranteeing the source remains unmodified during API verification.

What is the designated path to mount the UE engine tree for containerized API checks?

The designated path to mount the UE engine tree for containerized API checks is /engine inside the container, providing agents with direct access to read engine headers and validate class structures.

Does mounting the Unreal Engine source tree at /engine allow agents to modify files?

Mounting the Unreal Engine source tree at /engine does not allow agents to modify files because the mount is configured as read-only, ensuring safe inspection of API signatures and class hierarchies without alteration.