How do I install the Google Agent Registry skill?

Run npx skillmds@latest add solizardking/google-agent-registry-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Google Agent Registry safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Google Agent Registry?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Google Agent Registry free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Google Agent Registry?

Solizardking (@solizardking) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Google Agent Registry by solizardking

Name: Google Agent Registry
Author: Solizardking

Google Agent Registry

Maintain and register Cheshire Google Agent Registry artifacts under registry/google (A2A agent card, MCP tools list, MCP interface, server card, zero-service OpenAPI) and deploy Apigee reverse proxies on project x402-477302. Use for gcloud agent-registry, 10 KB size limits, tool-name parity with server/mcp/tools.ts, Apigee test-env, or validate:google-registry / register:google-agent.

Solizardking Updated Sep 21, 2026 0 repo stars

File contents

Google Agent Registry + Apigee

Operating flow

Edit sources under registry/google/ (never invent tool names)
Keep A2A card + tools list ≤ 10 KB each
pnpm run validate:google-registry
Live register: pnpm run register:google-agent (needs gcloud auth)
Apigee: pnpm run deploy:apigee:myproxy / deploy:apigee:zero

Load details when needed:

references/registry-files.md — file roles, size limits, extensions
references/apigee.md — proxies, hostnames, smoke
scripts/check-registry.sh — local size + parity smoke

Hard rules

Rule	Why
MCP tool `name`s == `createCheshireTools()` `title`s	Registry + live MCP must match
Agent card ≤ 10 KB	Google Agent Registry limit
Tools list ≤ 10 KB	Google Agent Registry limit
Agent card includes MCP interface + discovery extensions	A2A discoverability
Apigee BASE env: STANDARD proxies only	No extensible-only policies on BASE

Commands

pnpm run validate:google-registry
pnpm run register:google-agent
pnpm run deploy:apigee:myproxy
pnpm run deploy:apigee:zero

# Local skill script (size + key fields)
bash skills-store/google-agent-registry/scripts/check-registry.sh

Live probes

curl -sS https://cheshireterminal.ai/.well-known/agent-card.json | head -c 200
curl -sS https://34.54.168.40.nip.io/myproxy
curl -sS https://34.54.168.40.nip.io/zero/health

Project facts

Key	Value
GCP project	`x402-477302`
Location	`us-central1`
A2A service	`cheshire-terminal`
MCP service	`cheshire-terminal-mcp`
ADK `ApiRegistry.get_toolset`	`projects/x402-477302/locations/us-central1/mcpServers/agentregistry-00000000-0000-0000-2490-10e4bb2ec4c0`
Agent Registry service	`projects/x402-477302/locations/us-central1/services/cheshire-terminal-mcp`
Apigee env	`test-env` (BASE)
Env hostname	`34.54.168.40.nip.io`
Zero-service	Cloud Run `clawd-zero-service` (us-central1)

Canonical path file: registry/google/canonical-mcp-resource.json
ADK sample: python3 scripts/google-cloud/adk_cheshire_mcp_agent.py --print-path-only

Full GCP map: repo GOOGLE.md.

When tools change

Update server/mcp/tools.ts
Sync registry/google/cheshire-mcp-tools-list.json
Update agent card skills list if user-facing capabilities changed
Re-run validate:google-registry
Re-register if publishing to Google Agent Registry

---name: google-agent-registry-2description: Maintain and register Cheshire Google Agent Registry artifacts under registry/google (A2A agent card, MCP tools list, MCP interface, server card, zero-service OpenAPI) and deploy Apigee reverse proxies on project x402-477302. Use for gcloud agent-registry, 10 KB size limits, tool-name parity with server/mcp/tools.ts, Apigee test-env, or validate:google-registry / register:google-agent.license: MIT---# Google Agent Registry + Apigee## Operating flow1. Edit sources under `registry/google/` (never invent tool names)2. Keep A2A card + tools list **≤ 10 KB** each3. `pnpm run validate:google-registry`4. Live register: `pnpm run register:google-agent` (needs gcloud auth)5. Apigee: `pnpm run deploy:apigee:myproxy` / `deploy:apigee:zero`Load details when needed:- [references/registry-files.md](references/registry-files.md) — file roles, size limits, extensions- [references/apigee.md](references/apigee.md) — proxies, hostnames, smoke- [scripts/check-registry.sh](scripts/check-registry.sh) — local size + parity smoke## Hard rules| Rule | Why ||------|-----|| MCP tool `name`s == `createCheshireTools()` `title`s | Registry + live MCP must match || Agent card ≤ 10 KB | Google Agent Registry limit || Tools list ≤ 10 KB | Google Agent Registry limit || Agent card includes MCP interface + discovery extensions | A2A discoverability || Apigee BASE env: **STANDARD** proxies only | No extensible-only policies on BASE |## Commands```bashpnpm run validate:google-registrypnpm run register:google-agentpnpm run deploy:apigee:myproxypnpm run deploy:apigee:zero# Local skill script (size + key fields)bash skills-store/google-agent-registry/scripts/check-registry.sh```## Live probes```bashcurl -sS https://cheshireterminal.ai/.well-known/agent-card.json | head -c 200curl -sS https://34.54.168.40.nip.io/myproxycurl -sS https://34.54.168.40.nip.io/zero/health```## Project facts| Key | Value ||-----|-------|| GCP project | `x402-477302` || Location | `us-central1` || A2A service | `cheshire-terminal` || MCP service | `cheshire-terminal-mcp` || ADK `ApiRegistry.get_toolset` | `projects/x402-477302/locations/us-central1/mcpServers/agentregistry-00000000-0000-0000-2490-10e4bb2ec4c0` || Agent Registry service | `projects/x402-477302/locations/us-central1/services/cheshire-terminal-mcp` || Apigee env | `test-env` (BASE) || Env hostname | `34.54.168.40.nip.io` || Zero-service | Cloud Run `clawd-zero-service` (us-central1) |Canonical path file: `registry/google/canonical-mcp-resource.json` ADK sample: `python3 scripts/google-cloud/adk_cheshire_mcp_agent.py --print-path-only`Full GCP map: repo `GOOGLE.md`.## When tools change1. Update `server/mcp/tools.ts`2. Sync `registry/google/cheshire-mcp-tools-list.json`3. Update agent card skills list if user-facing capabilities changed4. Re-run `validate:google-registry`5. Re-register if publishing to Google Agent Registry

Frequently asked questions