Menu
2026 RI→FL road trip planning — read itinerary state, find park clusters per corridor segment, update booking status. Use when the user wants to plan driving legs, find parks to activate, or update the trip itinerary.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | rove-to-fl |
| description | 2026 RI→FL road trip planning — read itinerary state, find park clusters per corridor segment, update booking status. Use when the user wants to plan driving legs, find parks to activate, or update the trip itinerary. |
Goal: drive the I-95 corridor from Providence, RI to Singer Island / Riviera Beach, FL, activating POTA parks along the way. Arrive by June 26, 2026 for Field Day (June 27–28).
| Constraint | Value |
|---|---|
| Work window | 13:00–17:00 local (no activating during this window) |
| Max consecutive camping nights | 2 |
| Arrive FL by | 2026-06-26 |
| Field Day | 2026-06-27 at Singer Island / Riviera Beach |
data/pota/rove-to-fl/itinerary.json is the hand-editable source of truth for the trip plan. It has:
days[] — one entry per travel day with date, states, overnight (type + booking status), parkTargets, notes, approxDriveMilesconstraints — the trip rules aboveovernight.type is one of camp | hotel | home | tbd.
booking.status is one of planned | booked | n/a.
node -e "
const d = JSON.parse(require('fs').readFileSync('data/pota/rove-to-fl/itinerary.json','utf8'));
console.log('Days planned:', d.days.length);
d.days.forEach((day, i) => {
const o = day.overnight;
console.log(\`Day \${i+1} \${day.date}: \${o.type} @ \${o.name} [\${o.booking.status}]\`);
if (day.parkTargets.length) console.log(' Parks:', day.parkTargets.join(', '));
});
"
src/data/pota/rove-to-fl.json has 1,000+ POTA parks within ~75 km of I-95 across 10 states (CT → FL). Filter by state to see what's available for a given leg:
node -e "
const d = JSON.parse(require('fs').readFileSync('src/data/pota/rove-to-fl.json','utf8'));
const state = 'US-NC'; // change as needed
const parks = d.parks.filter(p => p.state === state);
console.log(state, parks.length, 'corridor parks');
parks.sort((a,b) => b.activations - a.activations)
.slice(0,20)
.forEach(p => console.log(p.reference, p.activations, 'acts', p.name));
"
Route summary is in d.route — each entry has code, name, total, corridorCount.
# CT corridor parks, 30-min adjacency, starting from FN41fr (Providence area)
mise run pota:rove-to-fl:rove-clusters -- --state US-CT --threshold 30
# Multiple states (e.g. a leg that crosses VA+NC)
mise run pota:rove-to-fl:rove-clusters -- --state US-VA --state US-NC --threshold 45
# Start grid for a mid-trip leg (e.g. Richmond, VA)
mise run pota:rove-to-fl:rove-clusters -- --state US-NC --grid FM17kk --threshold 45
Uses OSRM for real driving distances; falls back to haversine if OSRM is unreachable.
Adjust --threshold (minutes) to control cluster tightness. The --grid flag sets
the round-trip start point — use your overnight location for that leg.
Edit data/pota/rove-to-fl/itinerary.json directly to:
days[] entriesparkTargets with chosen POTA refsovernight.booking.status from planned → booked and add confirmationapproxDriveMiles as the route gets firmerThe project page at src/pages/projects/2026-06-rove-to-fl.astro renders the itinerary automatically and flags any consecutive-camping violations.
mise run pota:rove-to-fl:update-tracker # fetch all states + rebuild JSON
mise run pota:rove-to-fl:build-tracker-data # rebuild from cache only
| Path | Purpose |
|---|---|
data/pota/rove-to-fl/itinerary.json | Hand-editable trip plan — source of truth |
src/data/pota/rove-to-fl.json | Generated corridor park data (1,000+ parks) |
data/pota/rove-to-fl/cache/ | Raw POTA API caches per state |
scripts/pota/rove-to-fl-tracker.mjs | Corridor park data pipeline |
scripts/pota/rove-clusters.mjs | Rove cluster finder (RI-focused today; extend for corridor) |
scripts/pota/lib/routing.mjs | Shared routing utilities (grid→latlon, haversine, OSRM) |
src/pages/projects/2026-06-rove-to-fl.astro | Public project page |
Draft, edit, clean up, or publish Astro notes for rwjblue.com from rough notes, dictation, screenshots, or an existing draft. Use for work in src/content/notes, including frontmatter, slugs, asset organization, editorial cleanup, social share images, publication readiness, and final validation. POTA activation reports use pota-field-report as a specialized extension of this skill.
Draft publishable Astro notes for Parks on the Air (POTA) activations from dictated or rough mobile field notes. Use when the user wants to record, clean up, or publish a POTA operation recap, activation report, QRP field note, radio field log, portable HF outing, CW activation note, rove, or post-operation field report for rwjblue.com. Extends the repository's note-authoring workflow with POTA-specific links, tags, images, contact maps, and tracker updates.
Generate a concise readership and site-health report for rwjblue.com from locally authenticated Cloudflare APIs. Use when the user asks whether the site is being read, requests traffic or visitor analytics, wants popular content or referrer summaries, or asks whether 404s, errors, performance, cache behavior, or scanner traffic indicate a real problem.
Bootstrap a checked-in POTA contact-map JSON file from an ADI log for a field note.
RI POTA challenge planning — find remaining parks, estimate drive times, check live spots and conditions. Use when the user asks about activating RI parks, which parks are left, or where to go for a POTA outing.
Geospatial query capabilities — geocoding, nearby search, routing, place details, elevation. Trigger when the user mentions locations, addresses, coordinates, navigation, "what's nearby", "how to get there", distance/duration, or any question that inherently involves geographic information — even if they don't explicitly say "map". Update when new tools are added or tool parameters change.