本文へ移動
cccskills
無料GitHub で公開

cloud-databases-onboarding

Guides users through discovering their database requirements, recommends a Google Cloud database based on a recommendation matrix, and assists in database creation. Use when a user asks 'What database service should I use?', 'Help me pick a database', or when a user wants to create a new database on Google Cloud. Don't use for general Google Cloud maintenance, managing existing databases, or database migrations.

インストール方法を見る

含まれるファイル(5)

  • SKILL.md6.5 KB
  • references/onboarding_prompts.md12.1 KB
  • references/recommendation_matrix.txt43.5 KB
  • references/selection_prompts.md1.0 KB
  • scripts/database_onboarding_skill.py6.4 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Google Cloud Database Onboarding Skill

This skill provides domain instructions, decision matrices, and Infrastructure-as-Code workflows to guide users through discovering their exact database requirements, selecting an optimal Google Cloud database service, and drafting starter resource provisioning code for user review.

Validation & Progressive Disclosure

A validation script is provided to verify the skill's reference files and formatting:

python3 scripts/database_onboarding_skill.py --verify
  • Reading / Progressive Disclosure: When interacting with a user during a conversation, load reference files progressively. Follow the Just-in-Time (JiT) loading instructions outlined in the phases below.

Workflow & Just-in-Time (JiT) Instructions

This workflow operates in three distinct sequential phases. Evaluate the active conversation history to determine the current phase and follow the corresponding instructions:

Phase 1: Requirement Discovery & Information Gathering

When a user asks "What database should I use?" or requires guidance on Google Cloud database selection, you must initiate the Discovery phase.

  1. Load Discovery Instructions (JiT): Read the complete contents of references/onboarding_prompts.md using view_file.
  2. Execute Discovery: Follow the detailed Phase 1 instructions in onboarding_prompts.md to gather core requirements (data model, workload, scale, and migration context) using user-friendly phrasing and enforcing constraints (such as the 90% confidence rule) before proposing any recommendation.

Phase 2: Recommendation Analysis & Matrix Consultation

Once you have gathered sufficient explicit discovery context, you must determine the optimal Google Cloud database recommendation.

  1. Consult Matrix & Formulate Recommendation (JiT): Follow the Phase 2 instructions in references/onboarding_prompts.md. This involves distilling requirements, calling the database selection tool (or consulting references/recommendation_matrix.txt directly if the tool is unavailable), and formulating a single recommendation.
  2. Deliver Recommendation: Deliver the recommendation to the user, mapping destination codes to plain English, explaining the reasoning, and offering to help with provisioning as detailed in onboarding_prompts.md.

Phase 3: Implementation & Provisioning (Plan-Validate-Execute Pattern)

