For Agents · MCP

Your task.
The right skill.

The tunnel uses the same cards as the catalogue. Browse only as deep as needed — or load a broad bundle immediately.

No local installationNo M11 loginRead-only

Broad task

Load 5–10 and go

SEO, Sales, Agents or another broad area → one bundle call → work.

MCP endpoint: https://skills.m11.ch/mcp

Read-only access to published skills. Default 8, maximum 10 skills / 120,000 characters.

Task Packs

Marketing Foundation

Compact two-skill starter: clarify positioning and choose a lead magnet. Use Marketing Launch for the broader eight-skill go-to-market workflow.

Marketing Launch

Build an evidence-led marketing plan from ICP and competition through positioning, campaigns, growth and measurement.

Agent Audit Essentials

Diagnose architecture and context, plan agent-team responsibilities, then organize project context and session handoffs. Memory and cost-runtime reviews remain outside this pack.

Conversion and Activation Review

Review the journey from landing page and lead capture through registration, first value and transparent upgrades.

Campaign Content and Brand Review

Plan a campaign, draft its channel content and review the work against actual brand guidance.

Content and Launch Planning

Prioritize an editorial roadmap and plan how to launch and distribute it across suitable channels.

Customer, Market and Community Research

Understand customer needs, compare competitors and plan a community around real member value.

Lead Magnet to Lifecycle Nurture

Choose a relevant lead magnet, then draft a permission-based nurture journey with entry, suppression and exit rules.

API Contract and Observability

Define the API contract, then plan how to observe its latency, failures and retries. Guidance and checklist; no production changes.

Data Analysis Foundation

Profile a dataset, choose and interpret statistical methods, then validate calculations and conclusions before sharing.

Choose an area

01 · Category

What the MCP returns at this step

11 · Engineering · Cloud Architecture

Google Cloud Solution Architecture

Design cross-product Google Cloud solutions and review deployment plans; use Multi-Agent Deployment Design for agent-specific systems.

cloudloesungsarchitekturgoogle-cloud-solution-architecture

Google Cloud Solution Architecture · Original SKILL.md

---
name: google-cloud-solution-architecture
metadata:
version: "1.0.2"
category: MultiProductSolutions
description: >-
Interactively discovers requirements and designs holistic, multi-product
system architectures, solution blueprints, and deployment recommendations for
complex workloads on Google Cloud. Use when designing end-to-end cloud
solutions, selecting and integrating Google Cloud services, generating
architecture diagrams, or conducting requirements discovery for new cloud
workloads or migrations. Don't use for single-product tasks (use
product-specific skills), initial onboarding or authentication (use
google-cloud-recipe-*), Well-Architected Framework reviews or audits (use
google-cloud-waf-*), or workloads covered by specialized solution skills.
---

# Google Cloud solution-architecture workflow

## Overview of the workflow

The workflow consists of the following phases:

* **Phase 1: Requirements discovery**. Gather detailed requirements related to
the cloud workload or use case that the user needs assistance for.
* **Phase 2: Solution architecture**. Use the requirements that were gathered
in Phase 1 to generate a detailed solution architecture for the cloud
workload or use case.
* **Phase 3: Solution validation**. Create a plan to validate the generated
solution, generate validation instructions and scripts, and provide them to
the user to execute (or perform a dry-run validation with explicit
permission from the user).
* **Phase 4: Solution packing and presentation**. Consolidate the generated
content and present the solution.

**Important notes about the workflow**:

* **Strict phase separation**: During Phase 1 (Requirements discovery), when
you ask the user clarifying questions, don't recommend, propose, or outline
any architectural designs, technical decompositions, cloud services, or
component mappings. Proposing solutions before functional and non-functional
requirements are thoroughly assessed causes confirmation bias and risks
anchoring the solution on specific products, features, or tools prematurely.

* **Iterative approval & task transitions**: For each deliverable in this
workflow (technical decompositions, product recommendations, diagrams,
architectural descriptions, and deployment scripts), explicitly present your
output to the user for approval. If the user requests modifications,
iteratively revise the content until approved before progressing to the
subsequent task or phase.

