cloud-rest-endpoints

Maintain Google Cloud REST endpoints for navigator gcp setup.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/neon-law-foundation/navigator --skill cloud-rest-endpoints
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cloud-rest-endpoints
Source: https://github.com/neon-law-foundation/navigator/tree/main/.claude/skills/cloud-rest-endpoints
Command: npx skills add https://github.com/neon-law-foundation/navigator --skill cloud-rest-endpoints

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintain the Google Cloud REST endpoints that power navigator gcp setup, preventing broken provisioning flows caused by drifting API paths, request bodies, or polling URLs.

Core Features & Use Cases

  • Endpoint Maintenance: Review and update service base URLs, request paths, and long-running operation polling templates.
  • Provisioning Debugging: Diagnose 4xx and 5xx failures that appear in real-GCP runs but not in mocked tests.
  • Service Expansion: Add new Google Cloud services to the provisioning pipeline while preserving dry-run behavior and idempotent POST semantics.
  • Release Safety: Verify that endpoint changes match current Google documentation before deployment.

Quick Start

Use this skill to review or update navigator gcp setup endpoints, then verify the URL, request body, and long-running operation polling template against Google's current REST docs.

Frequently Asked Questions about cloud-rest-endpoints

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

FAQPage Schema
How do I keep GCP REST API endpoints in sync with current Google Cloud documentation?

Keeping GCP REST endpoints in sync involves reviewing and updating service base URLs, request paths, and long-running operation polling templates against Google's current REST documentation to prevent broken provisioning flows.

Why does my GCP provisioning flow fail with 4xx or 5xx errors during real runs?

GCP provisioning flows fail with 4xx or 5xx errors due to drifted API paths, invalid request bodies, or incorrect polling URLs. Diagnosing these real-GCP failures requires verifying endpoint configurations against current Google REST documentation.

How do I add new Google Cloud services to an existing provisioning pipeline?

Adding new Google Cloud services requires editing GCP modules to include correct base URLs, request bodies, and long-running operation polling templates. You must preserve dry-run behavior and idempotent POST semantics during service expansion.

How do long-running operations work when polling GCP REST endpoints?

Long-running operations for GCP REST endpoints work by polling a dedicated operation status URL until completion. Maintaining correct polling templates ensures provisioning pipelines accurately track asynchronous resource creation and avoid premature timeouts.

Can I test GCP REST endpoint changes without affecting live cloud resources?

You can test GCP REST endpoint changes safely using dry-run execution. This verifies that endpoint modifications, including idempotent POST semantics and request bodies, match current Google documentation without provisioning live resources.

What are idempotent POST semantics and why are they needed for cloud provisioning?

Idempotent POST semantics ensure that repeated GCP REST API requests produce the same result without duplicate resource creation. They are needed for cloud provisioning to handle network retries safely during long-running operations and service expansion.