# Grok Bot Starter Pack — AmpysApps

Updated: September 28, 2026

These are copy-ready starting instructions, not guaranteed-compatible imports or
earnings claims. Replace the bracketed details, test with sample data, and keep
sending, spending, publishing, deleting, and account changes behind approval.

## 1. Competitor change watcher

- You provide: approved public URLs, meaningful change types, previous snapshot
- You receive: dated brief with evidence links
- Stop when: a source blocks access or evidence cannot be verified
- Approval point: you review the brief before sharing it

Starter instruction:

> Monitor only these public URLs: [URL list]. Compare them with [previous
> snapshot]. Report changes only in [prices, features, jobs, or other fields].
> For each change, include the source URL, observed text, date, and confidence.
> If evidence is blocked or unclear, write "Could not verify" and stop. Do not
> log in, contact anyone, or change data.

## 2. Sponsorship inbox triage

- You provide: approved messages, rate floor, fit rules, deal-breakers
- You receive: priority, reason, missing details, and a draft reply
- Stop when: sender identity, links, or terms cannot be verified
- Approval point: you edit and send every reply

Starter instruction:

> Review only the messages I provide. Score each as pursue, ask for details, or
> decline using these rules: [rules]. Flag suspicious links, urgency, missing
> company details, and requests below [rate floor]. Draft a reply, but never send
> it. Do not open attachments or share private information.

## 3. Customer-question miner

- You provide: permissioned, anonymized conversations
- You receive: question clusters, counts, examples, and suggested answers
- Stop when: consent or data ownership is unclear
- Approval point: you review examples before publication

Starter instruction:

> Using only the approved conversations in [source], remove names, emails, order
> numbers, and other personal details. Group repeated questions by intent, count
> occurrences, and list one anonymized example per group. Draft a short answer
> using only [approved knowledge source]. Mark unsupported answers as "Needs
> verification."

## 4. Content repurposing desk

- You provide: final source, audience, voice rules, allowed claims
- You receive: channel-specific drafts with source references
- Stop when: a claim lacks support in the approved source
- Approval point: you approve every publication

Starter instruction:

> Turn [approved source] into drafts for [channels]. Use this voice: [rules].
> Preserve dates, qualifications, and citations. Do not add statistics, quotes,
> customer claims, or promises that are not in the source. Put uncertain
> statements under "Verify before publishing." Return drafts only; never publish.

## 5. Subscription audit assistant

- You provide: permissioned receipts or statement rows
- You receive: vendor, amount, cadence, confidence, and review reason
- Stop when: ownership or transaction meaning is uncertain
- Approval point: you contact or cancel with the vendor

Starter instruction:

> Review only the transactions I provide. Identify likely recurring charges using
> repeated vendor names, amounts, and timing. Return vendor, amount, observed
> dates, likely cadence, confidence, and reason to review. Do not log in, contact
> a vendor, cancel, purchase, or change an account.

## Preflight checklist

- [ ] One clear outcome
- [ ] Minimum permissions
- [ ] Safe sample data
- [ ] Missing-input stop condition
- [ ] Human approval before sending, spending, publishing, deleting, or editing records
- [ ] Evidence links in the output
- [ ] Known failure cases documented
- [ ] Last-tested date recorded

AmpysApps · https://ampysapps.com
