Source: google/agents-cli · Maintainer: Google · License: Apache-2.0 · Checked: 26 October 2026
What is the google-agents-cli-observability skill?
google-agents-cli-observability is an Agent Skill that teaches a coding agent how to monitor AI agents built and deployed with the agents-cli command. It covers Cloud Trace, prompt-response logging, the BigQuery Agent Analytics plugin, third-party platforms and common problems.
It is one of seven skills in google/agents-cli, Google's "CLI and skills for building agents on Gemini platform." In the workflow skill it is Phase 7, after deploy. The SKILL.md description says not to use it for deployment setup or API code patterns.
As of 26 October 2026, its skills.sh page listed about 511,700 installs (snapshot, 26 October 2026). The SKILL.md metadata lists Google as author and version 1.11.0.
What does it do?
The SKILL.md is organized around four tiers and tells the agent to ask you which ones you need. Cloud Trace is always on and the rest are additive.
| Tier | What it captures | Scope | Default |
|---|---|---|---|
| Cloud Trace | Execution flow, latency and errors as OpenTelemetry spans | All templates, all environments | Always on |
| Prompt-response logging | GenAI interactions to GCS, BigQuery and Cloud Logging | Scaffolded ADK Python projects | Off locally, on when deployed |
| BigQuery Agent Analytics | Structured agent events such as LLM calls and tool use | ADK Python with the plugin | Opt-in with --bq-analytics |
| Third-party integrations | Telemetry in external platforms | Any OpenTelemetry-instrumented agent | Opt-in per provider |
Cloud Trace
For ADK, spans nest as invoke_workflow, then invoke_agent, then call_llm (with generate_content) and execute_tool. Setup is automatic for Agent Runtime and scaffolded Cloud Run or GKE projects; manual deployments configure their own exporter. You view traces in the Cloud Console under Trace explorer. Google's Cloud Trace page in the agents-cli docs covers the same setup.
Prompt-response logging
This tier needs Terraform-provisioned resources: a service account, a GCS bucket and a BigQuery dataset. The skill says to run agents-cli infra single-project --apply --project PROJECT_ID to create them, before agents-cli deploy.
Content capture has two independent tiers. GCS and BigQuery completions capture full prompts and responses when OTEL_INSTRUMENTATION_GENAI_COMPLETION_HOOK=upload and LOGS_BUCKET_NAME are set. Trace spans and log events are governed by OTEL_INSTRUMENTATION_GENAI_CAPTURE_MESSAGE_CONTENT, which defaults to NO_CONTENT. In the skill's words, the net Terraform-deploy default is "full content in GCS/BigQuery, none in traces."
BigQuery Agent Analytics and feedback
The optional ADK plugin writes structured events to BigQuery for conversational analytics, LLM-as-judge evals, Looker Studio dashboards and tool provenance. A reference file also shows how to add a user-feedback endpoint whose structured logs flow through a log sink into BigQuery.
Third-party platforms
A comparison table covers AgentOps, Arize AX, Phoenix, MLflow, Monocle, Weave and Freeplay, with setup complexity and whether each can be self-hosted. The skill points to the ADK integrations directory for the full list.
Four reference files support it: cloud-trace-and-logging.md, bigquery-agent-analytics.md, feedback-mechanism.md and adk-docs.md.
How do you install it?
The Getting Started guide lists Python 3.11+, uv and Node.js as prerequisites, with the Google Cloud SDK and Terraform as optional extras for deployment. The recommended install adds the CLI and all seven skills:
uvx google-agents-cli setup
Or install skills only, either the whole set or just this one (the command shown on skills.sh):
npx skills add google/agents-cli
npx skills add https://github.com/google/agents-cli --skill google-agents-cli-observability
The skill's metadata lists the agents-cli binary as a requirement, installed with uv tool install google-agents-cli. It assumes a project scaffolded with agents-cli. In Claude Code, run /skills to confirm the agents-cli skills are listed. Codex and Cursor read the same SKILL.md format; see Codex skills and Cursor skills.
How do you use it?
The skill loads when you ask to "set up tracing", "monitor my agent", "configure logging", "add observability" or "debug production traffic", per its description. You can also call /google-agents-cli-observability in Claude Code.
Example prompts (suggestions, not quotes from the repo):
Set up observability for this agent before the first deploy. Ask me which tiers I need.No traces show up in Cloud Trace for the Cloud Run deployment. Check the likely causes.Keep prompt content out of traces but keep full completions in BigQuery. What do I set?Add a thumbs up and thumbs down feedback endpoint and route it to BigQuery.Compare Phoenix and MLflow for this agent. We need a self-hosted option.
Tips and limits
From the SKILL.md, the repo docs and skills.sh, not from testing:
- Order matters. For Terraform-managed observability, run
infra single-project --applyfirst, thendeploy. If you already deployed imperatively, the skill says: "Do not apply Terraform afterward." - Full content is stored by default. Completions in GCS and BigQuery capture full prompts and responses and ignore the content-capture variable. To stop that, remove the upload variables.
- Python and Go differ. ADK Python reads the content variable as an enum (
NO_CONTENT,EVENT_ONLY,SPAN_ONLY,SPAN_AND_EVENT) and treatstrueorfalseas invalid. ADK Go reads it as a boolean. - Some platforms replace native telemetry. The skill notes this for AgentOps.
- Costs. For high telemetry costs, it suggests turning content capture off, reducing BigQuery retention and disabling unused tiers. Resources are created in your own Google Cloud project.
- Security audits. On skills.sh, Gen Agent Trust Hub rated it Pass with risk level Safe (22 October 2026); its report flags free-text user feedback logged to BigQuery as an ingestion point for untrusted data and lists PII redaction or table expiration as mitigations. Socket (20 October 2026) and Snyk (risk level Low, 20 October 2026) rated it Pass.
Under Apache 2.0 you can copy and modify the skill as long as you keep the license and notices and mark files you change.
Save it in your Kipt library
In Kipt, open Skills and paste the skill's GitHub folder link to import it with its four reference files, or paste the repo link and pick from the list of all seven agents-cli skills. You can also drop the folder or a .zip. Your skills live in your own private GitHub repo and install into Claude Code or Codex with one command:
npx skills add https://github.com/<you>/<repo>.git --all -g
Kipt is not affiliated with Google.
Similar skills
- google-agents-cli-deploy skill: deploys the agent you then observe.
- google-agents-cli-eval skill: turns production problems into eval cases.
- google-agents-cli-workflow skill: the lifecycle, with observability as Phase 7.
- google-agents-cli-scaffold skill: add
--bq-analyticsat scaffold time. - Azure diagnostics skill: production troubleshooting with Azure Monitor, if you also run on Azure.
- Microsoft Foundry skill: agent deploys and evals on Azure.