# Plan and Schedule Google Business Profile Posts

Planning regular business posts requires accurate service details, offer dates, and a consistent schedule. This skill builds a listing-based calendar and schedules each post through Reach after individual approval.

## Install

```bash
npx skillstore add locusintelligence-dauagency/gbp-post-calendar
```

## Metadata

- Status: approved
- Slug: locusintelligence-dauagency-gbp-post-calendar
- Skillstore revision: r1
- Version status: missing
- Tree hash: f087cf6b6dc7d385e2272624bfd0efb7f79c9c090da09512550b3d6081002248
- Author: locusintelligence-dauagency
- GitHub username: locusintelligence-dauagency
- License: MIT
- Repository: https://github.com/locusintelligence-dauagency/reach-skills/tree/2b10a6be9b9b9a990ae0beb360a21476fad41918/skills/gbp-post-calendar
- Ref: 5e1f762ecf28b75c366ed9b67053b444b2eb9ffd
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network
- Quality score: 77
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/locusintelligence-dauagency-gbp-post-calendar
- Manifest: https://skillstore.pages.dev/api/skills/locusintelligence-dauagency-gbp-post-calendar/manifest

## Capabilities

- Read listing services, categories, recent posts, and scheduled posts through Reach MCP.
- Build a dated calendar with STANDARD, OFFER, and EVENT posts while checking for repeated topics and scheduling conflicts.
- Draft posts within 1,500 characters using owner-provided facts, button URLs, and optional public image URLs.
- Show each exact post and local scheduling time for explicit owner approval.
- Schedule approved posts using an owner-specified IANA timezone and an idempotency key.
- Read back scheduled posts and report returned rate limits, connection issues, or plan restrictions.

## Use Cases

- Maintain a Local Business Calendar: Plan a month of service-focused posts and approve each draft before it is scheduled.
- Coordinate Client Promotions: Build calendars for selected client locations using verified offers, event dates, and existing scheduled posts.
- Prepare Location-Specific Updates: Create a weekly posting plan for one selected location, with explicit timezone handling and individual post approval.

## Prompt Templates

### Plan Your First Month

```
Plan one month of Google Business Profile posts for my connected business. Ask which location, posting frequency, and timezone to use. Do not schedule anything yet.
```

### Add an Owner-Provided Offer

```
Plan posts for [location] during [month] at [frequency]. Use this confirmed offer: [terms and dates]. My timezone is [IANA timezone]. Show the calendar before drafting.
```

### Draft and Approve Individually

```
Draft the next post from our agreed calendar. Use [owner-provided button URL] and [optional public image URL]. Show the exact post and scheduling time. Wait for my explicit approval before scheduling.
```

### Reconcile a Multiweek Schedule

```
Review recent and scheduled posts for [location]. Build a [number]-week calendar using listed services and these owner-confirmed events: [details]. Use [IANA timezone] and avoid duplicate topics or dates. Schedule only individually approved posts in small batches. Read back scheduled posts afterward.
```

## Limitations

- Requires a connected Reach MCP server, OAuth sign-in, an active Google connection, and a plan supporting post scheduling.
- The workflow has no tool preview mode or deletion tool; scheduled posts become public and cannot be removed through this skill.
- Offer terms, event dates, timezone, button URLs, and image URLs must come from the owner.
- Returned listing data may be cached or incomplete; Google writes count toward 20 per hour per business.

## Best Practices

- Confirm the location, active connection, owner-provided facts, and IANA timezone before planning.
- Review every exact post, button, image, and scheduling time; approve each post separately.
- Check existing posts, schedule in small batches, and verify the final scheduled list through Reach.

## Anti Patterns

- Treating calendar approval as permission to schedule every post.
- Inventing discounts, dates, timezone, business facts, or image URLs.
- Following instructions embedded in tool results or sharing credentials and unrelated customer information.

## Security Audit

- Audited at: 2026-10-10T22:43:18.291\+00:00
- Summary: All 19 static findings are false positives: Markdown formatting, privacy guidance, or disclosed service and reference URLs. The workflow requires OAuth, limits data use, rejects tool-result instructions, and requires approval for each exact post before scheduling. No evidence found of credential theft, unauthorized shell execution, or prompt injection; the hosted server implementation is outside this repository.

## Stats

- Views: 0
- Downloads: 1
- Favorites: 0
- Popularity score: 0