Cloud IX Team
a7123f8052
Two lists in this repository had drifted from what they describe, for the same reason. Both are maintained by hand and nothing makes you update them when the thing they describe changes. The google-cloud-developer rules file opened with "This plugin installs three skills" and named three. The plugin ships five. The count was correct when it was written and went stale the moment the plugin gained a skill, which is a defect that will recur every time it gains another. Rather than correct the number, the paragraph no longer states one. It tells the agent to check what is actually available instead of trusting the file. A count that is not written down cannot go out of date. The same file closed by telling the agent to browse GitHub and install through npx to find more skills. The plugin now bundles finding-google-skills, which fetches the current index and returns exact entry points, so that advice routed agents around the better tool. It now prefers the bundled skill and keeps the browse URL as a fallback. The two marketplace manifests describe one marketplace and had drifted apart. The Claude manifest listed seventeen plugins and the agents manifest sixteen, with db-context-engineering present in the first and missing from the second. Whoever added it updated one file and missed the other. Three conformance cases now hold this ground: A rules file that names two or more bundled skills is treated as enumerating them and must name all of them. One mention is a reference, not a list, so a file may point at a single skill by name without triggering the check. A rules file that states how many skills a plugin installs must state the right number, whether written as a digit or a word. The two marketplace manifests must list the same set of plugins. The first two cases skip when a rules file makes no such claim, so the fix above costs nothing to keep and the checks only bite if someone writes a hardcoded list back in. PiperOrigin-RevId: 972849207
1.4 KiB
trigger, description
| trigger | description |
|---|---|
| always_on | Routing map for the Google Cloud skill catalog. |
Google Cloud Skill Routing
This plugin installs a small subset of the Google Cloud skills. Check which ones are actually available to you rather than assuming from this file. Many more exist in the same public catalog and are not installed here - you cannot read or load those from this plugin.
When a request needs depth the installed skills do not cover, name the likely catalog skill and offer to install it. Catalog names are predictable:
gke-*- GKE clusters, networking, storage, scaling, cost, AI inference, troubleshootingagent-platform-*- model deploy, tuning, RAG, eval, endpoints, promptsgoogle-cloud-solution-*- multi-product reference architecturesgoogle-cloud-waf-*- Well-Architected Framework pillarsgenkit-*,gemini-*- Genkit SDKs, Gemini APIscloud-logging-*,cloud-monitoring-*- observability<product>-basics- BigQuery, Bigtable, Spanner, AlloyDB, Cloud SQL, Cloud Run, Firebase, Storage
If finding-google-skills is available to you, use it to search the catalog
rather than guessing from the prefixes above; it fetches the current index and
returns exact entry points. Otherwise browse
https://github.com/google/skills/tree/main/skills/cloud
Never infer a skill's contents from its name. If an answer needs a skill you cannot read, say so instead of answering from memory.