agentleFS
Sign inStart free
leonardoaraujosantosleonardoaraujosantos/my_ai_skills/planetary-dashboard/SKILL.md

planetary-dashboard

Skill1 starsChanged 4 months agoLicence not identifiedView on GitHub

Build 3D web geospatial / planetary dashboards (CesiumJS globe and/or MapLibre 3D terrain) that fuse live public feeds, analysis and AI on one map, distilled from three shipped systems - God's Eye View (live aircraft/ships/satellites/quakes/fires/weather/cameras on a photoreal globe with sensor shaders, cockpit, voice agent, scene director), GeoSphere (SvelteKit MVVM + FastAPI hexagonal backend with STAC spectral indices, RF coverage, SSE analysis, MCP/chat agent) and KANZI (MapLibre digital twin with real-sun terrain, underground WebGL, GDAL pipeline with provenance + snapshots, brandkits, sovereign deploy). Ships a keyless Vite+Cesium starter, a curated catalog of 50 public data sources with a live probe, and references for architecture, proxies, rendering, UI, features, AI agents, backend, pipelines and QA. Use when the user wants to build, extend or review a 3D globe / map dashboard, digital twin, situational-awareness or OSINT console, satellite/flight/ship tracker, earth-observation viewer, or asks "which public feed has X", "add a live layer", "make it look like a spy-satellite console", "add a voice/chat agent to the map", or "make the map work offline / without API keys". Triggers - "3D globe", "Cesium", "CesiumJS", "MapLibre 3D", "planetary dashboard", "geospatial dashboard", "digital twin", "live flights on a map", "ADS-B", "AIS", "TLE / satellite tracker", "FIRMS fires", "earthquake map", "photorealistic 3D tiles", "sensor shader / FLIR / night vision", "war room map".

  • Reads credentials
  • Installs packages

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 2 are distinctive, and 7 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 7

    Very specific

    Tied to their project's names, files or tools. Probably skip.

The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free