From 3c4334db271da9fd460c67ff32681ba985f75d2c Mon Sep 17 00:00:00 2001 From: JP Date: Fri, 7 Aug 2026 12:28:31 +0100 Subject: [PATCH] docs: state conformance plainly rather than as a version milestone "As of v0.2.0 this plugin conforms to..." reads as an admission that it did not before. For a reader deciding whether to install, the relevant fact is the present one: it is compliant with the standard. Version history belongs in the changelog, which keeps its dated framing. Applies the same correction to the standards note in docs/SUBMISSIONS.md, which carried the identical phrasing. --- README.md | 2 +- docs/SUBMISSIONS.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 0455f72..aa9d5b9 100644 --- a/README.md +++ b/README.md @@ -16,7 +16,7 @@ Skill libraries for Google Cloud are everywhere. What they miss is the operating One install gives an agent (Claude, Codex, or Antigravity) six personas, eleven service skills, and a research pipeline that keeps every reference current. A plugin that goes stale in silence is worse than none. -**As of v0.2.0 this plugin conforms to [Agent Plugins 1.0.0](https://agent-plugins.org/specification)** — the open, vendor-neutral packaging standard co-maintained by Amazon, Cursor, Google, Microsoft, OpenAI and Vercel ([announcement](https://developers.googleblog.com/agent-plugins-package-your-skills-tools-and-more/)) — and to the [Agent Skills specification](https://agentskills.io/specification) it references. That means one directory layout works across conformant clients, rather than a bespoke wrapper per harness. Conformance is enforced in CI by `make spec` and verified against the official reference validator; see [Standards and compliance](#standards-and-compliance). +**Compliant with [Agent Plugins 1.0.0](https://agent-plugins.org/specification)** — the open, vendor-neutral packaging standard co-maintained by Amazon, Cursor, Google, Microsoft, OpenAI and Vercel ([announcement](https://developers.googleblog.com/agent-plugins-package-your-skills-tools-and-more/)) — and with the [Agent Skills specification](https://agentskills.io/specification) it references. One directory layout works across conformant clients, rather than a bespoke wrapper per harness. Enforced in CI by `make spec` and verified against the official reference validator; see [Standards and compliance](#standards-and-compliance). The plugin is **GCP-only and opinionated by design**. It covers the services a builder reaches for — Firebase, Cloud Run, BigQuery, GKE — and the agent frameworks now built on top: ADK, and the MCP / A2A / AP2 protocol stack, deployed on the Gemini Enterprise Agent Platform. Refine it for your team. Keep the contract coherent as you do. diff --git a/docs/SUBMISSIONS.md b/docs/SUBMISSIONS.md index c26d66e..dd826e6 100644 --- a/docs/SUBMISSIONS.md +++ b/docs/SUBMISSIONS.md @@ -2,7 +2,7 @@ Where to list `googlecloud-plugin` so builders can find and install it. Each entry has the destination, what it needs, and the status. -> **Standards note.** As of v0.2.0 this plugin conforms to [Agent Plugins 1.0.0](https://agent-plugins.org/specification) +> **Standards note.** This plugin is compliant with [Agent Plugins 1.0.0](https://agent-plugins.org/specification) > and the [Agent Skills specification](https://agentskills.io/specification) — the vendor-neutral standards > ([announcement](https://developers.googleblog.com/agent-plugins-package-your-skills-tools-and-more/)). > Directory-layout advice written for a single client is a *subset* of what we ship: the per-harness manifests