> For the complete documentation index, see [llms.txt](https://docs.yellowant.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yellowant.com/workflows/command-workflows/building-command-workflows/collection.md).
# Collection
A collection is a way of segregating workflows into sets in order to keep them more organized for every individual. This is totally up to the user and can be treated as having different set of workflows where each set forms a collection with some specific set of tasks. Watch out for custom collections for different domains which will soon launch on YellowAnt.
For command triggered workflows, collections also change the way the workflow is executed.
**If you create a new command triggered workflow and do not select/create a collection, by default it gets added to a collection called workflow.**
The way to execute such a command workflow would be to simply type: **workflow command-name** \
In case you select/add it to a workflow named myset, then the command changes to: **myset command-name**
Example 1:
In this case, the workflow command is "startmyday" and it belong to the collection "workflow" so the command to execute is "workflow startmyday".
Example 2:
In this case, the workflow command is "startmyday" and it belong to the collection "demo-collection" so the command to execute is "demo-collection startmyday".
We see that you can use the same command name, but place it uner different sets i.e. collections and use it in different contexts altogether without one interfering with the other.
This also makes it very easy for the user to view their workflows in the "My Workflows" panel by giving them an option to view them filtered by collections.
---
# 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.yellowant.com/workflows/command-workflows/building-command-workflows/collection.md?ask=&goal=
```
`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.