| name | formae-deps |
| description | Use when the user wants to add or remove a plugin schema dependency in an existing formae project's PklProject — e.g. 'add the grafana plugin', 'I need cloudflare DNS', 'drop the azure dependency'. |
Manage Formae Schema Dependencies
Use this skill to add or remove plugin schema dependencies in an existing formae project's PklProject file. This is authoring-only — schema packages provide PKL types and IDE completion. They do not install resource plugins on the agent and do not make infrastructure changes.
Step 1 — Locate the project's PklProject
Find the PklProject file in the current working directory or the path stated by the user. If it cannot be found, tell the user and stop — this skill requires an existing formae project. (If they need to create one from scratch, the formae-project-init skill applies.)
Step 2 — Add a dependency
2a — Resolve the package and version
Use get_hub_plugin to look up the plugin by name. If the plugin name is ambiguous or unknown, use search_hub_plugins first to find candidates and present them to the user for confirmation.
From the resolved plugin record, extract the latest stable version.
Trust gate. Check the originatorVerified field. If it is false, surface the originator domain explicitly to the user and ask for confirmation before proceeding. Do not silently add an unverified package.
2b — Write the dependency entry
Add the following block inside the dependencies section of PklProject:
["<name>"] {
uri = "package://hub.platform.engineering/plugins/<name>/schema/pkl/<name>/<name>@<version>"
}
For example, for grafana at version 0.1.3:
