> For the complete documentation index, see [llms.txt](https://gitbook.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.com/docs/create-content/blocks/task-list.md). # Task lists Add a task list to display tasks that can be completed Task lists allow you to create a list of items with checkboxes that you can check or uncheck. {% hint style="info" %} **Note:** Readers of your published site can't check or uncheck these boxes. You can decide which boxes are checked and unchecked when you create the content. {% endhint %} ### Example of a task list * [ ] Here’s a task that hasn’t been done * [ ] Here’s a subtask that has been done, indented using `Tab`. * [ ] Here’s a subtask that hasn’t been done. * [ ] Finally, an item, unindented using `shift` + `tab`. ### Representation in markdown ```markdown - [ ] Here’s a task that hasn’t been done - [x] Here’s a subtask that has been done, indented using `tab` - [ ] Here’s a subtask that hasn’t been done. - [ ] Finally, an item, unindented using `shift` + `tab`. ``` --- # 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://gitbook.com/docs/create-content/blocks/task-list.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.