gcp-awareness
ALWAYS check before using gcloud commands. Guide for GCP-related skills and tools.
What this skill does
# GCP Skills Guide You have specialized GCP debugging skills. Use these instead of raw gcloud commands for consistent, well-documented workflows. ## Decision Tree ### Skills vs Agents **Simple, single gcloud command query?** → Use `gcp-logs` skill - Better than: Running raw `gcloud logging read` commands - Example: "Find ERROR logs for api-gateway service" - Use when: Quick log fetch, single service, no correlation needed **Complex investigation requiring multiple steps?** → Use Task tool with GCP agents (conserves context) - `gcp-locator` - Fetch logs from multiple services, save to /tmp - `gcp-analyzer` - Filter logs, diagnose service issues, check IAM - `gcp-pattern-finder` - Correlate logs across services, build timelines - Use when: Multi-service investigation, correlation, pattern detection ### When to Use Which Agent **Just need to fetch logs broadly?** → Use `gcp-locator` agent only - Fetches logs from multiple services/time ranges - Saves to /tmp for later analysis - Example: "Get all ERROR logs from service-b, service-a, backend for last hour" **Investigating single service issue?** → Use `gcp-locator` + `gcp-analyzer` agents - Locator: Fetch relevant logs - Analyzer: Filter, diagnose root cause, check IAM/roles - Example: "Debug service-b permission errors" **Need to correlate across services or find patterns?** → Use all three: `gcp-locator` + `gcp-analyzer` + `gcp-pattern-finder` - Locator: Fetch from all relevant services - Analyzer: Filter each service's logs - Pattern-finder: Correlate by trace_id, build timelines, find patterns - Example: "Trace request flow across service-a → service-b → backend" **Need to understand GCP IAP authentication?** → Check documentation or use WebFetch - GCP IAP tokens: `gcloud auth print-identity-token` - Use for Grafana, ArgoCD, Temporal access ## Available GCP Tools | Type | Name | Purpose | |------|------|---------| | Skill | gcp-logs | Simple log queries (single gcloud command) | | Agent | gcp-locator | Fetch logs from multiple services/ranges | | Agent | gcp-analyzer | Analyze service logs, diagnose issues | | Agent | gcp-pattern-finder | Correlate logs, find patterns, build timelines | ## When to Use Raw gcloud Only use gcloud directly when: - Running one-off commands not covered by skills - User explicitly requests a specific gcloud command - Debugging the skill itself For systematic GCP work, use the specialized skills above. ## Common GCP Tools - `gcloud` - Primary CLI tool - `gcloud logging read` - Cloud Logging queries (use `gcp-logs` skill) - `gcloud auth print-identity-token` - Get IAP tokens for service access ## Authentication Check authentication before any GCP operation: ```bash gcloud auth list gcloud config get-value project ```
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.