> For the complete documentation index, see [llms.txt](https://guardian.hedera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guardian.hedera.com/docs/develop/guardian/workspace/policies/auto-suggestion.md). # Auto Suggestion The Auto Suggestion feature assists users in constructing policies by automatically recommending 'next' blocks or other policy language constructs based on the structure of existing policies. This feature draws upon a repository of common practices to provide suggestions within the context of the policy being developed. ### Benefits of Auto Suggestion * **Simplified Policy Creation:** The feature significantly lowers the barrier to creating real-world complexity policies by offering intuitive guidance throughout the policy development process. * **Enhanced Efficiency:** By providing relevant suggestions, the mechanism speeds up the policy construction process, allowing users to focus more on strategic aspects rather than getting bogged down by complexities. * **Improved Policy Quality:** With auto-suggestions based on established best practices, the quality of policies is inherently improved, ensuring that they are both comprehensive and robust. * **User Empowerment:** Users, especially those new to policy creation, are empowered with a tool that assists them in navigating through the intricacies of policy language and structure. --- # 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://guardian.hedera.com/docs/develop/guardian/workspace/policies/auto-suggestion.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.