> For the complete documentation index, see [llms.txt](https://docs.motar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.motar.com/motar-core-services/intro-to-core-services/studio/add-a-skill-badge.md).

# Add a Skill Badge

Adding **Skill Badges**  to an asset in Studio can only be done during the initial asset creation. 

After uploading the asset (audio file shown) the new "Badges" tab will appear on supported asset types\*

{% hint style="info" %}
Currently, only video and audio assets support badging.
{% endhint %}

* **Click** on the **Badges** tab to select or **add** a new skill.

### Selecting an existing Skill

<figure><img src="/files/VqwPWaLMH9Z4GkKtUWiw" alt=""><figcaption></figcaption></figure>

* Available skills will show up in the dropdown, or you can type the skill name.
* Selecting that skill and clicking the + button will add the skill to the asset

### Adding a New Skill

* Click "Add New Skill" if none are found.
* A model will appear, enter the Skill Badge Name and Description

<figure><img src="/files/GFiDgHAs0T8dWK1NLN7O" alt="" width="563"><figcaption></figcaption></figure>

{% hint style="warning" %}
Skill Badge Names must be unique. If the name is taken the system will alert you.
{% endhint %}

* After entering the name and description, **Click** "Add Skill"

<figure><img src="/files/aiTFayRbHDO4Ms4uxpfR" alt="" width="563"><figcaption></figcaption></figure>

* The skill will **automatically** be added to the asset.

<figure><img src="/files/kdQSTAsL5fRwRqsOv1Tu" alt=""><figcaption></figcaption></figure>

* Added Skill Badges can be found on the Listing Details Page, once the listing is published.

<figure><img src="/files/03XudihWyETAVtHH9R9x" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.motar.com/motar-core-services/intro-to-core-services/studio/add-a-skill-badge.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.