What problem does it solve? Code changes touching Google Maps and Places integrations can silently leak server-only API keys into client bundles, drop required field masks that inflate billing, or fabricate ungrounded place data. This Skill provides a structured review checklist that catches these defects before they ship. ## Core Features & Use Cases - Credential Safety Review: Verifies server-only Places and grounding credentials stay out of client bundles and that browser keys remain properly restricted. - Field-Mask and Cost Auditing: Checks that Places (New) requests use the exact field mask for the endpoint and fields needed, and flags avoidable billable requests that should be cached or reused. - Grounding Integrity Checks: Prevents invented or transformed place_id, coordinates, URLs, hours, ratings, prices, or availability from being presented as provider truth, and keeps map, list, and chat identity synchronized to stable provider or database IDs. - Use Case: When reviewing a pull request that adds a new Places search flow, apply this Skill to confirm the request path uses the minimal field mask, grounded results are cached, and mapId is preserved for AdvancedMarker compatibility. ## Quick Start Review this pull request's Google Maps and Places changes for API-key exposure, field-mask regressions, and ungrounded place data.
