awen

View saved version →

---
name: awen-brand
description: Make work that follows the organisation's brand, memories and skills in awen. Use when the user asks for on-brand work, names a brand, a client or a style they saved in awen, or asks to change a saved default.
---

# Work on brand with awen

awen keeps the organisation's brand knowledge as memories and skills. awen's agent reads them itself on every turn.

## Name what to follow

1. Call `list_memories` to see the names of the memories the user can use.
2. Name the memories and skills that apply in the `prompt` of `create_with_awen`, in the user's words, such as "follow the Spring 27 brand memory". Do not copy their contents into the prompt: awen's agent reads the current version itself.
3. Do not take brand rules from files on this machine unless the user asks you to. Upload such a file as a reference instead, as the `awen-create` skill describes.

## Saved defaults

Saved defaults, such as how many images to make, live in awen. To change one, ask awen's agent in a turn. Do not save it in your own memory: the next turn in awen would not see it.

View saved version →

---
name: awen-create
description: Make or edit images, posters, logos, 3D models or documents with awen. Use when the user asks for visual or design work, even if they do not name awen, unless they ask for code or a local file.
---

# Create with awen

awen's agent does the creative work. Your job is to give it a clear brief, start the turn, and report what it made.

## Before the turn

1. Pick the project. When the user names none, call `list_projects` and choose the one that fits, then say which one you chose. Ask only when nothing fits or a named project matches more than one.
2. Ask first when the request does not say what to make. A brand or file you find on this machine is not a request.
3. Bring the user's files. For a file on this machine, call `create_upload`, run the command it returns, then call `import_file` with its `upload_id`. For a public link, call `import_file` with the link. Pass the ids that `import_file` returns as `file_ids`.

## Write the brief

Pass the user's own words in `prompt`, plus what they told you about the goal, the audience, the format and the style. Do not invent a style they did not ask for. Use `image_count` and `image_resolution` only when the user gave a number or a size.

## Start and wait

1. Call `create_with_awen`. It spends the organisation's credits: a direct request from the user is approval, but describe your own ideas and ask before you start them.
2. When your host shows awen's card, the card follows the turn. Otherwise call `get_turn` with the `turn_id` until the status is no longer `working`.
3. When the turn ends with a question, show it to the user and wait for their answer. Pass it with the same `conversation_id`.
4. Never start paid work again on your own after a failure or a refusal: ask the user first.

## Find earlier work

To see recent work, or what is still running, call `list_conversations` with no project. When the user speaks of their projects, conversations, files, credits or usage and nothing in this conversation matches, look in awen.

View saved version →

---
name: awen-video
description: Make videos and motion with awen, from a brief or from images. Use when the user asks for a video, an animation, a clip or motion for an image, even if they do not name awen.
---

# Make a video with awen

Follow the `awen-create` skill to pick the project, bring files and start the turn. This skill adds what a video brief needs.

## Write the brief

Give awen's agent, in the user's words:

- what happens on screen, from start to end
- the length and the format (for example 9:16 for a story, 16:9 for a website)
- the images the video starts from or must follow, as `file_ids`
- the sound, when the user asked for it

awen's agent chooses the model and the settings. Do not name a model unless the user did.

## Wait for the result

A video takes longer than an image, and the turn stays `working` until its video is saved. Keep following the card, or call `get_turn` until the status is no longer `working`, then show the result or the failure. Do not start the same video again because it is still `working`.

A video costs more credits than an image. Do not make extra versions unless the user asks for them.