← SimplifiedCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Simplified
Snapshot Sep 30, 2026 · 22:54 UTC · version 2.0.0
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"name": "local-business-marketing",
"description": "Plan and create locally relevant social and Google Business content for location-based and service-area businesses. Use when the user asks for local marketing, neighborhood content, Google Business posts, store or restaurant promotion, appointment or booking campaigns, local events, service-area awareness, foot-traffic content, location launches, or a practical social plan for a small local business.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 530
},
{
"relative_path": "references/local-channel-playbook.md",
"size_in_bytes": 1933
}
],
"skill_md_contents": "---\nname: local-business-marketing\ndescription: Plan and create locally relevant social and Google Business content for location-based and service-area businesses. Use when the user asks for local marketing, neighborhood content, Google Business posts, store or restaurant promotion, appointment or booking campaigns, local events, service-area awareness, foot-traffic content, location launches, or a practical social plan for a small local business.\n---\n\n# Local Business Marketing\n\nTurn local relevance, operational truth, community proof, and timely offers into content that drives calls, bookings, directions, visits, and qualified inquiries.\n\n## Guardrails\n\n- Verify business name, locations or service area, hours, availability, prices, offer terms, event dates, phone/booking destination, and required disclaimers before publishing them.\n- Never fabricate reviews, customer identities, local partnerships, awards, scarcity, neighborhood knowledge, or “near me” relevance.\n- Treat regulated services, health claims, financial claims, age restrictions, and before/after results conservatively; surface required approvals.\n- Do not publish the same generic promotional caption to every location or platform.\n- Create drafts first. Obtain explicit approval of location, offer terms, CTA destination, date, account, and media before scheduling or queueing.\n- Stop on authorization failure or when the requested local account is not connected.\n\n## Workflow\n\n1. Establish location model: storefront, multi-location, mobile/service-area, appointment-led, event-led, or locally delivered ecommerce. Capture geography, audience, demand windows, offer, proof, conversion action, and operational constraints.\n2. Call `social_getSocialMediaAccounts` once and map returned accounts to locations and channels. Do not infer that similarly named accounts represent the same branch.\n3. Audit useful local inputs: FAQs, service availability, customer proof with permission, team expertise, products/menu, events, partnerships, landmarks, seasonality, weather sensitivity, inventory, and booking capacity.\n4. Build a balanced plan using five jobs: be found, reduce uncertainty, prove trust, create timely reasons to act, and strengthen community relevance.\n5. Choose platform roles using [references/local-channel-playbook.md](references/local-channel-playbook.md). Use Google Business for high-intent updates and actions; use social channels for discovery, familiarity, proof, and community context.\n6. Write location-specific copy with a concrete local detail, customer value, proof or operational fact, and one primary CTA. Avoid keyword-stuffed city lists.\n7. Plan authentic media: exterior/interior orientation, people with permission, process, product/service detail, local proof, event information, or offer creative. Upload local media through `$simplified-social` and retain permanent asset IDs.\n8. Show a location/channel matrix containing date, account, post purpose, copy, media, CTA, offer terms, and verification status.\n9. When authorized, create each post with `social_createSocialMediaPost` and `action: \"draft\"`. Apply exact Google Business and channel fields from `../simplified-social/references/platform-settings.md`.\n10. Schedule or queue only after explicit approval. Measure by the intended business action where available, separating platform engagement from calls, bookings, visits, and revenue.\n\n## Local Marketing Standard\n\n- Lead with usefulness and specificity: what is available, for whom, where, when, why it matters, and what to do next.\n- Use community content only when the relationship is real and relevant. Locality is context, not decoration.\n- Balance demand capture with trust building: offers alone create promotion fatigue; lifestyle content alone may fail to drive action.\n- Reflect capacity. Do not promote appointment slots, delivery coverage, inventory, or event access the business cannot fulfill.\n- For multiple locations, preserve brand consistency while allowing meaningful local differences in team, proof, events, products, and CTA routes.\n\n## Output\n\nLead with the local growth objective and conversion path. Then provide the channel/location roles, content plan, verification checklist, drafts created, measurement plan, and any operational fact blocking publication.\n"
}SHA-256: d28be0f598dfa07f4ad5e4faf8988fedf256f525386098fed9ad80b00ec173cf