> For the complete documentation index, see [llms.txt](https://docs.convai.com/api-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.convai.com/api-docs/zh/convai-playground/character-customization/character-description.md).
# 角色描述
了解如何在 Convai Playground 中使用“角色描述”页面来定义角色身份、说话风格和独特特征。
## 简介
该 **角色描述** 页面是您定义 AI 角色个性、背景故事和沟通风格的地方。Convai Playground 中的每个角色都有自己专属的角色描述页面，确保拥有独特身份，并可随着时间推移进行优化。
***
## 访问角色描述页面
您可以通过点击任意 **角色卡** 在您的 **仪表板**。这会打开该角色的资料页面，您可以在此编辑和管理其核心属性。
## 主要功能与部分
### 1. 角色名称和 ID
* **角色名称** – 可编辑字段，用于角色的显示名称。
* **角色 ID** – 角色的唯一标识符，对于在 **Convai SDK** 和 API 集成中使用它至关重要。
* 您可以复制该 ID 以在应用程序中使用。
{% hint style="success" %}
**支持提示**: 如果您在向支持团队寻求帮助时需要协助，请在报告与角色相关的问题时提供此 ID。
{% endhint %}
***
### 2. 核心描述 / 说话风格 / 具身化
**核心描述**
* 添加有关角色背景故事、性格特征、独特特征以及任何行为准则的细节。
* 字数限制： **1000 字**.
**说话风格**
* **描述角色如何说话** – 概述角色的语气、语速、正式程度和说话模式。包括他们经常使用的独特表达或短语。
* **示例对话** – 提供示例句子，展示角色典型的说话风格，包括能强化其个性的标志性短语。
**具身**
* 目前正在开发中，将很快上线。
***
## 示例
如需灵感，请浏览 **示例角色** 位于仪表板中。这些示例展示了不同角色的核心描述和说话风格是如何构建的。
***
## 结论
角色描述页面是您 AI 角色身份的基础。通过清晰定义其个性、声音和独特特征，您可以确保互动始终如一且引人入胜。
---
# 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.convai.com/api-docs/zh/convai-playground/character-customization/character-description.md?ask=&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.
