> For the complete documentation index, see [llms.txt](https://hacktoberfest-handbook.mlh.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacktoberfest-handbook.mlh.com/hack-days-partner-modules.md).

# Partner Challenges

Selected Hacktoberfest Hack Day events may receive one additional partner prize category. The MLH Hacktoberfest team assigns the category and adds it to OrganizerHQ automatically; hosts do not need to create it.

Use the page for your assigned category to find the participant-facing challenge copy, resources, opening materials, winner guidance, and expected prize:

* [Google Gemma](/hack-days-partner-modules/partner-challenge-google-gemma.md)
* [Snowflake](/hack-days-partner-modules/partner-challenge-snowflake-coco.md)
* [Solana](/hack-days-partner-modules/partner-challenge-solana.md)
* [GitHub Copilot](/hack-days-partner-modules/partner-challenge-github-copilot.md)

Your event onboarding remains the source of truth for its assigned category and prize details. If an assigned category is missing from OrganizerHQ, contact <hacktoberfest@mlh.io>. Do not create a replacement, although you may still add your own local challenges.

Every Hack Day also runs the separate [Best Open-Source AI Project challenge](/fest-planning-guide/open-source-prize-categories.md).


---

# 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://hacktoberfest-handbook.mlh.com/hack-days-partner-modules.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.