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

# VGS Agent Guide

Route an AI agent to the right VGS documentation, planning workflow, and implementation guidance.

Use this page to decide which VGS guidance applies to the customer's request. Reading this page does not install a Skill, CLI, plugin, or MCP server.

For “How do I integrate with VGS?”, propose a Credential Management Platform (CMP) integration first. Standard SANDBOX tenant setup provides its baseline. Inspect the customer's application and intended outcome, then identify only the additions it needs. Do not ask the customer to choose internal VGS products or configure the default bootstrap. Preserve an existing integration or an explicitly requested specialized flow.

| Request                                                             | Route                                                                                                                    |
| ------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
| Specific documentation or capability question                       | Answer directly from the relevant official documentation.                                                                |
| “How do I integrate with VGS?” or new-customer setup                | Follow [Guided VGS Setup](https://docs.verygoodsecurity.com/guided-vgs-setup.md), starting with standard CMP onboarding. |
| A change to an existing integration, migration, or specialized flow | Follow Guided VGS Setup for the requested change; reuse existing resources and decisions.                                |
| Scoped SDK implementation or repair                                 | Inspect the project, read the applicable package guidance, and prepare a scoped plan.                                    |
| Existing `VGS_ONBOARDING.md`                                        | Verify recorded evidence and resume applicable incomplete selected steps.                                                |
| Combined platform and application work                              | Produce one dependency-ordered plan that covers both and records their dependencies.                                     |

## Expected handoff

For a concrete integration or setup request, the planning workflow creates a reviewable, command-free `VGS_ONBOARDING.md`, prepares applicable SDK Skills where allowed, refines the plan, and then asks the customer to approve implementation scope. The file records architecture, decisions, selected steps, dependencies, blockers, Skill preparation, and separate progress for VGS resources, application changes, and end-to-end validation.

Creating the plan authorizes no installation, authentication, application change, or VGS mutation. Guided onboarding and automated validation are SANDBOX-only.

## Continue with the complete procedure

* Use [Guided VGS Setup](https://docs.verygoodsecurity.com/guided-vgs-setup.md) for project discovery, planning, and implementation-scope approval.
* Use [Agent Guided Implementation](https://docs.verygoodsecurity.com/agent-guided-implementation.md) after the customer approves selected work.
* Resolve optional execution guidance through the [public VGS Skills catalog](https://github.com/verygoodsecurity/skills). Follow the installation source declared for each selected Skill; do not assume every Skill is installed from the catalog repository.

If GitBook returned this page through an `?ask=` query, use the answer as routing support only. Fetch the complete applicable procedure before planning or implementing. A `goal=` value can preserve the customer's objective, but no special query string or GitBook endpoint is required for this workflow.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.verygoodsecurity.com/skill.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.