From e3daa0d90fa2686c96c16a76e43d36bc67583734 Mon Sep 17 00:00:00 2001 From: JP Date: Fri, 7 Aug 2026 12:25:36 +0100 Subject: [PATCH 1/2] docs: refresh submission targets for v0.2.0 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The tracker still said "ready to submit" for a hub listing that has been live for two weeks, and its release checkbox pointed at an untagged v0.1.0. Adds the Anthropic official marketplace as a target — named by ClaudePluginHub's own guide as complementary, not competing — and records that the hub re-indexes on a schedule with no self-service refresh, so the listing still shows v0.1.0 until it re-crawls. Also pins the standards note at the top: layout advice written for a single client is a subset of what we ship, and client-specific keys such as `when_to_use` must never reach SKILL.md frontmatter, because the Agent Skills field set is closed and a conformant client MUST skip a skill carrying extras. --- docs/SUBMISSIONS.md | 31 +++++++++++++++++++++++++++---- 1 file changed, 27 insertions(+), 4 deletions(-) diff --git a/docs/SUBMISSIONS.md b/docs/SUBMISSIONS.md index 45a573c..c26d66e 100644 --- a/docs/SUBMISSIONS.md +++ b/docs/SUBMISSIONS.md @@ -2,6 +2,14 @@ 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) +> 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 +> stay alongside the portable `plugin.json` + `mcp.json`. Never add client-specific keys to SKILL.md frontmatter +> (e.g. `when_to_use`) — the Agent Skills field set is closed and a conformant client MUST skip a skill that +> carries extras. + ## 1. Claude Plugin Hub — primary (Claude Code) - **Where:** https://www.claudepluginhub.com @@ -12,7 +20,11 @@ Where to list `googlecloud-plugin` so builders can find and install it. Each ent /plugin marketplace add jpantsjoha/googlecloud-plugin /plugin install googlecloud-plugin@googlecloud-plugin-marketplace ``` -- **Status:** ready to submit. +- **Re-index:** the hub auto-discovers on a schedule (GitHub Code Search backed), but submitting the repo URL + at https://www.claudepluginhub.com is the fastest route. Its own guide: *"Push your plugin to GitHub and + submit the URL for the fastest route to indexing."* +- **Status:** **LISTED** and verified owner. Showing v0.1.0 as of 2026-08-07 — awaiting re-crawl of the + v0.2.0 release. No self-service refresh control exists on the listing page. ## 2. Gemini CLI Extensions — Antigravity / Gemini @@ -24,13 +36,20 @@ Where to list `googlecloud-plugin` so builders can find and install it. Each ent ``` - **Status:** validated locally (`agy plugin validate .` → 17 skills + 2 mcpServers). Ready to request listing. -## 3. awesome-claude-code — community list +## 3. Anthropic official marketplace — canonical Claude listing + +- **Where:** https://claude.ai/settings/plugins/submit or https://platform.claude.com/plugins/submit +- **Needs:** public repo with `.claude-plugin/plugin.json` + `marketplace.json` (both present and valid). +- **Note:** complementary to Claude Plugin Hub, not competing — per the hub's own guidance. +- **Status:** not yet submitted. Eligible now that v0.2.0 is tagged and released. + +## 4. awesome-claude-code — community list - **Where:** https://github.com/hesreallyhim/awesome-claude-code - **Needs:** a PR adding the repo under the plugins/skills section, one-line description. - **Status:** ready — draft the PR entry. -## 4. MCP servers registry — optional (MCP angle) +## 5. MCP servers registry — optional (MCP angle) - **Where:** https://github.com/modelcontextprotocol/servers - **Needs:** only relevant if we surface the bundled MCP setup as a standalone entry; the plugin mainly *consumes* MCP servers rather than *being* one. Low priority. @@ -46,4 +65,8 @@ Where to list `googlecloud-plugin` so builders can find and install it. Each ent - [x] Repo description + 20 topics set - [x] `make gate` green in CI (gate.yml) - [x] "Not affiliated with Google" disclaimer in README -- [ ] Tag a release (`v0.1.0`) before submitting +- [x] Tag a release before submitting — `v0.2.0` tagged and released 2026-08-07 +- [x] Conforms to Agent Plugins 1.0.0 (`make spec`) and Agent Skills (`skills-ref` 17/17) +- [x] `CHANGELOG.md` present; version bumped so clients invalidate their cache +- [ ] Submit repo URL to Claude Plugin Hub to trigger re-index of v0.2.0 +- [ ] Submit to Anthropic official marketplace From 1a952078604418dd0f4b1bc35f9dccc34e69419d Mon Sep 17 00:00:00 2001 From: JP Date: Fri, 7 Aug 2026 12:27:00 +0100 Subject: [PATCH 2/2] docs: cite Agent Plugins 1.0.0 conformance at the top of the README The claim was only visible at line 149, below install and workflow sections. Anyone scanning the repo to decide whether it is worth installing never reached it. Adds two badges beside the existing ClaudePluginHub one and a sentence in the opening blurb naming the standard, who maintains it, what conformance buys the reader, and how it is enforced. --- README.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/README.md b/README.md index ec6e4bb..0455f72 100644 --- a/README.md +++ b/README.md @@ -3,6 +3,9 @@

[![Listed on ClaudePluginHub](https://www.claudepluginhub.com/badge/jpantsjoha-googlecloud-plugin)](https://www.claudepluginhub.com/plugins/jpantsjoha-googlecloud-plugin?ref=badge) +[![Agent Plugins 1.0.0](https://img.shields.io/badge/Agent%20Plugins-1.0.0%20conformant-4285F4)](https://agent-plugins.org/specification) +[![Agent Skills](https://img.shields.io/badge/Agent%20Skills-conformant-34A853)](https://agentskills.io/specification) + # GoogleCloud Plugin > **Install once, and your coding agent gains a full Google Cloud delivery team — a vendor-objective solution designer, a GCP architect, an agentic-systems architect, plus security, SRE, and QA — wired into a design-first, security-first delivery gate.** @@ -13,6 +16,8 @@ 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). + 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. > **Speed is easy. Safe speed is engineered.**