* **No autonomous execution of code and scripts**: Don't run any scripts or
code that you generate without explicit, unambiguous permission from the
user. Executing scripts autonomously can provision unintended cloud
resources (incurring unexpected costs), mutate live infrastructure, or pose
security and safety risks. Always offer the option for the user to execute
the commands manually.

* **When you can skip certain phases**: If the user's prompt indicates that a
specific phase or task in this workflow is already completed or approved
(e.g., "requirements discovery stage is completed", "product selection is
approved", or "architecture is confirmed"), don't repeat that phase or task.
Instead, skip directly to the requested task (such as generating the
technical decomposition, recommending products, or compiling the solution
guide).

## Phase 1: Requirements discovery

1. Gather the following requirements related to the workload or use case for
which the user needs assistance.

**CRITICAL**: You MUST NOT generate any architecture designs, product
recommendations, or technical decompositions until the user provides these
requirements.

* **Functional requirements**: Ask the user to describe the business
processes, activities, and use cases of their workload.
* **Non-functional requirements**: Ask the user to describe requirements
for security, privacy, compliance, reliability, disaster recovery, cost,
operations, performance, and sustainability.
* **CRITICAL**: If non-functional requirements are missing or
incomplete, you MUST ask the user to describe the requirements and
explicitly explain why they are important (e.g., because they
directly dictate operational SLAs, availability tiers, scaling
configuration, cost budgets, resource types, and the security
posture) when asking the user to supply them.
* **Current state**: Ask whether the workload currently runs on other
cloud providers or on-premises (if yes, prompt for the architecture of
the existing deployment).
* **System dependencies**: Ask the user to describe any dependencies
between their application and other workloads, products, systems, or
tools.

2. Review the input that the user has provided so far, and check whether there
are any ambiguities or contradictions (e.g., conflicting goals like complete
network isolation with zero internet exposure vs. real-time ingestion from
public APIs).

If you identify any ambiguities or contradictions in the user's
requirements, you must:

* Clearly describe the ambiguities and contradictions.
* Explain why the contradictory requirements cannot be simultaneously
satisfied.
* Request the user to clarify their trade-off preferences and choices to
resolve the ambiguities and contradictions.
* If the user delegates the choice to you (e.g., the user replies with
"do what you think is best" or "you decide"), then provide a clear
suggestion to resolve the ambiguity or contradiction, explain your
reasoning, and ask the user to approve your suggestion.

**CRITICAL**: Until all the ambiguities and contradictions that you identify
are resolved, don't recommend or generate any architecture design, technical
decomposition, or Google Cloud product recommendations. Ambiguous or
contradictory requirements lead to invalid architectural assumptions.

3. Generate a technical decomposition of the components of the workload that
breaks down the solution into logical components. Present it to the user and
obtain approval before proceeding to Phase 2.

**CRITICAL**: Before proceeding to Phase 2, ensure that the user has
approved the technical decomposition. Misalignment of the technical
decomposition with the user's requirements will invalidate the outputs of
the subsequent phases in this workflow.

## Phase 2: Solution architecture

Use the approved requirements from Phase 1 to generate a comprehensive solution
architecture.

### Ground all generated content

For each task in this phase, to ensure that the generated content aligns with
the latest and official Google Cloud guidance, you must ground the generated
content by using the following resources:

* Google Developer Knowledge MCP server
* Server: https://developerknowledge.googleapis.com/mcp
* Tools:
* `developerknowledge:search_documents`
* `developerknowledge:get_documents`
* `developerknowledge:answer_query`
* Relevant skills from https://github.com/google/skills
* Official Google Cloud documentation, including the following:
* Reference architectures and design guides that are relevant to the
technology category of the workload: `references/architecture-guides.md`
* Decision-making guides for the products and topics that are relevant to
the workload: `references/decision-making-guides.md`
* Best-practices guides for the products and topics that are relevant to
the workload: `references/best-practices-guides.md`

For each item in the generated guidance, you must include citations to the
relevant official Google Cloud documentation pages.

### Task 2.1: Identify Google Cloud products and features required for the workload.

1. Recommend the products and features that are appropriate for each component
of the user's workload.

**CRITICAL**:

* Don't recommend any products or features that are deprecated, retired,
decommissioned, or unsupported. To check the status of a product or
feature, call `developerknowledge:answer_query` or
`developerknowledge:search_documents` with query strings like:
"{product_name} release status".
* If multiple products or features can be used for a component of the
workload, then do the following:
* Recommend the most appropriate product or feature. When alternative
products exist, the relevant product documentation might provide
guidance on when to choose each product. Follow that guidance.
* Mention the available alternative products or features.
* Explain the pros and cons of each alternative product or feature.

2. Present the generated product recommendations to the user and ask whether
any changes are needed.

**CRITICAL**: Don't generate anything further (architecture diagrams,
descriptions, or deployment configurations) in the same turn. Halt execution
immediately after listing the product choices until the user approves the
product selections.

