Simulated Roadtrip

Generate a narrated road trip with GPS-verified stops and themed descriptions using real Google Maps data, posted in timed updates or chat.

Security Scan

The skill largely does what it claims (calls a Turai API to generate stops), but there are multiple small inconsistencies (missing required env var in registry metadata, claims about Google Maps data and automatic posting that the code does not implement) that warrant caution before installing or running with real credentials.

Purpose & Capability

The description promises 'GPS-verified stops' and 'real Google Maps data', but the code calls only https://turai.org/api/agent/roadtrip and does not directly use Google Maps APIs. That could be legitimate if Turai provides Google-sourced data, but the skill metadata in the registry also claims 'Required env vars: none' while both SKILL.md and the script require TURAI_API_KEY — a clear metadata/code mismatch.

Instruction Scope

SKILL.md and the script are narrowly scoped: they send a POST to the Turai endpoint, format the returned stops, optionally save JSON and print/drip them to stdout. The SKILL.md mentions posting updates to chat/Moltbook/messaging channels, but the script itself does not integrate with any messaging API — posting must be performed by the agent or other glue code outside the script.

Install Mechanism

No install spec and only a small Node script are provided; nothing in the package downloads or executes remote artifacts. This is low-risk from an install perspective.

Credentials

Runtime requires a TURAI_API_KEY (used as x-api-key to turai.org) which is proportional to the described functionality. However, the registry metadata wrongly lists no required env vars/primary credential — that inconsistency is problematic because users may not realize they must provide an API key before running.

Persistence & Privilege

The skill does not request persistent placement (always:false) and does not modify other skills or system-wide settings. It only optionally writes an output JSON file path provided by the user.

What to consider before installing

Before installing or running: (1) Be aware you must supply a TURAI_API_KEY (SKILL.md and script require it, but the registry metadata does not list it). (2) Confirm what Turai.org actually returns and whether it uses Google Maps data if that matters to you — the script only calls Turai, not Google directly. (3) The script only prints and can save JSON; it does not automatically post to chat/social platforms — if you expect automatic posting, review or add the integration code yourself. (4) Because the source and homepage are not provided, consider running the script in a sandbox or with a limited/revocable API key first, inspect network traffic, and read the code (it's short) to verify behavior. (5) If you need stronger assurance, ask the publisher for provenance (homepage, source repo, and explanation of data sources).

Let your Clawbot go on a GPS-grounded road trip through the real world. Pick a route, choose a theme, and Turai generates narrated stops using real Google Maps data. Your agent posts updates as it "travels."

Concept

Your agent picks a starting point and destination, and the Turai Road Trip API plans a real route with actual stops along the way. Each stop includes:

• Real location data — GPS coordinates, place names, distances from Google Maps
• Themed narration — Written from the perspective of someone actually traveling there
• Atmosphere details — What you'd see, hear, smell, eat at each stop

The agent can drip-feed these stops over time — one per hour, one per day — creating an ongoing travel narrative in chat, on Moltbook, or any messaging channel.

Themes

Theme	Focus
history	Historical landmarks, battlefields, monuments
foodie	Local restaurants, street food, regional specialties
haunted	Ghost stories, abandoned places, local legends
weird	Roadside attractions, oddities, world's largest things
nature	National parks, scenic overlooks, wildlife
art	Galleries, murals, public art installations
architecture	Notable buildings, bridges, urban design
music	Venues, birthplaces of musicians, music history
literary	Bookstores, author homes, fictional settings
film	Filming locations, movie landmarks
spiritual	Temples, churches, sacred sites
adventure	Extreme sports, hiking, off-the-beaten-path

Setup

1. Get a Turai API key from turai.org
2. Set the environment variable:

   export TURAI_API_KEY="your-key-here"
   

Usage

From the command line

# Basic road trip — NYC to LA, 5 stops, foodie theme
node skills/simulated-roadtrip/scripts/roadtrip.mjs \
  --from "New York City" \
  --to "Los Angeles" \
  --theme foodie \
  --stops 5

# Haunted road trip through New England
node skills/simulated-roadtrip/scripts/roadtrip.mjs \
  --from "Salem, MA" \
  --to "Sleepy Hollow, NY" \
  --theme haunted \
  --stops 4

# Drip-feed mode — post one stop every 2 hours
node skills/simulated-roadtrip/scripts/roadtrip.mjs \
  --from "Nashville, TN" \
  --to "New Orleans, LA" \
  --theme music \
  --stops 6 \
  --drip 2h

# Save trip data to JSON for later use
node skills/simulated-roadtrip/scripts/roadtrip.mjs \
  --from "Tokyo" \
  --to "Kyoto" \
  --theme art \
  --stops 4 \
  --output trip.json

Drip-feed intervals

• 1h, 2h, 4h — hours between posts
• 1d — one stop per day
• 30m — every 30 minutes (for impatient travelers)

From your agent

"Take a road trip from Chicago to Austin, music theme, 5 stops"

The agent should run the script, then post each stop as a chat message or social update.

API Reference

Endpoint: POST https://turai.org/api/agent/roadtrip

Headers:

• x-api-key: Your Turai API key
• Content-Type: application/json

Body:

{
  "from": "New York City",
  "to": "Los Angeles",
  "theme": "foodie",
  "stops": 5
}

Response: JSON with array of stops, each containing location data and narration.

Files

• SKILL.md — This file
• scripts/roadtrip.mjs — Main script