pp-google-business-profile

Dieser Auszug wurde bei der Prüfung gespeichert. Die externe Quelle enthält die vollständige und aktuelle Version.

---
name: pp-google-business-profile
description: "Printing Press CLI for Google Business Profile. Combined CLI for multiple API services"
author: "Raj Yaligar"
license: "Apache-2.0"
argument-hint: "<command> [args] | install cli|mcp"
allowed-tools: "Read Bash"
metadata:
  openclaw:
    requires:
      bins:
        - google-business-profile-pp-cli
    install:
      - kind: go
        bins: [google-business-profile-pp-cli]
        module: github.com/mvanhorn/printing-press-library/library/marketing/google-business-profile/cmd/google-business-profile-pp-cli
---
<!-- GENERATED FILE — DO NOT EDIT.
     This file is a verbatim mirror of library/marketing/google-business-profile/SKILL.md,
     regenerated post-merge by tools/generate-skills/. Hand-edits here are
     silently overwritten on the next regen. Edit the library/ source instead.
     See the repository agent guide, section "Generated artifacts: registry.json, cli-skills/". -->

# Google Business Profile — Printing Press CLI

## Prerequisites: Install the CLI

This skill drives the `google-business-profile-pp-cli` binary. **You must verify the CLI is installed before invoking any command from this skill.** If it is missing, install it first:

1. Install via the Printing Press installer:
   ```bash
   npx -y @mvanhorn/printing-press-library install google-business-profile --cli-only
   ```
2. Verify: `google-business-profile-pp-cli --version`
3. Ensure `$GOPATH/bin` (or `$HOME/go/bin`) is on `$PATH`.

If the `npx` install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.3 or newer):

```bash
go install github.com/mvanhorn/printing-press-library/library/marketing/google-business-profile/cmd/google-business-profile-pp-cli@latest
```

If `--version` reports "command not found" after install, the install step did not put the binary on `$PATH`. Do not proceed with skill commands until verification succeeds.

Use the Google Business Profile CLI to manage API resources, then archive them locally for fast search, grouped analytics, and rollout verification. It is designed for operator workflows where repeated read access and auditability matter as much as raw endpoint coverage.

## Unique Capabilities

These capabilities aren't available in any other tool for this API.

### Local operator workflows
- **`workflow archive`** — Build a local SQLite archive of Google Business Profile resources so agents can inspect accounts and locations without re-hitting the API on every question.

  _Lets an agent answer follow-up questions from a synchronized snapshot instead of burning quota and latency on repeated list calls._

  ```bash
  google-business-profile-pp-cli workflow archive --agent
  ```
- **`workflow status`** — Show local archive freshness and sync state across resource tables so operators know whether offline answers are still trustworthy.

  _Prevents agents from making stale operational recommendations from an old archive._

  ```bash
  google-business-profile-pp-cli workflow status --agent
  ```
- **`search`** — Search locally synced Business Profile data with FTS5 when a native API search path is absent or live auth is unavailable.

  _Gives fast operator lookup across synced records without crafting custom filters for each API surface._

  ```bash
  google-business-profile-pp-cli search "Toronto" --data-source local --type locations --limit 20 --json
  ```
- **`analytics`** — Run grouped analytics over synced data to count resources and surface distribution patterns without exporting to spreadsheets first.

  _Turns the CLI into a lightweight reporting surface for location inventory and QA work._

  ```bash
  google-business-profile-pp-cli analytics --type locations --group-by storeCode --limit 25 --json
  ```

### Monitoring and verification
- **`tail`** — Poll the API and emit NDJSON change events so operators can watch location-related activity in near real time.

  _Makes the CLI useful for active monitoring, not just one-shot API calls