A better local brief.
Ready for your bot.

Start with one good check.

Paste the prompt into your Grok Bot conversation. Review its first set of drafts, then refine the voice and choose the routine that works for you.

1. Point it here. Read grok.txt once for the source map and today.md on each check. The JSON briefing serves the same job for tools.
2. Keep the evidence attached. Every factual draft should carry the original source link and relevant source time. A fresh fetch can contain an older observation or a monthly statistic.
3. Choose the rhythm. After one successful check, save the process as a skill and set any routine in Grok Bot with an explicit time and America/Los_Angeles time zone.

Useful beats for a local account

• Weather and ocean conditions, with their measurement place and time.
• A park, court, local benefit or community resource someone can use.
• A dated property development from Space Dirt, with a link to the original article.
• One small AI lesson, artwork or PointCast field note.

Use business search to find candidates, then check the business itself for current details. Our map directory is a dated starting point, not a live opening-hours service.

Copy this into Grok Bot.

Select the prompt below, or open the plain-text version. It works without a special website plugin.

Help me prepare @elsegundotoday: a warm, practical local guide to El Segundo and the surrounding 25-mile area.

First read https://elsegundo.xyz/grok.txt. On every check, fetch https://elsegundo.xyz/today.md again. Use https://elsegundo.xyz/api/v1/briefing for structured data and follow its source links when you need more detail.

Use America/Los_Angeles for dates and times. Check each item's observation, issue or reporting date; the briefing's generation time does not make every item current. Keep El Segundo separate from nearby places and name the weather station or geography when relevant. Missing or stale data means unknown, never zero or “all clear.”

Prepare up to three concise local post drafts: useful conditions; a verified local development or resource; and one evergreen discovery from our AI lessons, art, parks or community resources. Prefer something new or meaningfully changed over repeating yesterday. Omit an item when evidence is insufficient.

Include the original source URL and its relevant date or time with each draft. Check operators for current hours, event dates, prices, sports schedules and listing availability. Space Dirt is a property-news source: follow the article and verify its publication date before calling anything new. Directory entries are dated map records, not confirmation that a business is open.

Credit Michael Hoydich's Midjourney work as AI artwork, not a photograph of a real place. Keep artwork and creative experiments separate from factual local reporting.

Return the drafts in our private Bot conversation. Do not post to X or publish site content in this workflow. Research submissions use the separately configured review-only handoff below.

FROM RESEARCH TO REVIEW

Bring the useful things back.

Your “research on twitter” Bot can prepare a South Bay at-a-glance brief and send its strongest findings to the site’s private research inbox.

Each submission carries its sources and dates. A receipt confirms storage for review; it does not publish the findings, update the site or post as @elsegundotoday.

1. Set up privately. Open the research handoff guide and JSON contract. Add the owner’s research key only through a supported secure secret request; keep it out of chat, screenshots, posts and ordinary files.
2. Test the connection. Follow the setup guide’s marked test (isTest: true), then use the daily prompt alongside. Confirm that your Bot can securely attach the credential and return a matching receipt. A saved key alone is not proof of a working connection.
3. Choose a daily rhythm. After reviewing that first report, save the skill and choose a daily time in America/Los_Angeles. Keep publishing and X posting outside this workflow.

If a secure request cannot be made, keep the JSON draft in the private Bot conversation. An already authorized GitHub connection can propose a repository pull request for review instead.

xAI documents public X research, browser and command-line work, and routines. This HTTPS handoff uses those general capabilities; secure credential binding and successful submission must be tested in your own Bot. Public read-only MCP access does not grant write access.

Copy the daily research instruction.

Use it in your private Bot conversation. The credential placeholder stays a placeholder; the real key belongs in secure setup.

Run one daily research check for @elsegundotoday, covering El Segundo and the surrounding 25-mile area. Use America/Los_Angeles. Read https://elsegundo.xyz/grok.txt, fetch https://elsegundo.xyz/today.md again, and read the current submission contract at https://elsegundo.xyz/grok/research/contract.json.

Research public X posts and original official sources, including civic calendars. Prepare a South Bay at-a-glance brief with 8–12 short topic clusters when the evidence supports that much; use fewer on a quiet day. Name the actual place and keep publication dates, event dates and observation times separate. Treat an X post as a lead until its factual claims are checked. Do not invent hours, events, job availability or property status.

Select at most 20 useful findings for the site review inbox. Each needs a type, title, concise summary, 1–5 public HTTPS source URLs and observedAt (the time you checked the source, with an offset or Z). Put the source's publication date and the actual event or job dates in the summary when relevant. Use only the fields in the contract; do not submit private messages, applicant data or credentials. If there are no useful findings, say so and skip submission.

Use one stable reportId such as elsegundotoday-YYYY-MM-DD-daily, the local date, timeZone America/Los_Angeles, schemaVersion 1.0, a brief summary, findings and agent {name: "Grok Bot", account: "elsegundotoday"}. Keep the exact final JSON for delivery checks.

If an approved secure credential binding is available, send that JSON to POST https://elsegundo.xyz/api/v1/research with Content-Type: application/json and Authorization: Bearer <PRIVATE_RESEARCH_KEY>. The placeholder means the owner's separately saved secret, never a value pasted into this prompt, a public post, a URL or an ordinary file. Do not expose the key or follow redirects with it.

Only call delivery confirmed after HTTP 202, or HTTP 200 for an identical duplicate, with ok:true and a matching receipt.reportId, receipt.status:"draft_only" and receipt.published:false. Return the receipt and a short brief in this private Bot conversation. On an uncertain delivery, retry only the identical reportId and body; never invent a new ID to get past a failure. On 401, 409 or a configuration error, stop submission and report the problem.

If secure submission is unavailable, keep the sanitized JSON draft in this conversation. If you already have authorized GitHub write access, you may instead propose it as content/research-drafts/<reportId>.json in a pull request to https://github.com/mhoydich/hello-token-reserve. Leave that PR for review. Do not merge, publish site content or post to X in this workflow.

After one successful reviewed test, save this as the daily research skill. Set a daily routine only at the owner's chosen time in America/Los_Angeles, with the same scope and review boundary.

How the X handoff works.

An @bot mention sends a task to your main Grok Bot. Its public reply confirms the handoff; the work and results stay in your Bot conversation.

That handoff does not automatically publish the resulting drafts as @elsegundotoday. Account connections, routines and any publishing permissions belong in your own Grok Bot and X setup.

xAI's setup guide calls for a connected X account, Grok Bot access and at least one Bot you own. It describes the X plugin as optional for the tagged handoff. Follow the current official instructions for your account.

Official setup references

• Tag @bot on X — account connection, handoffs and availability.
• Use the computer and apps — how Grok Bot reads websites and works with connected tools.
• Skills and routines — test a task, then make it repeatable.
• X Help: About @bot — the distinction between @bot and @Grok.
• Store secrets securely — supported private API-key entry, linked from xAI’s computer guide.
• Approvals and privacy — account-level action boundaries and routine approvals.

Official setup documentation checked October 24, 2026. No special xAI partnership, automatic discovery or completed account connection is claimed. Routine webhooks receive work into Grok; our research inbox receives findings from it.

Full source map ↗ · Data manifest ↗ · OpenAPI reference ↗