> For the complete documentation index, see [llms.txt](https://token-engineering-commons.gitbook.io/tec-handbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://token-engineering-commons.gitbook.io/tec-handbook/processes/discord-roles/praise-giver.md).

# Praise Giver

This role is given to any community member who would like to praise other members for their contributions to the community. Without this role/tag in one’s Discord profile, the praise (using !praise command) will not be recognized by the bot and will not be recorded and quantified.

**To get this role, the member can request it from any Steward or Admin.**

*General Permissions of Server*

* View channels

*Membership Permissions*

* Create invite
* Change nickname

*Text Channel Permissions*

* Send messages
* Attach files
* Add reactions
* Use external emoji
* Mention @everyone, @here and all roles
* Read message history
* Use application commands

*Voice Channel Permissions*

* Connect
* Speak
* Video
* Use voice activity

*Stage Channel Permissions*

* Request to speak


---

# 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://token-engineering-commons.gitbook.io/tec-handbook/processes/discord-roles/praise-giver.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.