Skip to content

Improve skill description for deploy. #173

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
CoasterJX wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Improve skill description for deploy. #173

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 11 additions & 2 deletions skills/google-cicd-deploy/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,10 +1,19 @@
---
name: google-cicd-deploy
description: >
Use this skill when requested to deploy an application to Google Cloud (GCS, Cloud Run, GKE) or when analyzing an application to determine the best deployment target.
**Why**: This skill enforces mandatory security protocols, specifically secret scanning, and guides the selection of the optimal deployment workflow, preventing security risks and inefficient resource use. Activation ensures compliance with these standards and best practices.
Use this skill when requested to deploy, host, or release any application, static site, backend service, or container image to Google Cloud (including GCS, Cloud Run, GKE/Kubernetes), or whenever the user has the intent to get their application running/working on Google Cloud.

**Triggers**:
- Any user request with the intent to get an application "up and running", "working", "hosted", or "online" on Google Cloud / GCP.
- Deploying static websites, uploading build artifacts/dist folders, or configuring hosting on Google Cloud Storage (GCS).
- Running containerized applications or Docker images on Google Kubernetes Engine (GKE), including creating/updating Kubernetes manifests (Deployment, Service).
- Deploying backend apps (Node.js, Python, Go) to Cloud Run, whether deploying from source code, container images, or using Cloud Native Buildpacks.

@gemini-code-assist gemini-code-assist Bot May 19, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The list of supported languages for Cloud Run should be more inclusive to match the capabilities defined in the prompt (Workflow B), which supports Go, Node.js, Python, Java, .NET, Ruby, and PHP. Using "such as" or expanding the list helps ensure the skill is triggered for all supported language runtimes.

Suggested change
- Deploying backend apps (Node.js, Python, Go) to Cloud Run, whether deploying from source code, container images, or using Cloud Native Buildpacks.
- Deploying backend apps (such as Node.js, Python, Go, Java, .NET, Ruby, or PHP) to Cloud Run, whether deploying from source code, container images, or using Cloud Native Buildpacks.

- Planning, troubleshooting, or analyzing the best Google Cloud deployment target for an application (even if the request has missing files or false assumptions).

**CRITICAL**: Activation is MANDATORY before writing any Dockerfiles, Kubernetes manifests, or running deployment shell commands (such as `gcloud storage`, `gsutil`, `gcloud run deploy`, or `gcloud deploy`). This guarantees compliance with required security protocols (like secret scanning) and prevents security leaks.

@gemini-code-assist gemini-code-assist Bot May 19, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The list of deployment commands in the CRITICAL section should include kubectl, as it is the primary tool used for GKE deployments (Workflow D). Including it ensures the model recognizes that kubectl operations also require prior skill activation to trigger mandatory security protocols like secret scanning.

Suggested change
**CRITICAL**: Activation is MANDATORY before writing any Dockerfiles, Kubernetes manifests, or running deployment shell commands (such as `gcloud storage`, `gsutil`, `gcloud run deploy`, or `gcloud deploy`). This guarantees compliance with required security protocols (like secret scanning) and prevents security leaks.
**CRITICAL**: Activation is MANDATORY before writing any Dockerfiles, Kubernetes manifests, or running deployment shell commands (such as `gcloud storage`, `gsutil`, `gcloud run deploy`, `kubectl`, or `gcloud deploy`). This guarantees compliance with required security protocols (like secret scanning) and prevents security leaks.

---


# Google Cloud CI/CD Assistant

You are a comprehensive Google Cloud CI/CD Assistant. Your primary function is to help users deploy to Google Cloud. You operate by first analyzing the user's intent if provided, and then following the appropriate workflow.
Expand Down
Loading