3. After the user approves the product selections, proceed to Task 2.2.

### Task 2.2: Generate an architecture diagram.

1. Generate an architecture diagram in Mermaid format:
https://github.com/mermaid-js/mermaid.
2. Present the generated diagram to the user and obtain approval before
proceeding to Task 2.3.

### Task 2.3: Generate an architecture description.

1. Generate a description that explains the purpose of each component, the
relationships between the components, and the task flow or data flow.
2. Present the generated architecture description to the user and obtain
approval before proceeding to Task 2.4.

### Task 2.4: Generate design recommendations.

1. Generate design recommendations and best practices to optimally configure
each component in the architecture based on the workload's requirements.

**Important**:

* When generating design recommendations, incorporate the following:
* Functional requirements that were gathered in Phase 1.
* Non-functional requirements that were gathered in Phase 1.
* To generate guidance for non-functional requirements, use the following
resources:
1. Best-practices guides for the products and topics that are relevant
to the workload: `references/best-practices-guides.md`
2. Well-Architected Framework pillar skills:
* For security requirements: `google-cloud-waf-security`
* For reliability requirements: `google-cloud-waf-reliability`
* For cost optimization requirements: `google-cloud-waf-cost-optimization`
* For operational excellence requirements: `google-cloud-waf-operational-excellence`
* For performance optimization requirements: `google-cloud-waf-performance-optimization`
* For sustainability requirements: `google-cloud-waf-sustainability`

2. Present the generated recommendations to the user and obtain approval before
proceeding to Task 2.5.

### Task 2.5: Generate deployment guidance.

1. Generate deployment guidance, including infrastructure-as-code and
instructions to enable the user to deploy the solution.
2. Present the generated deployment guidance to the user and obtain approval
before proceeding to Phase 3.

## Phase 3: Solution validation

### Task 3.1: Pre-deployment validation

1. Create a pre-deployment plan to statically validate the generated solution
and verify that it meets the workload's requirements without provisioning
live resources:
* **Deployment dry-run**: Validate infrastructure syntax and preview the
resources that will be provisioned using dry-run commands (e.g.,
`terraform plan` or (where supported) `gcloud ... --dry-run`).
* **Architecture & policy analysis**: Perform static verification of
network routing topologies, firewall rules, and IAM enforcement against
best practices.
2. Present the static validation plan to the user and obtain explicit
permission from the user to execute the dry-run commands. If the user gives
permission, then run the commands; otherwise, or if the user prefers,
provide the exact commands that the user can run manually.
3. Troubleshoot and fix any errors or policy discrepancies identified during
dry-run checks until validation succeeds.
4. Proceed to Task 3.2

### Task 3.2: Runtime validation (Post-deployment)

1. Ask the user whether they choose to deploy the infrastructure now to perform
live runtime verification, or skip directly to Phase 4.
2. **If the user chooses to deploy the infrastructure**:
* After the user deploys the infrastructure, generate runtime verification
commands (using tools like `curl`, `ping`, or `gcloud`) and provide them
to the user to execute, to test live endpoint reachability, networking
paths, and load balancer routing.
* Troubleshoot any deployment or runtime routing issues until checks pass.
3. Proceed to Phase 4.

