Skip to content

docs: state conformance plainly rather than as a version milestone #7

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jpantsjoha merged 1 commit into from
Aug 7, 2026
Merged

docs: state conformance plainly rather than as a version milestone #7

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down
2 changes: 1 addition & 1 deletion docs/SUBMISSIONS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
Loading