Aura Skills

Reusable, shareable instructions that teach Aura how to do your team's work — drop in a file, invoke it with a slash command, or let Aura reach for it on its own.

What are Aura Skills?

A Skill is a small Markdown file (SKILL.md) that packages up a set of instructions for Aura. Think of it as a saved, reusable prompt with a name. Once a skill lives in your project, Aura can:

• Run it on demand when you type /skill-name in chat, or
• Reach for it automatically when your request matches what the skill is for.

Skills are Claude Code–compatible. A SKILL.md you write for Aura works in Claude Code, and a skill you already have for Claude Code works in Aura — same format, no conversion.

Skills live in your Unreal project at:

<YourProject>/Saved/.Aura/Skills/<skill-name>/SKILL.md

Because they're plain files in your project, you can commit them to version control and share them with your whole team.

---

Capabilities

• Slash commands — Type /my-skill to inject the skill's instructions into the conversation instantly.
• Autonomous invocation — Aura sees a one-line description of each skill and pulls in the right one on its own when your request fits — no command needed.
• Self-authoring — Ask Aura to create a skill ("turn this workflow into a skill") and it writes a valid SKILL.md for you.

Note: A skill is injected text, not code that Aura runs. Aura never executes a skill's scripts on its own. (In Agentic/Custom mode, Aura can run a bundled script through its normal command tool, which always asks you for approval first.)

---

---

How to use

1. Add a skill

Create the folder and file in your project:

<YourProject>/Saved/.Aura/Skills/your-skill-name/SKILL.md

The first time Aura looks for skills it scaffolds the Skills/ folder and drops a README.md explaining the format, so you'll have a starting point even if you've never made one.

2. Run a skill explicitly

In the Aura chat, type / to open the skill picker, or type the command directly:

/cute-animal-skill

Add arguments after the command to scope it:

/cute-animal-skill create a cute cat

The skill's instructions are injected and Aura follows them.

3. Ask Aura to run the skill

You don't have to use the command. Just tell Aura the skill to use:

"Can you use a skill that creates cute animals to create a cute kitten?"

Aura sees the cute-animal-skill skill's description, recognizes the match, and pulls it in automatically.

4. Ask Aura to write a skill

Describe a workflow and ask Aura to save it:

"Turn that review checklist into a reusable skill called level-review."

Aura writes a valid SKILL.md to your Skills folder, and it's immediately available in the / picker.

5. Share skills with your team

Skills are project files, so commit them to version control. Unreal's default ignore rules exclude Saved/, so add a negation so the folder is tracked:

# .gitignore / .p4ignore
Saved/
!Saved/.Aura/Skills/

Aura will warn you in chat if it detects that your ignore file would exclude your skills.

---

Examples

Example — A team coding-standard skill

Goal: Every Blueprint your team creates should follow the same naming and structure conventions.

Create Saved/.Aura/Skills/bp-standards/SKILL.md:

---
description: Apply our team's Blueprint conventions when creating or editing Blueprints.
argument-hint: [blueprint name]
---

Follow these conventions for any Blueprint work:

- **Naming:** `BP_` prefix for actors, `WBP_` for widgets, `BPI_` for interfaces.
- **Variables:** PascalCase, with categories set. Booleans start with `b` (e.g. `bIsAlive`).
- **Functions:** Verb-first names (`ApplyDamage`, not `DamageApply`). Add a tooltip.
- **Structure:** No logic in the event graph beyond dispatch — push real work into functions.
- **Comments:** Wrap each logical section in a labeled comment box.

After making changes, compile the Blueprint and report any errors.

Use it:

/bp-standards BP_HealthComponent

Aura injects your conventions and creates/edits the Blueprint to match them — every time, consistently, across everyone on the team.

---

---

Tips & troubleshooting

• Write descriptions for the model, not just for humans. Autonomous invocation is only as good as your description and when-to-use. Say plainly what it does and when to reach for it.
• Skill not showing up? Confirm the path is Saved/.Aura/Skills/<name>/SKILL.md, the folder name is lowercase-with-hyphens, and the file has a description. Aura skips folders with no SKILL.md and surfaces a warning in chat.
• Changes not appearing? Discovery refreshes when the Aura window regains focus — click into the editor and back, or just re-open the picker.

---