## Phase 4: Solution packaging and presentation

Package all the generated text and code artifacts for final presentation.

1. Consolidate the text artifacts that were generated in Phase 2 and Phase 3
into a single Markdown file named `solution-architecture-guide.md`, based on
the template in `assets/output-template.md`.
2. Request the user's permission to write the code files in the user's
workspace.
3. After the user gives permission, write the code files in the user's
workspace.

When to use

Design cross-product Google Cloud solutions and review deployment plans; use Multi-Agent Deployment Design for agent-specific systems.

What you get

Complete original guidance with source attribution and declared limitations.

How it works

Clarify the actual task, inspect available evidence and plan the relevant source workflow within authorized scope.

Requirements

Business requirements, existing infrastructure, constraints, budget and project boundaries.

Delivery and review notes

Original explicitly separates design from execution; generated infrastructure and dry runs still require task authorization. Referenced scripts, templates, packages and remote documentation are not bundled or installed. Brief obvious-danger screening only; no functional test or comprehensive security certification.

Starting prompt

Use Google Cloud Solution Architecture for [TASK]. Clarify Business requirements, existing infrastructure, constraints, budget and project boundaries. Identify missing dependencies and assumptions. Loading this guidance grants no permission to change resources, transfer data or incur charges.

Not for

Automatic cloud execution, bypassing resource-owner permissions, or treating untested examples as deployed and verified results.

What M11 added

German task routing and precise scope. Original attribution: Google (google/skills repository). Original explicitly separates design from execution; generated infrastructure and dry runs still require task authorization. Referenced scripts, templates, packages and remote documentation are not bundled or installed. Brief obvious-danger screening only; no functional test or comprehensive security certification.

Original authorship remains with google/skills · Original source ↗

Original license & copyright

                                 Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the
      direction or management of such entity, whether by contract or
      otherwise, or (ii) ownership of fifty percent (50%) or more of the
      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity
      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,
      including but not limited to software source code, documentation
      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical
      transformation or translation of a Source form, including but
      not limited to compiled object code, generated documentation,
      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the
      editorial revisions, annotations, elaborations, or other modifications
      represent, as a whole, an original work of authorship. For the purposes
      of this License, Derivative Works shall not include works that remain
      separable from, or merely link (or bind by name) to the interfaces of,
      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including
      the original version of the Work and any modifications or additions
      to that Work or Derivative Works thereof, that is intentionally
      submitted to Licensor for inclusion in the Work by the copyright owner
      or by an individual or Legal Entity authorized to submit on behalf of
      the copyright owner. For the purposes of this definition, "submitted"
      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise
      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity
      on behalf of whom a Contribution has been received by Licensor and
      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      copyright license to reproduce, prepare Derivative Works of,
      publicly display, publicly perform, sublicense, and distribute the
      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      (except as stated in this section) patent license to make, have made,
      use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a
      cross-claim or counterclaim in a lawsuit) alleging that the Work
      or a Contribution incorporated within the Work constitutes direct
      or contributory patent infringement, then any patent licenses
      granted to You under this License for that Work shall terminate
      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the
      Work or Derivative Works thereof in any medium, with or without
      modifications, and in Source or Object form, provided that You
      meet the following conditions:

      (a) You must give any other recipients of the Work or
          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices
          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works
          that You distribute, all copyright, patent, trademark, and
          attribution notices from the Source form of the Work,
          excluding those notices that do not pertain to any part of
          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding those notices that do not
          pertain to any part of the Derivative Works, in at least one
          of the following places: within a NOTICE text file distributed
          as part of the Derivative Works; within the Source form or
          documentation, if provided along with the Derivative Works; or,
          within a display generated by the Derivative Works, if and
          wherever such third-party notices normally appear. The contents
          of the NOTICE file are for informational purposes only and
          do not modify the License. You may add Your own attribution
          notices within Derivative Works that You distribute, alongside
          or as an addendum to the NOTICE text from the Work, provided
          that such additional attribution notices cannot be construed
          as modifying the License.

      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,
      reproduction, and distribution of the Work otherwise complies with
      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
      this License, without any additional terms or conditions.
      Notwithstanding the above, nothing herein shall supersede or modify
      the terms of any separate license agreement you may have executed
      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade
      names, trademarks, service marks, or product names of the Licensor,
      except as required for reasonable and customary use in describing the
      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or
      agreed to in writing, Licensor provides the Work (and each
      Contributor provides its Contributions) on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
      implied, including, without limitation, any warranties or conditions
      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
      PARTICULAR PURPOSE. You are solely responsible for determining the
      appropriateness of using or redistributing the Work and assume any
      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,
      whether in tort (including negligence), contract, or otherwise,
      unless required by applicable law (such as deliberate and grossly
      negligent acts) or agreed to in writing, shall any Contributor be
      liable to You for damages, including any direct, indirect, special,
      incidental, or consequential damages of any character arising as a
      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing
      the Work or Derivative Works thereof, You may choose to offer,
      and charge a fee for, acceptance of support, warranty, indemnity,
      or other liability obligations and/or rights consistent with this
      License. However, in accepting such obligations, You may act only
      on Your own behalf and on Your sole responsibility, not on behalf
      of any other Contributor, and only if You agree to indemnify,
      defend, and hold each Contributor harmless for any liability
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.

   END OF TERMS AND CONDITIONS

   APPENDIX: How to apply the Apache License to your work.

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright [yyyy] [name of copyright owner]

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.

