> For the complete documentation index, see [llms.txt](https://nuscwiki.gitbook.io/25-26/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nuscwiki.gitbook.io/25-26/student-life/interest-groups/sports/nuscaptain-s-ball.md).
# NUSCaptain's Ball
The Captain’s Ball Interest Group is a healthy mix of both casual and competitive fun! Our weekly sessions are a great opportunity to come down and decompress from the stress of the semester through sport.
### Weekly Sessions!
Our sessions are held every Monday on a rotating time slot between 6pm - 8pm, 8pm - 10 pm, and 10pm - 12am! Captain’s Ball is also very beginner-friendly (no prior experience in ball sports needed!) and the interest group is full of friendly players who are always eager to help out
For those looking for something more competitive, we also regularly participate in the NUS Inter-Faculty Games as well as Inter-College Games. In AY25/26, Team NUSC managed to achieve Silver in IFG and Bronze in ICG!
### Inter-College Games
We hope to see you in the coming Academic Year!!
---
# 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://nuscwiki.gitbook.io/25-26/student-life/interest-groups/sports/nuscaptain-s-ball.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.
