cloud-tasks-queue-setup
Configure cloud tasks queue setup operations. Auto-activating skill for GCP Skills. Triggers on: cloud tasks queue setup, cloud tasks queue setup Part of the GCP Skills skill category. Use when working with cloud tasks queue setup functionality. Trigger with phrases like "cloud tasks queue setup", "cloud setup", "cloud".
What this skill does
# Cloud Tasks Queue Setup ## Overview Create and configure Google Cloud Tasks queues for reliable asynchronous task execution. Covers queue creation with rate limiting and retry policies, HTTP and App Engine task targets, task dispatching with scheduling delays, and queue management operations (pause, resume, purge). ## Prerequisites - Google Cloud project with Cloud Tasks API enabled (`gcloud services enable cloudtasks.googleapis.com`) - `gcloud` CLI authenticated with `roles/cloudtasks.admin` or `roles/cloudtasks.enqueuer` IAM role - Target HTTP endpoint or App Engine service to receive dispatched tasks - Service account with appropriate permissions for task execution ## Instructions 1. Create a Cloud Tasks queue with rate limiting: `gcloud tasks queues create <queue-name> --location=<region> --max-dispatches-per-second=10 --max-concurrent-dispatches=5` 2. Configure retry policy for failed tasks: `gcloud tasks queues update <queue-name> --max-attempts=5 --min-backoff=1s --max-backoff=300s --max-doublings=4` 3. Create an HTTP task targeting your endpoint: `gcloud tasks create-http-task --queue=<queue-name> --url=https://your-service.run.app/process --method=POST --body-content='<json-payload>'` 4. Schedule a delayed task by adding `--schedule-time` with an ISO 8601 timestamp up to 30 days in the future 5. Verify queue status and task counts: `gcloud tasks queues describe <queue-name>` to check dispatch rate, retry config, and queue state 6. Manage queue operations: pause (`gcloud tasks queues pause`), resume (`gcloud tasks queues resume`), or purge all tasks (`gcloud tasks queues purge`) ## Examples **Setting up an email processing queue**: Create a queue with 5 dispatches per second rate limit and 3 max concurrent tasks to avoid overwhelming the email service. Configure retry with exponential backoff (1s min, 60s max, 3 doublings) and 10 max attempts for transient failures. **Scheduling delayed webhook callbacks**: Create HTTP tasks with a 15-minute schedule delay to implement webhook retries. Each task POSTs to the callback URL with the original event payload and includes an OIDC token for authentication. ## Output - Cloud Tasks queue created with rate limiting and retry configuration - Task creation commands for HTTP and App Engine targets - Queue management commands for operational control ## Error Handling | Error | Cause | Solution | |-------|-------|----------| | Queue already exists | Queue name taken in the specified region | Use `gcloud tasks queues describe` to check existing config; update if needed | | PERMISSION_DENIED on task creation | Service account lacks `cloudtasks.tasks.create` permission | Grant `roles/cloudtasks.enqueuer` to the service account | | Task handler returns 5xx | Target endpoint failed to process the task | Tasks auto-retry per queue retry policy; check handler logs for root cause | | Rate limit exceeded | Dispatch rate exceeds queue configuration | Increase `max-dispatches-per-second` or reduce task creation rate | ## Resources - Cloud Tasks documentation: https://cloud.google.com/tasks/docs - Queue configuration reference: https://cloud.google.com/tasks/docs/configuring-queues - Creating HTTP tasks: https://cloud.google.com/tasks/docs/creating-http-target-tasks - IAM permissions: https://cloud.google.com/tasks/docs/access-control ## Related Skills Part of the **GCP Skills** skill category. Tags: gcp, bigquery, vertex-ai, cloud-run, firebase
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.