> For the complete documentation index, see [llms.txt](https://docs.optitrack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.optitrack.com/v2.3/motive-ui-panes/settings/settings-assets/skeletons.md).

# Skeletons

### Skeleton Display Properties

A list of the default Skeleton display properties for newly created skeletons is listed under the *Skeletons* tab. These properties are applied to only skeleton assets that are newly created after the properties have been modified. For descriptions of the skeleton properties, please read through the Properties: Skeleton page.

{% hint style="info" %}
Note that this is the default *creation* properties. Asset-specific skeleton properties are modified directly from the [Properties pane](/v2.3/motive-ui-panes/properties-pane.md).
{% endhint %}

### Advanced Properties

**Skeleton Creation Pose**

Chooses which Skeleton calibration pose to be used for creation. (T-pose, A-pose Palms Downward, A-pose Palms Forward, and A-pose Elbows Bent)

**Head Upright**

Creates the skeleton with heads upright irrespective of head marker locations.

**Straight Arms**

Creates the skeleton with arms straight even when arm markers are not straight.

**Straight Legs**

Creates the skeleton with straight knee joints even when leg markers are not straight.

**Feet On Floor**

Creates the skeleton with feet planted on the ground level.

**Height Marker**

Force the solver so that the height of the created skeleton aligns with the top head marker.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.optitrack.com/v2.3/motive-ui-panes/settings/settings-assets/skeletons.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.