google-cloud-configs
Google Cloud Platform configuration templates for BigQuery ML and Vertex AI training with authentication setup, GPU/TPU configs, and cost estimation tools. Use when setting up GCP ML training, configuring BigQuery ML models, deploying Vertex AI training jobs, estimating GCP costs, configuring cloud authentication, selecting GPUs/TPUs for training, or when user mentions BigQuery ML, Vertex AI, GCP training, cloud ML setup, TPU training, or Google Cloud costs.
What this skill does
Use when: - Setting up BigQuery ML for SQL-based machine learning - Configuring Vertex AI custom training jobs - Setting up GCP authentication for ML workflows - Selecting appropriate GPU/TPU configurations - Estimating costs for GCP ML training - Deploying models to Vertex AI endpoints - Configuring distributed training on GCP - Optimizing cost vs performance for cloud ML ## Platform Overview ### BigQuery ML **What it is**: SQL-based machine learning directly in BigQuery **Best for**: - Quick ML prototypes using existing data warehouse data - Classification, regression, forecasting on structured data - Users familiar with SQL but not Python/ML frameworks - Large-scale batch predictions **Available Models**: - Linear/Logistic Regression - XGBoost (BOOSTED_TREE) - Deep Neural Networks (DNN) - AutoML Tables - TensorFlow/PyTorch imported models **Pricing**: - Based on data processed (same as BigQuery queries) - $5 per TB processed for analysis - AutoML: $19.32/hour for training ### Vertex AI Training **What it is**: Fully managed ML training platform **Best for**: - Custom PyTorch/TensorFlow training - Large-scale distributed training - GPU/TPU-accelerated workloads - Production ML pipelines **Available Compute**: - **CPUs**: n1-standard, n1-highmem, n1-highcpu - **GPUs**: NVIDIA T4, P4, V100, P100, A100, L4 - **TPUs**: v2, v3, v4, v5e (8 cores to 512 cores) **Pricing**: - CPU: $0.05-0.30/hour depending on machine type - GPU T4: $0.35/hour - GPU A100: $3.67/hour (40GB) or $4.95/hour (80GB) - TPU v3: $8.00/hour (8 cores) - TPU v4: $11.00/hour (8 cores) ## GPU/TPU Selection Guide ### GPU Selection (Vertex AI) **T4 (16GB VRAM)**: - Use case: Inference, light training, small models - Cost: $0.35/hour - Good for: BERT-base, small CNNs, inference serving **V100 (16GB VRAM)**: - Use case: Mid-size training, mixed precision training - Cost: $2.48/hour - Good for: ResNet training, medium transformers **A100 (40GB/80GB VRAM)**: - Use case: Large model training, distributed training - Cost: $3.67/hour (40GB), $4.95/hour (80GB) - Good for: GPT-style models, large vision models, multi-GPU training **L4 (24GB VRAM)**: - Use case: Modern alternative to T4, better performance - Cost: $0.66/hour - Good for: Mid-size models, efficient inference ### TPU Selection (Vertex AI) **TPU v2 (8 cores)**: - Use case: TensorFlow/JAX training, matrix operations - Cost: $4.50/hour - Memory: 8GB per core (64GB total) - Good for: Legacy TensorFlow models **TPU v3 (8 cores)**: - Use case: Standard TPU training - Cost: $8.00/hour - Memory: 16GB per core (128GB total) - Good for: BERT, T5, image classification **TPU v4 (8 cores)**: - Use case: Latest generation, best performance - Cost: $11.00/hour - Memory: 32GB per core (256GB total) - Good for: Large language models, cutting-edge research **TPU v5e (8 cores)**: - Use case: Cost-optimized TPU - Cost: $2.50/hour - Good for: Development, training at scale on budget **Multi-node TPU Pods**: - v3-32: 32 cores, $32/hour - v3-128: 128 cores, $128/hour - v4-128: 128 cores, $176/hour - Use for: Massive distributed training (GPT-3 scale) ## Usage ### Setup BigQuery ML Environment ```bash bash scripts/setup-bigquery-ml.sh ``` **Prompts for**: - GCP Project ID - BigQuery dataset name - Service account credentials - Default model type preference **Creates**: - `bigquery_config.json` - Project configuration - `.bigqueryrc` - CLI configuration - Example training SQL in examples/ ### Setup Vertex AI Training Environment ```bash bash scripts/setup-vertex-ai.sh ``` **Prompts for**: - GCP Project ID - Region (us-central1, europe-west4, etc.) - Service account credentials - Default machine type - GPU/TPU preference **Creates**: - `vertex_config.yaml` - Training job configuration - `vertex_requirements.txt` - Python dependencies - Training script template ### Configure GCP Authentication ```bash bash scripts/configure-auth.sh ``` **Prompts for**: - Authentication method (service account, user account, workload identity) - Service account key path (if applicable) - IAM roles needed **Creates**: - `.gcp_auth_config` - Authentication configuration - Sets GOOGLE_APPLICATION_CREDENTIALS environment variable - Validates permissions **Required IAM Roles**: - BigQuery ML: `roles/bigquery.dataEditor`, `roles/bigquery.jobUser` - Vertex AI: `roles/aiplatform.user`, `roles/storage.objectAdmin` - Both: `roles/serviceusage.serviceUsageConsumer` ### Estimate GCP Training Costs ```bash bash scripts/estimate-gcp-cost.sh ``` **Interactive prompts**: - Platform: BigQuery ML or Vertex AI - If BigQuery ML: Data size to process - If Vertex AI: - Machine type (CPU/GPU/TPU) - Number of machines - Training duration estimate - Storage requirements **Output**: - Estimated compute cost - Storage cost - Data transfer cost (if applicable) - Total estimated cost - Cost comparison with other GCP options ## Templates ### BigQuery ML Training Template (`templates/bigquery_ml_training.sql`) SQL template for creating and training models: - Model creation syntax - Feature engineering examples - Training options (L1/L2 reg, learning rate, etc.) - Evaluation queries - Prediction queries **Supported model types**: - LINEAR_REG, LOGISTIC_REG - BOOSTED_TREE_CLASSIFIER, BOOSTED_TREE_REGRESSOR - DNN_CLASSIFIER, DNN_REGRESSOR - AUTOML_CLASSIFIER, AUTOML_REGRESSOR ### Vertex AI Training Job Template (`templates/vertex_training_job.py`) Python template for custom training: - Training loop structure - Distributed training setup (PyTorch DDP) - Checkpointing and model saving - Metrics logging to Vertex AI - Hyperparameter tuning integration **Includes**: - Single GPU training - Multi-GPU training (DataParallel, DistributedDataParallel) - TPU training with PyTorch/XLA - Cloud Storage integration ### GPU Configuration Template (`templates/vertex_gpu_config.yaml`) YAML configuration for GPU training jobs: - Machine type selection - GPU type and count - Disk configuration - Network configuration - Environment variables **Presets included**: - Single T4 (budget) - Single A100 (standard) - 4x A100 (distributed) - 8x A100 (large-scale) ### TPU Configuration Template (`templates/vertex_tpu_config.yaml`) YAML configuration for TPU training jobs: - TPU type and topology - TPU version selection - JAX/TensorFlow runtime - XLA compilation flags **Presets included**: - v3-8 (single TPU) - v4-32 (TPU pod slice) - v5e-8 (cost-optimized) ### GCP Authentication Template (`templates/gcp_auth.json`) Service account configuration template: - Project ID - Service account email - Key file path - Required scopes - IAM role assignments **Security notes**: - Uses placeholders only (never real keys) - Documents how to create service accounts - Includes `.gitignore` protection ## Examples ### BigQuery ML Regression Example (`examples/bigquery-regression-example.sql`) Complete example: - Dataset: NYC taxi trip data - Task: Predict trip duration - Model: BOOSTED_TREE_REGRESSOR - Includes feature engineering, training, evaluation **Demonstrates**: - CREATE MODEL syntax - TRANSFORM clause for feature engineering - MODEL evaluation - Batch predictions ### Vertex AI PyTorch Training Example (`examples/vertex-pytorch-training.py`) Complete training script: - Dataset: IMDB sentiment analysis - Model: DistilBERT fine-tuning - Training: Single GPU - Logging: Vertex AI experiments **Demonstrates**: - Loading data from GCS - Training loop with mixed precision - Checkpointing to GCS - Metrics logging - Model export to Vertex AI ### Vertex AI Distributed Training Example (`examples/vertex-distributed-training.py`) Multi-GPU training example: - Dataset: ImageNet subset - Model: ResNet-50 - Training: 4x A100 with DDP - Scaling: Linear scaling rule **Demonstrates**: - PyTorch DistributedDataParallel - Gradient accumulation - Learning rate scaling - Synchronized batch norm - Multi-node coordination ### Hugging Face Fine-tuning on Vertex AI (`examples/vertex-huggingface-fine
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.