> For the complete documentation index, see [llms.txt](https://docs.shiftiq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shiftiq.com/help/standards/edit-standards/searching-standards.md).

# Searching Standards

From the Admin Home page select the Standards Toolkit

From the Admin Home page select the **Standards** Toolkit

Under the **Counters** panel, select the **Standard Type** you would like to search for

Users are able to search for a specific **Standard Type: Area, Competency, Document, Framework or Profile** You can view as little or as much information as you want on the **Standards Search** page by selecting the information you require to see under **Settings**.

**Filter:** You can specify one filter for each search operation, but the filter itself can include multiple fields, multiple criteria **Clear:** The filters should be cleared, as your new search term maybe for something entirely different from the original search query.


---

# 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://docs.shiftiq.com/help/standards/edit-standards/searching-standards.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.