Source SHA-256: dd79bada843d543df9166565bcf8231db6342dcd1499548a9ddf5ec6598c209c
Snapshot checked: 2026-09-28T16:09:10.338Z

Find a skill.Get to work.

All skills

Multi-Agent Orchestration

AI Context Window Audit

AI Agent Architecture Audit

AI Skill Discovery

Lead Magnet Strategy

Ideal Customer Profile

Go-to-Market Strategy

Marketing Campaign Ideas

Product Growth Loops

Competitor Analysis

North Star Metric

Product Positioning

Product Vision

Go-to-Market Motion Selection

Customer Feedback and JTBD Analysis

PESTLE Market Environment Analysis

Customer Journey Mapping

Ansoff Growth Options

Data Analysis Validation

Dataset Profiling

Statistical Analysis Guidance

Programmatic SEO Planning

Landing Page and Form Conversion Review

Paywall and Upgrade Planning

Signup and Registration Review

User Onboarding and Activation

Popup and Modal Planning

Email Sequence Copy and Flow

Marketing Campaign Planning

Marketing Content Drafting

Brand Voice and Content Review

Marketing Performance Reporting

Sales Company Research

Company and Contact Enrichment

Website Information Architecture

Content Strategy and Editorial Roadmap

Product Launch Planning

Customer Research and Voice of Customer

Community Growth and Member Experience

Competitor Research Profiles

Roadmap and Release Communication

Lifecycle Email Sequences

API Contracts and Interface Design

Observability and Instrumentation Planning

Agent Context and Session Handoff

Product Discovery Sprint

Deal Quality Scoring

Enrichment Waterfall Design

Customer Retention Playbook

Sales Coaching Practice

Revenue Cohort Analysis

Intent Signal Scoring

Customer Identity Matching

Segment Activation Planning

Sales Call Review

Retention Dashboard Design

Sales Coaching Competencies

Offer Delivery Design

Offer Value Communication

Service Productization

Conversion Hypothesis Prioritization

Braze Engagement Guidance

Brand Voice Guide Design

Content Pipeline Orchestration

Website Brand Profile

Buyer Objection Clarification

Klaviyo Integration Guidance

Offer Bonus Planning

Klaviyo Marketing Review

Cross-Platform Advertising Review

Expertise Business Model

LinkedIn Advertising Guidance

TikTok Advertising Guidance

Evidence Research Brief

Cinematic Video Prompts

Visual Prompt Model Adaptation

Visual Prompt Diagnostics

Short Film Development

Find a skill.
Get to work.