> For the complete documentation index, see [llms.txt](https://docs.roboflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roboflow.com/roboflow/roboflow-ko/annotate/edit-keypoint-skeletons.md).

# Keypoint Skeleton 설정

## Keypoint Skeletons

Keypoint Skeletons는 하나의 필수적인 부분입니다 **Keypoint Detection 프로젝트의**. skeleton은 객체의 keypoints 수와 기본 위치, 이름, 색상, 그리고 edge를 알려줍니다. 라벨링하기 전에 [프로젝트의 Classes로 이동하여](/roboflow/roboflow-ko/datasets/manage-datasets/manage-classes.md) skeleton을 설정하세요.

클래스의 이름(사람이나 자동차와 같은 전체 객체 이름)을 추가한 후, Edit Keypoints를 선택합니다.

<figure><img src="/files/c23e5e362007392a3bfddf6da683347b72c4b7c7" alt="" width="563"><figcaption><p>Edit Keypoints 버튼은 Classes 페이지에 있습니다</p></figcaption></figure>

### Skeleton Editor

아무 곳이나 클릭해 첫 번째 포인트를 만들고 이름을 지정하세요. 그런 다음 계속 포인트를 만들거나, 포인트를 선택해 edge를 만들고 색상을 수정하거나 삭제할 수 있습니다.

<figure><img src="/files/48b4cfbc1938892a0aa618f7d78dcd84c97a7dd1" alt="" width="563"><figcaption><p>Skeleton Editor의 시각적 표현</p></figcaption></figure>

편집을 마치면 Save를 클릭하고 이미지를 업로드하고 라벨링을 계속하세요. skeleton은 annotation bounding box 안에 표시되어야 합니다.

참조 [Keypoints 라벨링 방법](/roboflow/roboflow-ko/annotate/annotate-keypoints.md).


---

# 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.roboflow.com/roboflow/roboflow-ko/annotate/edit-keypoint-skeletons.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.