> For the complete documentation index, see [llms.txt](https://learn.mechanic.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.mechanic.dev/custom-help.md). # Get help with a custom task Get help with your custom Mechanic task — community Slack, developer hiring, and partner matchmaking. {% hint style="info" %} **What support is included with my Mechanic subscription?** Our support team assists with **platform issues** and issues with tasks from the [Mechanic task library](https://tasks.mechanic.dev/). For these topics, contact us at . For custom tasks not included in our task library, our support service is limited to Mechanic platform support. See the options below for getting help with custom tasks. {% endhint %} ## Getting help with custom tasks ### Slack Community * **Community Support:** We encourage you to join our Slack community, where you can seek advice and share experiences with other Mechanic developers. Often, community members can offer insights or solutions based on their experiences. * **Joining the Community:** You can join our Slack community through the following link: [Mechanic Slack Community](https://slack.mechanic.dev/). ### Hiring a Developer * **Partner Directory:** We recommend hiring a developer if the issue requires more in-depth technical expertise. Our partner directory lists qualified developers familiar with Mechanic task development. * **Finding a Developer:** Visit our partner directory at [partners.mechanic.dev](https://partners.mechanic.dev/) to find a developer who can customize or optimize your task. If you want to be matched with a suitable developer, use our [matchmaking service](https://partners.mechanic.dev/matchmaking).
--- # 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://learn.mechanic.dev/custom-help.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.