> For the complete documentation index, see [llms.txt](https://bit.lockyzdev.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bit.lockyzdev.com/plugins/2024.2/for-developers/certification-requirements.md). # Certification Requirements {% hint style="danger" %} We're no longer accepting certification requests for this version of Bit {% endhint %} For a plugin to be "certified" by for use with Bit a few requirements will need to be met. ## Plugin ID Requirements Your Plugins ID: MUST be in Kebab Case (ex. kebab-case)!\ CANNOT include numbers!\ CANNOT include symbols bar the dash (-)!\ CANNOT include a space (We recommend using a dash (-) instead)\ CANNOT use the names `bit-core`or `example-plugin`\ CANNOT use offensive language\ MUST be unique compared to the other Bit Certified Plugins ## Plugin Content Requirements Your Plugin: CANNOT contain NSFW content\ CANNOT break Discords TOS, Community Guidelines or Developer TOS\ CANNOT break the law in the region we reside (New South Wales, Australia) ## Soft Requirements These things are not exactly required, but these are extra factors we consider when choosing whether to certify a plugin or not. We give extra consideration to plugins that: Create fun and engaging content to users\ Aid in the moderation of a Discord server\ Help deal with spam\ Contain content that will give some benefit to users --- # 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://bit.lockyzdev.com/plugins/2024.2/for-developers/certification-requirements.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.