/google-cloud-solution-agentic-ai-bidirectional-streaming
Guides agents to interactively discover customer requirements for live, bidirectional multi-agent AI systems that process continuous streams of multimodal data for real-time technical guidance and safety monitoring. Generates a custom Google Cloud solution that uses opinionated
$ npx -y skills add google/skills --skill google-cloud-solution-agentic-ai-bidirectional-streaming --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/google-cloud-solution-agentic-ai-bidirectional-streaming
Context preview
The summary Claude sees to decide when to auto-load this skill.
Guides agents to interactively discover customer requirements for live, bidirectional multi-agent AI systems that process continuous streams of multimodal data for real-time technical guidance and safety monitoring. Generates a custom Google Cloud solution that uses opinionated
SKILL.md
google-cloud-solution-agentic-ai-bidirectional-streaming.SKILL.mdname: google-cloud-solution-agentic-ai-bidirectional-streaming
metadata:
category: MultiProductSolutions
description: >-
Guides agents to interactively discover customer requirements
for live, bidirectional multi-agent AI systems that process continuous streams
of multimodal data for real-time technical guidance and safety monitoring.
Generates a custom Google Cloud solution that uses opinionated best practices
and architecture guidance. Use when users need agentic assistance to design
and create a multi-product solution in the cloud for live bidirectional
multimodal streaming workloads. Don't use for simple text-based chat
applications or workloads without real-time streaming requirements.
Live bidirectional multimodal streaming agentic AI solution
This skill guides agents through the workflow to design and implement a tailored multi-product solution in the cloud for a live, bidirectional multimodal streaming workload, use case, or requirement.
Workflow
The solution design and implementation workflow consists of the following phases:
- **Phase 1: Requirements discovery and analysis**: Analyze the workload's
requirements, constraints, dependencies, and current state.
- **Phase 2: Solution design**: Build a technology stack, architecture, and
deployment configuration for the workload based on Google Cloud design best practices and recommendations.
- **Phase 3: Implementation plan**: Generate automation and instructions to
deploy the solution.
- **Phase 4: Solution validation**: Validate that the deployment meets the
requirements of the workload.
Phase 1: Requirements discovery and analysis
- [ ] **Step 1: Discover requirements**: Understand the functional and
non-functional requirements, business goals, and current state (if any) of the workload, including its architecture, dependencies, and constraints. Use the following questions to guide the requirements discovery process:
- What are the primary input modalities (audio, video, or text) and
what is the target latency for real-time, narrated feedback?
- Do you require real-time safety monitoring, hazard detection, or visual
inspection? If so, then what specific safety hazards, operational risks, or incorrect steps need to be monitored and detected in the video stream?
- What existing systems, knowledge bases, product documentation, or
schematic repositories must the AI agents access for grounded guidance?
- What are the client-side device constraints and network limitations?
- [ ] **Step 2: Identify components**: Based on the requirements analysis,
identify the components of the workload and their relationships. Also identify any cross-cloud components, hybrid components, or on-prem components that the solution needs to integrate with.
- [ ] **Step 3: Generate component decomposition**: Generate a technical
decomposition of the components of the workload. The technical decomposition must break down the solution into logical components.
- [ ] **Step 4: Ask for confirmation**: Ask the user to confirm whether the
generated technical decomposition matches their workload requirements.
- [ ] **Step 5: Iterate**: If the user requests changes, then generate an
updated technical decomposition, and ask the user to confirm the changes. Continue iterating until the user confirms the technical decomposition.
Phase 2: Solution design
- [ ] **Step 1: Retrieve relevant Google Cloud documentation**:
- [Enable live bidirectional multimodal streaming](https://docs.cloud.google.com/architecture/agentic-ai-bidirectional-multimodal-streaming.md.txt)
- [Multi-agent AI system in Google Cloud](https://docs.cloud.google.com/architecture/multiagent-ai-system.md.txt)
- [Choose your agentic AI architecture components](https://docs.cloud.google.com/architecture/choose-agentic-ai-architecture-components.md.txt)
- [Multi-agent private networking patterns in Google Cloud](https://docs.cloud.google.com/architecture/multi-agent-private-networking-patterns.md.txt)
*Important*: Use the content that you retrieve from Google Cloud documentation to ground the guidance that you generate in the remaining steps of this phase.
- [ ] **Step 2: Map components to Google Cloud products**: For each component in
the confirmed technical decomposition and agentic design pattern, identify the appropriate Google Cloud products and features, based on the guidelines in [references/product-mapping.md](references/product-mapping.md).
- [ ] **Step 3: Create architecture diagram**: Generate an architecture diagram
in Mermaid format: https://github.com/mermaid-js/mermaid.
- [ ] **Step 4: Generate design recommendations**: Generate design guidance
based on the guidelines in [references/design-recommendations.md](references/design-recommendations.md).
- [ ] **Step 5: Draft solution architecture**: Compile the requirements, technical
decomposition, product mapping, architecture diagram, and design recommendations into a single Markdown file named `solution-architecture-guide.md`, based on the template in [assets/output-template.md](assets/output-template.md).
- [ ] **Step 6: Request review**: Present the generated solution architecture to
the user and request their feedback or approval.
- [ ] **Step 7: Iterate**: If the user requests changes, generate an updated
solution architecture and repeat steps 2-6 until the user approves the solution architecture.
Phase 3: Implementation plan
- [ ] **Step 1: Retrieve relevant implementation resources**:
- [Host AI agents on Cloud Run](https://docs.cloud.google.com/run/docs/ai-agents.md.txt)
- [Triggering Cloud Run with WebSockets](https://docs.cloud.google.com/run/docs/triggering/websockets.md.txt)
- [Start and Manage a Gemini Live API Session](https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/live-api/start-manage-session.md.txt)
- [A
Read more
name: google-cloud-solution-agentic-ai-bidirectional-streaming metadata: category: MultiProductSolutions description: >- Guides agents to interactively discover customer requirements for live, bidirectional multi-agent AI systems that process continuous streams of multimodal data for real-time technical guidance and safety monitoring. Generates a custom Google Cloud solution that uses opinionated best practices and architecture guidance. Use when users need agentic assistance to design and create a multi-product solution in the cloud for live bidirectional multimodal streaming workloads. Don't use for simple text-based chat applications or workloads without real-time streaming requirements.
Live bidirectional multimodal streaming agentic AI solution
This skill guides agents through the workflow to design and implement a tailored multi-product solution in the cloud for a live, bidirectional multimodal streaming workload, use case, or requirement.
Workflow
The solution design and implementation workflow consists of the following phases:
- **Phase 1: Requirements discovery and analysis**: Analyze the workload's
requirements, constraints, dependencies, and current state.
- **Phase 2: Solution design**: Build a technology stack, architecture, and
deployment configuration for the workload based on Google Cloud design best practices and recommendations.
- **Phase 3: Implementation plan**: Generate automation and instructions to
deploy the solution.
- **Phase 4: Solution validation**: Validate that the deployment meets the
requirements of the workload.
Phase 1: Requirements discovery and analysis
- [ ] **Step 1: Discover requirements**: Understand the functional and
non-functional requirements, business goals, and current state (if any) of the workload, including its architecture, dependencies, and constraints. Use the following questions to guide the requirements discovery process:
- What are the primary input modalities (audio, video, or text) and
what is the target latency for real-time, narrated feedback?
- Do you require real-time safety monitoring, hazard detection, or visual
inspection? If so, then what specific safety hazards, operational risks, or incorrect steps need to be monitored and detected in the video stream?
- What existing systems, knowledge bases, product documentation, or
schematic repositories must the AI agents access for grounded guidance?
- What are the client-side device constraints and network limitations?
- [ ] **Step 2: Identify components**: Based on the requirements analysis,
identify the components of the workload and their relationships. Also identify any cross-cloud components, hybrid components, or on-prem components that the solution needs to integrate with.
- [ ] **Step 3: Generate component decomposition**: Generate a technical
decomposition of the components of the workload. The technical decomposition must break down the solution into logical components.
- [ ] **Step 4: Ask for confirmation**: Ask the user to confirm whether the
generated technical decomposition matches their workload requirements.
- [ ] **Step 5: Iterate**: If the user requests changes, then generate an
updated technical decomposition, and ask the user to confirm the changes. Continue iterating until the user confirms the technical decomposition.
Phase 2: Solution design
- [ ] **Step 1: Retrieve relevant Google Cloud documentation**:
- [Enable live bidirectional multimodal streaming](https://docs.cloud.google.com/architecture/agentic-ai-bidirectional-multimodal-streaming.md.txt)
- [Multi-agent AI system in Google Cloud](https://docs.cloud.google.com/architecture/multiagent-ai-system.md.txt)
- [Choose your agentic AI architecture components](https://docs.cloud.google.com/architecture/choose-agentic-ai-architecture-components.md.txt)
- [Multi-agent private networking patterns in Google Cloud](https://docs.cloud.google.com/architecture/multi-agent-private-networking-patterns.md.txt)
*Important*: Use the content that you retrieve from Google Cloud documentation to ground the guidance that you generate in the remaining steps of this phase.
- [ ] **Step 2: Map components to Google Cloud products**: For each component in
the confirmed technical decomposition and agentic design pattern, identify the appropriate Google Cloud products and features, based on the guidelines in [references/product-mapping.md](references/product-mapping.md).
- [ ] **Step 3: Create architecture diagram**: Generate an architecture diagram
in Mermaid format: https://github.com/mermaid-js/mermaid.
- [ ] **Step 4: Generate design recommendations**: Generate design guidance
based on the guidelines in [references/design-recommendations.md](references/design-recommendations.md).
- [ ] **Step 5: Draft solution architecture**: Compile the requirements, technical
decomposition, product mapping, architecture diagram, and design recommendations into a single Markdown file named `solution-architecture-guide.md`, based on the template in [assets/output-template.md](assets/output-template.md).
- [ ] **Step 6: Request review**: Present the generated solution architecture to
the user and request their feedback or approval.
- [ ] **Step 7: Iterate**: If the user requests changes, generate an updated
solution architecture and repeat steps 2-6 until the user approves the solution architecture.
Phase 3: Implementation plan
- [ ] **Step 1: Retrieve relevant implementation resources**:
- [Host AI agents on Cloud Run](https://docs.cloud.google.com/run/docs/ai-agents.md.txt)
- [Triggering Cloud Run with WebSockets](https://docs.cloud.google.com/run/docs/triggering/websockets.md.txt)
- [Start and Manage a Gemini Live API Session](https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/live-api/start-manage-session.md.txt)
- [A
This repository contains Agent Skills for Google products and technologies, including Google Cloud. This repository is under active development.
Repo: google/skills
Other skills on google-skills.
- /data-manager-api-audience-ingestion
Guides developers through managing (adding, removing, and clearing) audience members for Google products using the Data Manager API and its associated client libraries. Use this skill when the user wants to upload audience members, remove specific users, or clear/replace an
Open skill - /data-manager-api-event-ingestion
Guides developers through implementing event and conversion ingestion to Google products using the Data Manager API /v1/events/ingest endpoint and its associated client libraries. Use this skill when the user wants to upload offline conversions, enhanced conversions for leads,
Open skill - /data-manager-api-setup
Guides developers through client library installation and authentication setup steps for the Data Manager API. Use this skill when a user is getting started with the Data Manager API and needs to setup their local environment, install the client library, or setup access to the
Open skill - /google-ads-api-account-diagnostics
Diagnoses Google Ads account performance issues such as conversion loss (value or volume), low lead flow/volume, and lost impression share (opportunities) due to ad rank, bids, or budgets. Use when troubleshooting sudden performance drops, analyzing campaign impression share
Open skill - /google-ads-api-mcp-setup
Guides developers through downloading, configuring, and installing the official open-source Google Ads MCP Server. Use this skill when a user wants to connect their AI assistant (such as Gemini, Claude Code, or Cursor) to their Google Ads account to query campaigns or retrieve
Open skill - /google-ads-api-quickstart
Guides developers through Google Ads API quickstart: credential setup, choosing from 6 client libraries/REST, configuring environments, and running a "retrieve campaigns" script. Troubleshoots common setup errors: USER_PERMISSION_DENIED, login_customer_id issues, and
Open skill

