> For the complete documentation index, see [llms.txt](https://recconnect.gitbook.io/recconnect-tutorials/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://recconnect.gitbook.io/recconnect-tutorials/game-schedules/create-game-schedule.md).
# Create Game Schedule
1\) Login to the RecConnect dashboard at: [https://admin.recconnect.io](https://my.recconnect.io/)
2\) Select Game Schedules in the left hand navigation and then select your team from the dropdown. If you have not created a team yet, please see the create team documentation.
3\) Fill out the form and click `Add Game` . This process can be repeated for as many games as you'd like.
4\) After games are added, you will have the ability to publish your schedule to the public. Simply click the `Publish Schedule` button. You also have the option to `Unpublish Schedule` if need be. `Download Schedule` will download a PDF version of the schedule.
---
# 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://recconnect.gitbook.io/recconnect-tutorials/game-schedules/create-game-schedule.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.