orion-asset-management

Validate Unreal Engine asset names, folders, and workflows in Orion projects.

16|3|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/OrionUE/Orion_FreeEdition --skill orion-asset-management
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orion-asset-management
Source: https://github.com/OrionUE/Orion_FreeEdition/tree/main/.agents/skills/orion-asset-management
Command: npx skills add https://github.com/OrionUE/Orion_FreeEdition --skill orion-asset-management

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill prevents Unreal Engine asset organization problems by enforcing consistent naming, folder structures, save verification, and content management practices across complex projects.

Core Features & Use Cases

  • Asset Naming & Taxonomy Enforcement: Applies Allar-style prefixes, Blueprint naming conventions, PascalCase folder rules, and Orion Content taxonomy for Unreal assets.
  • Asset Workflow Validation: Guides creation, importing, moving, converting, and batch-editing workflows with checks for save persistence, overwrite risks, and GameFeature layouts.
  • Use Case: When creating a new Widget Blueprint, Gameplay Ability, Material Instance, or GameFeature asset, use this Skill to select the correct path, naming pattern, and validation process before saving.

Quick Start

Use the orion-asset-management skill before creating or organizing Unreal Engine assets to validate the asset name, folder path, and workflow requirements.

Frequently Asked Questions about orion-asset-management

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

FAQPage Schema
How do I enforce Unreal Engine asset naming conventions for Blueprint and UI assets?

Unreal Engine asset naming conventions are enforced by applying Allar-style prefixes, PascalCase folder rules, and Orion Content taxonomy to validate Blueprint and UI asset creation before saving.

What is the correct folder taxonomy for organizing GameFeature and gameplay ability assets?

Folder taxonomy for GameFeature and gameplay ability assets follows Orion Content taxonomy rules, enforcing PascalCase folder structures and specific plugin content layouts to maintain production-ready organization.

How do I validate save persistence and overwrite risks when batch editing Unreal Engine assets?

Batch editing Unreal Engine assets requires workflow validation checks for save persistence and overwrite risks, ensuring physical material handling and content organization rules are met before finalizing operations.

Does this asset management workflow support audio, media, and localization asset creation?

Asset management workflows support audio, media, and localization asset creation by applying consistent naming patterns, folder taxonomy rules, and validation processes across these specific asset types.

Can I use this to validate physical material handling and plugin content layouts?

Physical material handling and plugin content layouts are validated through workflow checks that enforce specific naming patterns, folder paths, and content organization rules for reliable asset pipelines.

What's the best way to select the correct path and naming pattern for a new Widget Blueprint?

Selecting the correct path and naming pattern for a new Widget Blueprint involves applying Orion Content taxonomy, validating prefixes, and verifying folder structures before executing the save workflow.