When the user accepts the recommendation and requests to provision or modify cloud resources, follow the Phase 3 instructions in references/onboarding_prompts.md using a strict Plan-Validate-Execute pattern. Limit your actions to creating and validating draft artifacts for user review.

  1. Analyze the Workspace: Scan the user's workspace/open files/related directories with database resources scripts.

  2. Obtain User Confirmation: If the target infrastructure files are not clear, ask the user explicitly to confirm the file paths or target directory before modifying anything.

  3. Draft Infrastructure Plan (Plan): Create or edit the necessary Terraform configuration files or any other relevant scripts necessary to provision the resources. When creating or editing Terraform files or any other database resource provisioning script, you MUST:

    • Add a stamped header comment at the top of every generated Terraform file/ shell script or any other resource provisioning script. (e.g., # Generated with cloud onboarding skills selector @date, replacing @date with the current date/timestamp).
    • Add a custom default tag like resource_generated_by = "cloud db onboarding skill" under the default_tags block or as a resource label/tag.
    • gcloud CLI Generation: When drafting gcloud CLI commands or shell scripts, you MUST follow the instructions in the gcloud skill (../gcloud/SKILL.md). Specifically:
      • Always use gcloud beta command group for database provisioning (e.g., gcloud beta <group> <resource> create).
      • Validate leaf-level syntax using gcloud help <leaf_command> prior to proposing commands.
      • Append explicit --project=<PROJECT_ID> and explicit location flags (--region, --zone, or --location).
      • Use --dry-run or --validate-only preview flags where supported.
      • Include custom label/tag flags (e.g. --labels=resource_generated_by=cloud_db_onboarding_skill) on generated gcloud provisioning commands.
      • Do NOT include --quiet (-q): Provisioning commands are drafted for interactive human user review and execution, so do NOT include non-interactive --quiet or -q flags.
      • No Live Write Execution: The skill MUST ONLY draft provisioning commands or code for user review and MUST NOT execute mutating/write infrastructure operations directly.
  4. Validate Infrastructure Code (Validate): Before finalizing, you must validate the drafted infrastructure code to verify syntax and configuration correctness. Why this matters: Validating Terraform code ensures that configuration blocks, IAM bindings, and instance sizing are syntax-error-free and strictly enforceable before code review.

  5. Create Pull Request (Execute): Once validation succeeds with zero errors, automatically create a Pull request containing the validated Terraform/shell/scripts updates for user review. Leave live infrastructure changes (terraform apply or gcloud commands) to human review or automated CI/CD pipelines.


Supporting Resources & Documentation

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Configures best-practice alerting policies for AI agents using OpenTelemetry (OTel) metrics, generating output as Terraform (.tf) configuration files. Use when analyzing, writing, or deploying alerting policies to monitor agent latency, error rates, token usage, and quality metrics. Don't use for standard infrastructure monitoring unrelated to AI agents, or when the agent is not instrumented with OpenTelemetry (for Reliability, Cost, Safety, Security alerts). NOTE: Reliability, Cost, Safety, and Security alerts use generic OTel metrics and work across runtimes (such as Cloud Run, Vertex AI). Quality alerts rely on Vertex AI Online Monitors and are strictly bound to Vertex AI deployments.

日本語の概要は準備中です。原文の説明を表示しています。

google/skills2.1万2026年10月10日 更新

Deploy open models or custom weights from Model Garden to Agent Platform endpoints, check the status of an in-progress deployment operation, or clean up resources by undeploying models and deleting endpoints. Use when asked to actively deploy a model, list the Model Garden CATALOG of available models, check if a specific model is deployable (`gcloud ai model-garden models list-deployment-config`), query deployment cost, troubleshoot deployment errors (like quota limits), or undeploy/clean up endpoints. Also use when copying and deploying a 1P Tuned Model. Don't use for pure listing/discovery questions of the form "is X deployed?", "list my endpoints", or "which regions have models running?" — for those use `agent-platform-endpoint-management`. Don't use for running model evaluations (use `agent-platform-eval-flywheel` skill).

日本語の概要は準備中です。原文の説明を表示しています。

google/skills2.1万2026年10月10日 更新

Manages Agent Platform serving endpoints. Use when you need to create, list, describe, update, or delete serving endpoints for model deployment on Agent Platform. Also use when troubleshooting endpoint permission, quota, or resource busy errors. Don't use for deploying models to endpoints or for running model evaluations.

日本語の概要は準備中です。原文の説明を表示しています。

google/skills2.1万2026年10月10日 更新

Measures and improves the quality of AI models and agents on Google Cloud using the Eval Quality Flywheel methodology. Use when generating synthetic user scenarios, evaluating an agent or model, building an eval dataset, picking or writing evaluation metrics, analyzing failures, comparing results before and after a fix, or when guidance is needed on Agent Platform eval methodology — including dataset schema, LLM-as-judge scoring, and common failure causes. For fine-tuning, use agent-platform-tuning. For general production deployment, use agent-platform-deploy.

日本語の概要は準備中です。原文の説明を表示しています。

google/skills2.1万2026年10月10日 更新

Connects to and performs inference with Google Cloud Agent Platform GenAI models, including First-Party Gemini models and Third-Party OpenMaaS models (Llama, DeepSeek, Qwen, etc.). Use when asked to perform inference, ask a model a question, run a test prompt, execute chat completions, or generate code for calling Gemini or OpenMaaS models, authenticate with GenAI SDK, OpenAI SDK, or legacy Agent Platform SDK, configure base URLs and global/regional endpoints, or troubleshoot 429 Resource Exhausted (DSQ), 400 User Validation, or 404 Not Found errors. Don't use for deploying models to endpoints or for running model evaluations.

日本語の概要は準備中です。原文の説明を表示しています。

google/skills2.1万2026年10月10日 更新

Guides agents and users through migrating from Gemini API in Google AI Studio to Gemini Enterprise Agent Platform (formerly Vertex AI). Use this skill when moving applications to Google Cloud, to leverage Cloud credits, or to unify inferencing with other Cloud infrastructure (IAM, billing, telemetry).

日本語の概要は準備中です。原文の説明を表示しています。

google/skills2.1万2026年10月10日 更新

google のスキルをすべて見る

このスキルの問題を報告する