Automated summary

This skill maintains a repository's GCP onboarding documentation, ensuring any changes to Google Cloud setup (OAuth, API scopes, Secret Manager, Cloud Run, environment variables) are reflected in the onboarding guides.

Strengths

Centralizes critical GCP information in a single file, avoiding duplication.
Promotes checklists and copy-paste commands for quick setup.
Ensures configuration changes are documented consistently.
Reduces risk of misconfiguration when onboarding new environments.

Limitations

Requires manual updates and careful review after each change.
May become outdated if changes are not documented promptly.
Only covers documentation, not actual infrastructure configuration.

When to use it

Use this skill when making changes to GCP components (OAuth, APIs, Secret Manager, Cloud Run, environment variables) and need to update the corresponding onboarding documentation.

When not to use it

Do not use for purely frontend or backend changes that don't affect GCP configuration, or for internal changes that don't require an onboarding documentation update.

Security analysis

Safe

Quality score90/100

The skill only instructs to maintain documentation files; it does not execute any commands, access external resources, or handle sensitive data. No executable tool usage is involved, and it explicitly warns against including secrets. Thus, it poses no security risk.

No concerns found

How this analysis is made

Examples

Update GCP onboarding after adding OAuth scope

I've added a new OAuth scope for Google Calendar API in the backend. Please update the GCP onboarding documentation to reflect this new scope, including the consent screen and any changes to environment variables.

Update Cloud Run deployment section in onboarding

We changed the Cloud Run service name from 'my-service' to 'new-service'. Update the onboarding guide with the new deployment commands and any configuration changes (e.g., memory, concurrency).

Add new Secret Manager secret to onboarding

We added a new secret called 'API_KEY' in Secret Manager for the backend. Update the onboarding docs to include instructions for granting access, referencing the secret, and setting the corresponding environment variable.

name: gcp-onboarding description: Maintain this repository's GCP onboarding documentation. Use when changes touch Google Cloud setup, OAuth consent or clients, Google API scopes, Secret Manager, Cloud Run, GitHub Pages deployment configuration, backend environment variables, or frontend environment flags that a new project/environment must configure.

GCP Onboarding

Name: GCP Onboarding
Author: Skills Guide Bot

When implementing changes that affect environment setup, inspect and maintain:

docs/guidelines/gcp-onboarding.md
projects/frontend/README.md
projects/backend/README.md
.github/copilot-instructions.md

Keep onboarding docs concise and task-oriented. Prefer checklists, exact config names, and copy-pasteable commands. Avoid duplicating the full guide in multiple READMEs; link to docs/guidelines/gcp-onboarding.md from local setup sections.

Required checks:

If OAuth origins, scopes, consent screen requirements, Google APIs, environment flags, secrets, Cloud Run settings, or deployment commands changed, update docs/guidelines/gcp-onboarding.md.
If the setup change is not straightforward enough to document safely, add a short note in the PR or implementation summary that onboarding docs need confirmation.
Keep existing documentation and links intact unless they are stale.
Never include real secrets, private client secrets, or production-only secret values in documentation.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/gcp-onboarding-mrwakfz2/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/gcp-onboarding-mrwakfz2' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/gcp-onboarding-mrwakfz2/download' --output '.skill-downloads/gcp-onboarding-mrwakfz2/SKILL.md.part' && mv '.skill-downloads/gcp-onboarding-mrwakfz2/SKILL.md.part' '.skill-downloads/gcp-onboarding-mrwakfz2/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code

test -f '.skill-downloads/gcp-onboarding-mrwakfz2/SKILL.md' && test -s '.skill-downloads/gcp-onboarding-mrwakfz2/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/gcp-onboarding' && cp -R '.skill-downloads/gcp-onboarding-mrwakfz2' '.claude/skills/gcp-onboarding'

Cursor

test -f '.skill-downloads/gcp-onboarding-mrwakfz2/SKILL.md' && test -s '.skill-downloads/gcp-onboarding-mrwakfz2/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/gcp-onboarding' && cp -R '.skill-downloads/gcp-onboarding-mrwakfz2' '.cursor/skills/gcp-onboarding'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation

openskills install './.skill-downloads/gcp-onboarding-mrwakfz2'

openskills read 'gcp-onboarding-mrwakfz2'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/gcp-onboarding-mrwakfz2/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

Supabase Docs Authoring

Documentation

Write, edit, and review Supabase documentation content including guides, tutorials, reference docs, and partials. Follow style guides and MDX/TOML validation rules.

Claude CodeintermediateSafe 108,544

Skills Guide Bot