Have three Grok Bots research and plan your next trip
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 prompt.
Use cases
Methods
Paste into a general LLM and have three Grok Bots research and plan your next trip.
LLMPrompt
Prompt
Copied 0
Set up a three-Bot travel team with these roles: 1: The Trip Planner. Ask me for my departure city, dates, travellers, total budget, preferred travel pace and non-negotiables. Turn my answers into one shared brief for the team. Clarify anything missing before research begins. 2: The Options Researcher. Use the shared brief to find three flight-and-hotel combinations. Compare total costs, including baggage, transfers and disclosed mandatory fees, plus flight times, hotel location and cancellation terms. Include source links, when prices were checked and any unknown costs. Recommend the best fit and explain the tradeoffs. Bring me the comparison and wait for my choice before starting the itinerary. 3: The Itinerary Builder. Use my chosen option and the shared brief to build a realistic daily plan. Check opening hours, group nearby activities and allow for travel time, meals and downtime. Include activity costs against the remaining budget. Keep suggested bookings separate from confirmed bookings. As Chief of Staff, coordinate the handoffs so I don’t have to move information between Bots. If my requirements change, update the shared brief and have the affected work revised. Flag anything you cannot verify. Give me the booking links and recheck selected prices and availability when I’m ready to book. Don’t book or pay for anything.
No methods for that filter.
Add a method
How you would do this use case, in plain words. Anyone can post.
The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.
- All use cases:
GET /api/jobs - This use case:
GET /api/jobs/three-bot-travel-team - Schema:
GET /api/jobs/schema - Add a method:
POST /api/jobs/method— same fields as the form. No API key yet.
A bad request returns JSON like {"error":"Method description is required"} with status 400.
| Field | What it is |
|---|---|
jobId | This use case. Review queue uses useCaseTitle + email instead. |
summary | Method description. Shown on the card. Also accepts title. |
products | Optional. Array of { name, url }. Legacy: tools. |
prompts | Optional. Array of prompt strings. Legacy: one prompt string. |
skills | Optional. Array of { text, url }. Legacy: skill + skillUrl. |
authorName | Author name. Legacy live field: postedBy. |
author | Optional 𝕏 handle. Legacy live field: creditHandle. |
parts | Optional. Inferred from products, prompts, and skills if omitted.standalone-product, ai-agent, ai-tool, skill, prompt. Do not send a prompt/product/agent/skill radio. |
{
"jobId": "three-bot-travel-team",
"summary": "Turns a Zoom recording into notes and action items with owners",
"products": [
{
"name": "Claude",
"url": "https://claude.ai"
}
],
"prompts": [
"Turn this transcript into notes and action items with owners."
],
"skills": [
{
"text": "Watch a folder. When a transcript lands, write notes with owners.",
"url": "https://example.com/zoom-notes.md"
}
],
"authorName": "Alex Rivera",
"author": "@handle"
}