> For the complete documentation index, see [llms.txt](https://docs.holons.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.holons.io/software/holonsbot/holonsbot-commands.md).

# HolonsBot commands

### Task Management

* `/task [description]` - Creates a new task
  * Example: `/task do the dishes`
* `/tasks` - Lists currently open tasks
* `/actions` - Lists the history of completed tasks

### Recognition & Value System

* `/appreciate [@user] [reason]` - Sends appreciation to the listed user
  * Example: `/appreciate @laura for taking care of the garden`
* `/status` - Shows rank of user according to the value points
* `/weights` - Changes the points assigned to each action

### Needs & Offers

* `/request [description]` - Something you would like to have
  * Example: `/request foot massage`
* `/offer [description]` - Something you would like to give
  * Example: `/offer yoga sessions`
* `/board` - Lists all users' requests and offers

### Community & Facilitation

* `/prompt` - Indicates the day of the current lunation, together with a suggested team activity
* `/facilitate [issue]` - Gives advice on community issues
  * Example: `/facilitate i don't feel recognized`
* `/bigtalk` - Get to know each other better by collectively answering the prompt

### Role Management

* `/assignroles` - Assigns roles to members of the community based on their actions
* `/setroles [roles]` - Defines roles within the community
  * Example: `/setroles cook, gardener`

### Shopping & Expenses

* `/buy [item]` - Adds an item to the shopping list
  * Example: `/buy milk`
* `/shopping` - Displays the shopping list as clickable items
* `/spent` - Submits an expense in the format /spent \[quantity] \[currency] \[reason]
  * Example: /spent 10 euros shopping
* `/balance` - Prints balance table /balance \[currency]

### Personal Values & Needs

* `/ivalue` - Allows to specify the list of values for the user
* `/values [@users]` - Visualizes the shared values of the specified users, or of all users
* `/ineed` - Allows to specify the list of needs for the user
* `/needs [@users]` - Visualizes the shared needs of the specified users, or of all users

### Holon Management

* `/restart` - Resets everything, all data will be lost.
* `/fork` - Unbinds federated chats
* `/federate` - Federates with another holon

### Content Management

* `/tag [tag]` - Saves content under the specified tag
* `/publish` - Saves the content in the holosphere
* `/cast` - Saves the content on every scale in the holosphere
* `/summarize` - Listens to the conversation and summarises it when `/done` is entered

### System & Interface

* `/settings` - Opens up the configuration interface
* `/dashboard` - A direct link to the web dashboard
* `/checklists` - Opens up the list of checklists
* `/agenda` - Opens up the agenda interface


---

# 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.holons.io/software/holonsbot/holonsbot-commands.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.