Menu
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.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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.
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.
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.
| name | ri-pota |
| description | 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. |
Goal: activate every Rhode Island POTA reference by December 31, 2026.
cat src/data/pota/ri-tracker.json | node -e "
const d = JSON.parse(require('fs').readFileSync('/dev/stdin','utf8'));
console.log('Summary:', d.summary);
d.references.filter(r => r.status === 'remaining').forEach(r =>
console.log(r.reference, r.grid, r.name));
"
Or just read src/data/pota/ri-tracker.json directly — it has summary (completed/remaining/total) and a references array with status, latitude, longitude, grid, and name for every park.
mise run pota:ri:travel-times
# or from a different home grid:
mise run pota:ri:travel-times -- --grid FN41gs
Output is sorted by estimated drive time. Requires network for OSRM routing; falls back to haversine if OSRM is unreachable. Default home grid is FN41fr.
mise run pota:ri:rove-clusters
# wider threshold (more parks per cluster):
mise run pota:ri:rove-clusters -- --threshold 60
# include already-activated parks:
mise run pota:ri:rove-clusters -- --all
Groups remaining parks by adjacency (default: 45-min inter-park drive) using connected components. For each cluster, computes a nearest-neighbor round-trip from home and reports ordered stops with segment times and total drive. Isolated parks (no neighbor within threshold) are listed separately. Falls back to haversine if OSRM is unreachable.
pota_spots(location="US-RI") # any active RI activators right now
solar_conditions() # SFI, Kp, overall HF quality
solar_band_outlook() # per-band forecast
mise run pota:update # profile, tracker, park pages
For a full historical refresh:
mise run pota:update --full-backfill
The full backfill refreshes the RI park list and activation history before rebuilding tracker and canonical park-page data.
The public RI checklist and map should link to canonical park pages such as
/radio/pota/US-1234/. Keep POTA.app as the external reference from those park
pages. RI challenge labels are activation metadata on canonical park pages, not
project-owned detail pages.
| Reference | Note |
|---|---|
| US-0513 Block Island NWR | Ferry from Point Judith (~1 hr each way). Half-day minimum. Drive-time estimates are misleading — add ferry time. |
| US-10545 Hillsdale Preserve | Historical/Archaeological Preserve: no antennas staked into the ground. |
| Path | Purpose |
|---|---|
src/data/pota/ri-tracker.json | Generated tracker state — source of truth for status |
src/data/pota/parks.json | Generated canonical POTA park-page data |
data/pota/parks/cache/ | Cached POTA park metadata for /radio/pota/US-1234/ pages |
data/pota/ri/activations.json | Activation ledger (hand-editable if needed) |
data/pota/ri/cache/ | Raw API response caches |
scripts/pota/parks.mjs | Canonical park-page cache and data pipeline |
scripts/pota/ri-tracker.mjs | Tracker data pipeline |
scripts/pota/travel-times.mjs | Drive-time estimator (home → each park) |
scripts/pota/rove-clusters.mjs | Rove cluster finder (groups of nearby parks) |
scripts/pota/lib/routing.mjs | Shared routing utilities (grid, haversine, OSRM) |
src/pages/projects/2026-activate-all-ri-pota.astro | Public tracker page |