Agent Skills

A large tool catalog does not teach an agent how to use it correctly. An agent that can call SetParameterByIndex still has to know that a material change does not show in the level until the material is applied, that a ProgressBar fill is driven by its Percent property and not by its size, or that saving while inside a Multi-User session writes into a Concert sandbox. Agent Skills carry that workflow knowledge as short procedures stored in the project itself.

What a skill actually is

A skill is a real Unreal asset: a Blueprint whose parent class is UAgentSkill, creatable from the Content Browser under Artificial Intelligence, Generative AI, or authored by the agent itself. It carries two authored fields. Description is the one-line summary of what the skill covers and when to reach for it. Instructions is the multi-line body holding the actual procedure and its gotchas. Because a skill is an asset and not a loose file, it sits in Content, travels with the project, and goes through source control and review like everything else your team ships.

How the agent finds the right one

• ListSkills returns only a map of skill path to short description, so surveying the entire library costs almost nothing in context.
• GetSkills takes an explicit list of paths and returns the full instruction body for just those skills, which is the second half of the same progressive-disclosure trick the toolset meta-tools use.
• The instructions block the MCP server returns during the initialize handshake tells the agent to call ListSkills first whenever it is asked what it can do, then read the relevant skill before starting the work.
• The same library is a first-class CLI surface: claudus skill list names every skill and claudus skill show prints the ones you ask for, so an agent working from a terminal finds them from claudus --help instead of having to know the toolset name.
• CreateSkill and UpdateSkill let the agent write the library back. Both are documented as calls it may only make after explicit direction from you.
• ClaudusBridge also exposes CreateAgentSkill on its own Asset toolset, taking a folder, name, description and instructions body, and returning the generated class path of the new skill.

What ships in the box

The plugin ships domain-specific Agent Skills for editor workflows. Query ListSkills in the current project for its actual inventory; read the relevant instructions and compare them with the current tool schema before acting.

• Editor and scene: EditorNavigation, SceneAndActors, LevelsAndLighting, NonIntrusiveMultiLevel, ObjectProperties, HeadlessCapture
• Blueprints and gameplay: Blueprints, BlueprintGraphDSL, GameFramework, CharacterMovement, EnhancedInput, GameplayTagsAndData, SaveGame, Animation
• Rendering and effects: Materials, CustomHLSL, Niagara, UMG
• Collaboration and workflow: MultiUserEditing, MultiAgentOrchestration, TerminalGuide, ToolLibraryAuthoring, SkillGrowth
• Showcase: ChessGameplay, MultiUserChess

Growing the library on your own project

The shipped set is a starting point, not the destination. The SkillGrowth skill sets the protocol for adding to it: when you finish a durable, reusable workflow, or hit a non-obvious project gotcha that no existing skill covers, capture it. Deduplicate against ListSkills first, confirm with the user before writing, and keep the result executable rather than descriptive. That is what turns the library from generic Unreal advice into your studio's naming conventions, your water system's quirks, and the three steps your build always needs in the right order.

Against the 5.7 generation