gcp-pubsub

Generate Google Cloud Pub/Sub topic and subscription configurations with gcloud CLI and Terraform HCL.

1|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/sitharaj88/claude-skills --skill gcp-pubsub
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gcp-pubsub
Source: https://github.com/sitharaj88/claude-skills/tree/main/skills/gcp-pubsub
Command: npx skills add https://github.com/sitharaj88/claude-skills --skill gcp-pubsub

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill simplifies the creation and configuration of Google Cloud Pub/Sub resources, enabling robust event-driven architectures and asynchronous messaging patterns.

Core Features & Use Cases

  • Topic & Subscription Management: Generate configurations for Pub/Sub topics and various subscription types (pull, push, BigQuery, Cloud Storage).
  • Messaging Patterns: Implement patterns like fanout, queues, dead-lettering, and exactly-once delivery.
  • Use Case: Set up a Pub/Sub topic and a push subscription to an existing Cloud Run service to handle real-time order processing events.

Quick Start

Generate a Pub/Sub topic named 'order-events' with a 7-day message retention and a pull subscription named 'order-processor-sub' with a 60-second ack deadline.

Frequently Asked Questions about gcp-pubsub

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure a Google Cloud Pub/Sub topic with a pull subscription and custom message retention?

Configure event-driven Google Cloud Pub/Sub topics and pull subscriptions using generated Terraform HCL or gcloud CLI commands. You can specify custom message retention durations and ack deadlines to control asynchronous delivery and processing behavior.

Can I set up a dead-letter queue for failed messages in Google Cloud Pub/Sub?

Yes, you can implement dead-lettering patterns in Google Cloud Pub/Sub to handle failed messages. The generated configurations define subscriptions that route undeliverable messages to designated dead-letter topics for isolated retry tracking.

What's the best way to create a Pub/Sub subscription that writes directly to BigQuery?

Generate a BigQuery subscription configuration using Terraform HCL or gcloud CLI to stream Pub/Sub messages directly into a BigQuery table. This enables event-driven streaming pipelines without requiring intermediate compute services for data routing.

Does this support push subscriptions for delivering events to Cloud Run services?

Yes, it generates configurations for push subscriptions that deliver Pub/Sub events directly to HTTP endpoints like Cloud Run. This supports real-time event processing workloads by triggering services automatically upon message publication.

How do I implement a fan-out messaging pattern in Google Cloud Pub/Sub?

Implement a fan-out pattern by generating a single Pub/Sub topic with multiple subscriptions attached. Each subscription independently receives the full message stream, enabling parallel asynchronous processing across different consumer services.

Can I enforce message ordering in Google Cloud Pub/Sub event-driven architectures?

Yes, generated Pub/Sub subscription configurations support message ordering keys. This ensures that messages with the same ordering key are delivered to consumers sequentially, maintaining event state consistency in streaming pipelines.