> For the complete documentation index, see [llms.txt](https://experience-digital-transform.gitbook.io/experience-digital-transformation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://experience-digital-transform.gitbook.io/experience-digital-transformation/cloud-for-dpi/chapter-1/optional-tooling-for-the-assessment.md).

# Optional tooling for the assessment

Teams that already use AI agents can use the public [GIGA Cloud Agent Plugin](https://git.vanillacore.net/giga/cloud-skills) as a workbench for the assessment. It now contains six user-facing skills: public-service- platform-architecture frames service-to-foundation questions, while five focused skills profile the workload, compare delivery arrangements, explain interoperability and dependency conditions, identify missing evidence, and maintain the decision matrix. The plugin organises service facts, options, uncertainties and evidence into one reviewable record rather than replacing local judgement.

The plugin is optional and does not make a local choice. It helps a team organise the service facts, options, uncertainties and evidence that the institution must review for itself. Teams should use it only where their AI environment and information-handling rules permit it, and they should check the repository and requested permissions before installation.


---

# 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://experience-digital-transform.gitbook.io/experience-digital-transformation/cloud-for-dpi/chapter-1/optional-tooling-for-the-assessment.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.