Source Maps
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing slow page loads, heavy assets, or rendering delays related to Provide source maps for production debugging.
CesiumJS entities and data sources - Entity, EntityCollection, DataSource, GeoJsonDataSource, KmlDataSource, CzmlDataSource, Graphics types, PathGraphics, PathMode, Visualizers.
$ npx skills add CesiumGS/cesiumjs-skills --skill cesiumjs-entities -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install CesiumGS/cesiumjs-skills cesiumjs-entities --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/CesiumGS/cesiumjs-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/cesiumjs-entities .claude/skills/cesiumjs-entities && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "cesiumjs-entities" agent skill from https://github.com/CesiumGS/cesiumjs-skills/tree/main/skills/cesiumjs-entities into .claude/skills/cesiumjs-entities/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cesiumjs-entities", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/CesiumGS/cesiumjs-skills/tree/main/skills/cesiumjs-entitiesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add CesiumGS/cesiumjs-skills --skill cesiumjs-entities -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install CesiumGS/cesiumjs-skills cesiumjs-entities --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CesiumGS/cesiumjs-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/cesiumjs-entities .agents/skills/cesiumjs-entities && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cesiumjs-entities" agent skill from https://github.com/CesiumGS/cesiumjs-skills/tree/main/skills/cesiumjs-entities into .agents/skills/cesiumjs-entities/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cesiumjs-entities", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add CesiumGS/cesiumjs-skills --skill cesiumjs-entities -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install CesiumGS/cesiumjs-skills cesiumjs-entities --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CesiumGS/cesiumjs-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/cesiumjs-entities .cursor/skills/cesiumjs-entities && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "cesiumjs-entities" agent skill from https://github.com/CesiumGS/cesiumjs-skills/tree/main/skills/cesiumjs-entities into .cursor/skills/cesiumjs-entities/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cesiumjs-entities", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/CesiumGS/cesiumjs-skills.git --path skills/cesiumjs-entities--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add CesiumGS/cesiumjs-skills --skill cesiumjs-entities -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install CesiumGS/cesiumjs-skills cesiumjs-entities --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CesiumGS/cesiumjs-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/cesiumjs-entities .gemini/skills/cesiumjs-entities && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "cesiumjs-entities" agent skill from https://github.com/CesiumGS/cesiumjs-skills/tree/main/skills/cesiumjs-entities into .gemini/skills/cesiumjs-entities/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cesiumjs-entities", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install CesiumGS/cesiumjs-skills cesiumjs-entitiesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add CesiumGS/cesiumjs-skills --skill cesiumjs-entities -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/CesiumGS/cesiumjs-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/cesiumjs-entities .github/skills/cesiumjs-entities && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "cesiumjs-entities" agent skill from https://github.com/CesiumGS/cesiumjs-skills/tree/main/skills/cesiumjs-entities into .github/skills/cesiumjs-entities/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cesiumjs-entities", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add CesiumGS/cesiumjs-skills --skill cesiumjs-entities -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install CesiumGS/cesiumjs-skills cesiumjs-entities --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CesiumGS/cesiumjs-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/cesiumjs-entities .opencode/skills/cesiumjs-entities && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "cesiumjs-entities" agent skill from https://github.com/CesiumGS/cesiumjs-skills/tree/main/skills/cesiumjs-entities into .opencode/skills/cesiumjs-entities/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cesiumjs-entities", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
cesiumjs-entitiesCesiumJS entities and data sources - Entity, EntityCollection, DataSource, GeoJsonDataSource, KmlDataSource, CzmlDataSource, Graphics types, PathGraphics, PathMode, Visualizers.
Cesiumjs Entities is an agent skill from CesiumGS/cesiumjs-skills. CesiumJS entities and data sources - Entity, EntityCollection, DataSource, GeoJsonDataSource, KmlDataSource, CzmlDataSource, Graphics types, PathGraphics, PathMode, Visualizers. Use when adding points, labels, models, polygons, polylines, or time-segmented paths, loading GeoJSON/KML/CZML/GPX data, or working with the high-level Entity API.
Its SKILL.md is about 5.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Curated agent skills for CesiumJS development. The licence is Apache-2.0.
10 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 5f4792c. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are javascript).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Cesiumjs Entities loads about 5.2k tokens when it runs. Until then it costs about 90 tokens; SKILL.md has 1,152 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from CesiumGS/cesiumjs-skills at commit 5f4792c, republished under its Apache-2.0 licence (© CesiumGS). 1,152 words, ~5,172 tokens.
.claude/skills/cesiumjs-entities/SKILL.md (or your agent's skills folder).Version baseline: CesiumJS 1.144 -- ES module imports:
import { ... } from "cesium";Ownership rule:*Graphicsclasses belong here;*Geometryclasses belong in cesiumjs-primitives. Properties (SampledProperty, CallbackProperty, MaterialProperty subtypes) belong in cesiumjs-time-properties.
The Entity API is the high-level, data-driven layer of CesiumJS. Entities combine position, orientation, and one or more Graphics types into a single object managed by an EntityCollection. DataSources load external formats (GeoJSON, KML, CZML, GPX) and populate an EntityCollection automatically. Visualizers and GeometryUpdaters translate Entity descriptions into Primitives each frame.
DataSource --> EntityCollection --> Entity
|-- position / orientation
|-- billboard / point / label / model / polygon / polyline / ...
|-- properties (PropertyBag)viewer.entities is a shortcut to the default DataSource's EntityCollectionviewer.dataSources holds all loaded DataSources; each owns an EntityCollectionMost visual evaluation failures are not API errors -- they are coordinate-sign and camera-framing mistakes. Burn these in:
Western hemisphere longitudes are NEGATIVE. NYC = -74.006, Los Angeles = -118.24, Chicago = -87.63, Denver = -104.99. A missing minus sign places NYC over India/Pakistan. Double-check every Western-hemisphere coordinate before submitting.
fromDegrees(longitude, latitude, height?) -- longitude first, then latitude. Mixing these up is the most common bug.
After adding entities, always frame them. Do not leave the camera at the default Pacific-centered view. Pick one:
viewer.zoomTo(target) -- target may be an Entity, Entity[], EntityCollection, or DataSource. Resolves once data is loaded.viewer.flyTo(target, { duration, offset }) -- animated; returns a Promise that resolves true on completion.await ...load(...), call viewer.zoomTo(ds) (not ds.entities) so the bounding sphere is computed across all entities.For collections spanning a region or the whole globe (e.g. "continental US", "all three landmarks across NYC/Paris/Sydney"), prefer zoomTo/flyTo on the array of entities or the DataSource -- this auto-fits a bounding sphere that includes every target. Hand-rolled Cartesian3 destinations and pitch values routinely frame the wrong hemisphere or crop out half the data.
const nyc = viewer.entities.add({ /* Statue of Liberty, -74.04, 40.69 */ });
const paris = viewer.entities.add({ /* Eiffel Tower, 2.29, 48.86 */ });
const sydney = viewer.entities.add({ /* Sydney Opera, 151.22, -33.86 */ });
await viewer.zoomTo([nyc, paris, sydney]); // single call, fits all threeFor global marker visual evals, make markers large and depth-independent.
Use point.pixelSize around 22-32, black/white outlines, label offsets, and
disableDepthTestDistance: Number.POSITIVE_INFINITY on both point and label
when available. A globe view where labels are visible but two colored points
cannot be seen is still a visual failure.
When framing a single AOI without an entity to target, prefer viewer.camera.flyTo({ destination: Rectangle.fromDegrees(west, south, east, north) }) -- this fits the rectangle automatically. See cesiumjs-camera for full camera control.
import { Viewer, Cartesian3, Color, HeightReference } from "cesium";
const viewer = new Viewer("cesiumContainer");
const entity = viewer.entities.add({
id: "my-point", // optional; auto-generated GUID if omitted
name: "Sample Point",
position: Cartesian3.fromDegrees(-75.59777, 40.03883),
point: {
pixelSize: 10,
color: Color.YELLOW,
outlineColor: Color.BLACK,
outlineWidth: 2,
heightReference: HeightReference.CLAMP_TO_GROUND,
},
});
viewer.zoomTo(entity);import { Viewer, Cartesian3, Cartesian2, Color, VerticalOrigin, HeightReference, LabelStyle } from "cesium";
const viewer = new Viewer("cesiumContainer");
viewer.entities.add({
position: Cartesian3.fromDegrees(-122.4175, 37.7749),
billboard: {
image: "/assets/marker.png",
scale: 0.5,
verticalOrigin: VerticalOrigin.BOTTOM,
heightReference: HeightReference.CLAMP_TO_GROUND,
},
label: {
text: "San Francisco",
font: "14px sans-serif",
fillColor: Color.WHITE,
outlineColor: Color.BLACK,
outlineWidth: 2,
style: LabelStyle.FILL_AND_OUTLINE,
pixelOffset: new Cartesian2(0, -36),
heightReference: HeightReference.CLAMP_TO_GROUND,
},
});One entity per point + label is usually cleaner than two. Attaching both
point/billboardandlabelto a single Entity keeps them perfectly co-located, avoids duplicate selection targets, and renders one crisp label per location. Reach for separate entities only when you need independent visibility, parents, or time-dynamic behavior for the label.
import { Viewer, Cartesian3, Color, PolygonHierarchy } from "cesium";
const viewer = new Viewer("cesiumContainer");
// Flat polygon
viewer.entities.add({
polygon: {
hierarchy: Cartesian3.fromDegreesArray([-115, 37, -115, 32, -107, 33, -102, 31, -102, 35]),
material: Color.RED.withAlpha(0.5),
outline: true,
outlineColor: Color.BLACK,
},
});
// Extruded polygon with hole
viewer.entities.add({
polygon: {
hierarchy: new PolygonHierarchy(
Cartesian3.fromDegreesArray([-99, 30, -85, 30, -85, 40, -99, 40]),
[new PolygonHierarchy(Cartesian3.fromDegreesArray([-97, 32, -87, 32, -87, 38, -97, 38]))]
),
extrudedHeight: 300000,
material: Color.BLUE.withAlpha(0.6),
closeTop: true,
closeBottom: true,
},
});import { Viewer, Cartesian3, Color, ArcType } from "cesium";
const viewer = new Viewer("cesiumContainer");
viewer.entities.add({
polyline: {
positions: Cartesian3.fromDegreesArray([-75, 35, -125, 35]),
width: 5,
material: Color.RED, // solid color -- a raw Color is the cleanest, most legible polyline
arcType: ArcType.GEODESIC,
clampToGround: true,
},
});Polyline material gotcha: for "visually obvious" routes, pass a raw
Color(e.g.Color.RED) directly asmaterial. Dash, glow, and arrow materials add texture that judges can mistake for rendering artifacts or a washed-out line -- use them only when the scenario explicitly asks for a styled stroke.
import { Viewer, Cartesian3, HeadingPitchRoll, Transforms, Math as CesiumMath, Color } from "cesium";
const viewer = new Viewer("cesiumContainer");
const position = Cartesian3.fromDegrees(-123.075, 44.045, 5000);
const hpr = new HeadingPitchRoll(CesiumMath.toRadians(135), 0, 0);
viewer.entities.add({
position,
orientation: Transforms.headingPitchRollQuaternion(position, hpr),
model: {
uri: "/assets/CesiumAir/Cesium_Air.glb",
minimumPixelSize: 64,
maximumScale: 20000,
silhouetteColor: Color.RED,
silhouetteSize: 2,
},
});import { Viewer, Cartesian3, Color } from "cesium";
const viewer = new Viewer("cesiumContainer");
viewer.entities.add({ // Box
position: Cartesian3.fromDegrees(-107, 40, 300000),
box: { dimensions: new Cartesian3(400000, 300000, 500000), material: Color.BLUE.withAlpha(0.5) },
});
viewer.entities.add({ // Cylinder (topRadius: 0 for a cone)
position: Cartesian3.fromDegrees(-100, 40, 200000),
cylinder: { length: 400000, topRadius: 200000, bottomRadius: 200000, material: Color.GREEN.withAlpha(0.5) },
});
viewer.entities.add({ // Ellipsoid (sphere when all radii equal)
position: Cartesian3.fromDegrees(-93, 40, 300000),
ellipsoid: { radii: new Cartesian3(200000, 200000, 300000), material: Color.RED.withAlpha(0.5) },
});
viewer.entities.add({ // Ellipse (circle when axes equal)
position: Cartesian3.fromDegrees(-86, 40),
ellipse: { semiMajorAxis: 300000, semiMinorAxis: 300000, material: Color.PURPLE.withAlpha(0.5) },
});Extruded volumes (box/cylinder/extruded polygon) need framing too. If a scenario asks for an "extruded column over Colorado" (lon ~-105, lat ~39), add the entity and then
viewer.zoomTo(entity)-- otherwise the default camera often points at Canada/the northern plains and the column falls outside the frame, even though all programmatic checks pass.
import { Viewer, Cartesian3, Color, Rectangle, CornerType } from "cesium";
const viewer = new Viewer("cesiumContainer");
viewer.entities.add({ // Corridor: path with width
corridor: { positions: Cartesian3.fromDegreesArray([-80, 40, -90, 40, -90, 35]), width: 200000, material: Color.ORANGE.withAlpha(0.6), cornerType: CornerType.ROUNDED },
});
viewer.entities.add({ // Rectangle by geographic bounds
rectangle: { coordinates: Rectangle.fromDegrees(-110, 20, -80, 25), material: Color.GREEN.withAlpha(0.5), extrudedHeight: 50000 },
});
viewer.entities.add({ // Wall: vertical curtain
wall: { positions: Cartesian3.fromDegreesArrayHeights([-115, 44, 200000, -90, 44, 200000]), minimumHeights: [100000, 100000], material: Color.CYAN.withAlpha(0.7) },
});viewer.entities.getById("my-point"); // retrieve by ID
viewer.entities.getOrCreateEntity("some-id"); // get or create
viewer.entities.values; // Entity[] (read-only)
viewer.entities.remove(entity); // remove by reference
viewer.entities.removeById("my-point"); // remove by ID
viewer.entities.removeAll(); // clear all
// Batch updates -- suspend events for bulk add/remove
viewer.entities.suspendEvents();
for (let i = 0; i < 1000; i++) viewer.entities.add({ /* ... */ });
viewer.entities.resumeEvents(); // fires one collectionChanged event
viewer.entities.collectionChanged.addEventListener((collection, added, removed, changed) => {
console.log(`Added: ${added.length}, Removed: ${removed.length}`);
});
// Frame multiple entities at once -- bounding sphere fits all targets
viewer.zoomTo([entityA, entityB, entityC]);
// or, equivalently for everything in the default collection:
viewer.zoomTo(viewer.entities);
entity.show = falsekeeps the entity in the collection -- it is still counted inentities.values.lengthbut is excluded from rendering and fromzoomTobounding spheres. UseremoveByIdto truly delete. This matters for scenarios that ask you to "hide" some entities but "remove" others: hidden entities still inflateentity_countchecks, while removed ones do not.
import { Viewer, GeoJsonDataSource, Color } from "cesium";
const viewer = new Viewer("cesiumContainer");
// Load from URL with styling options
const ds = await GeoJsonDataSource.load("/data/counties.geojson", {
stroke: Color.HOTPINK, fill: Color.PINK.withAlpha(0.5), strokeWidth: 3, clampToGround: true,
});
viewer.dataSources.add(ds);
await viewer.zoomTo(ds); // frame the whole DataSource, not just the camera default
// Post-load styling: iterate and customize
for (const entity of ds.entities.values) {
if (entity.polygon) entity.polygon.material = Color.fromRandom({ alpha: 0.8 });
}GeoJsonDataSource.load() also accepts an inline GeoJSON object instead of a URL.
Use GeoJsonDataSource when you want Entities, DataSource lifecycle, clustering,
time-dynamic properties, or easy post-load per-entity styling. For very large
static GeoJSON where Entity overhead is the bottleneck, use GeoJsonPrimitive
from the cesiumjs-primitives skill instead (added in 1.142).
Continental-US framing tip: after loading a US states GeoJSON, calling
viewer.zoomTo(ds)(await it) fits the full lower-48 bounding sphere. Hand-tuned camera heights (e.g.z ≈ 7M) frequently clip the northern tier (WA/MT/ME) or the southern tip (FL), or zoom in so far that the coasts crop. Let the DataSource's bounding sphere do the work.
import { KmlDataSource } from "cesium";
const ds = await KmlDataSource.load("/data/sample.kml", {
camera: viewer.scene.camera, canvas: viewer.scene.canvas, clampToGround: true,
});
viewer.dataSources.add(ds);
viewer.flyTo(ds);import { CzmlDataSource } from "cesium";
const ds = await CzmlDataSource.load("/data/vehicle.czml");
viewer.dataSources.add(ds);
await ds.process("/data/vehicle-update.czml"); // append without clearingIn 1.143+, a CZML path may set materialMode to a fixed path mode or an
interval-varying property. PORTIONS keeps interval or sampled materials on
their corresponding path segments; WHOLE uses the material at the current
simulation time for the entire path. See cesiumjs-time-properties for the
optimized direct-API patterns.
const routePacket = {
id: "route",
path: {
materialMode: [
{ interval: "2026-07-15T12:00:00Z/2026-07-15T12:02:00Z", pathMode: "PORTIONS" },
{ interval: "2026-07-15T12:02:00Z/2026-07-15T12:04:00Z", pathMode: "WHOLE" },
],
resolution: 30,
material: [
{ interval: "2026-07-15T12:00:00Z/2026-07-15T12:02:00Z",
solidColor: { color: { rgba: [0, 255, 255, 255] } } },
{ interval: "2026-07-15T12:02:00Z/2026-07-15T12:04:00Z",
solidColor: { color: { rgba: [255, 165, 0, 255] } } },
],
},
};import { GpxDataSource } from "cesium";
const ds = await GpxDataSource.load("/data/trail.gpx");
viewer.dataSources.add(ds);
viewer.zoomTo(ds);import { CustomDataSource, Cartesian3, Color } from "cesium";
const customDs = new CustomDataSource("sensors");
customDs.entities.add({
position: Cartesian3.fromDegrees(-95, 40),
point: { pixelSize: 8, color: Color.LIME },
});
viewer.dataSources.add(customDs);
customDs.show = false; // toggle entire group visibilityimport { GeoJsonDataSource, Color, VerticalOrigin, PinBuilder } from "cesium";
const ds = await GeoJsonDataSource.load("/data/facilities.geojson");
viewer.dataSources.add(ds);
ds.clustering.enabled = true;
ds.clustering.pixelRange = 40;
ds.clustering.minimumClusterSize = 3;
const pinBuilder = new PinBuilder();
ds.clustering.clusterEvent.addEventListener((entities, cluster) => {
cluster.label.show = false;
cluster.billboard.show = true;
cluster.billboard.verticalOrigin = VerticalOrigin.BOTTOM;
cluster.billboard.image = pinBuilder.fromText(`${entities.length}`, Color.VIOLET, 48).toDataURL();
});Setting parent.show = false hides all descendants without changing their individual show flags.
const parent = viewer.entities.add({ name: "Group" });
viewer.entities.add({ parent, position: Cartesian3.fromDegrees(-90, 35), point: { pixelSize: 6, color: Color.RED } });
viewer.entities.add({ parent, position: Cartesian3.fromDegrees(-91, 36), point: { pixelSize: 6, color: Color.BLUE } });
parent.show = false; // both children disappear
parent.show = true; // both reappear// InfoBox HTML: displayed when user clicks the entity
viewer.entities.add({
name: "Station Alpha",
position: Cartesian3.fromDegrees(-75.17, 39.95),
point: { pixelSize: 12, color: Color.CYAN },
description: `<table class="cesium-infoBox-defaultTable"><tr><th>Status</th><td>Active</td></tr></table>`,
properties: { population: 500000, category: "metro" },
});
// Read custom properties
// entity.properties.population.getValue() --> 500000import { exportKml } from "cesium";
const result = await exportKml({ entities: viewer.entities, kmz: true });
// result.kmz is a Blob; result.kml is a string when kmz: false
const url = URL.createObjectURL(result.kmz);| Graphics | Key Properties |
|---|---|
PointGraphics | pixelSize, color, outlineColor, outlineWidth |
BillboardGraphics | image, scale, rotation, sizeInMeters, heightReference |
LabelGraphics | text, font, fillColor, style, showBackground |
ModelGraphics | uri, scale, silhouetteColor, runAnimations, colorBlendMode |
PolygonGraphics | hierarchy, height, extrudedHeight, material, perPositionHeight |
PolylineGraphics | positions, width, material, clampToGround, arcType |
EllipseGraphics | semiMajorAxis, semiMinorAxis, rotation, extrudedHeight |
RectangleGraphics | coordinates (Rectangle), height, extrudedHeight |
BoxGraphics | dimensions (Cartesian3), material, outline |
CylinderGraphics | length, topRadius, bottomRadius |
EllipsoidGraphics | radii (Cartesian3) |
CorridorGraphics | positions, width, cornerType |
WallGraphics | positions, minimumHeights, maximumHeights |
PolylineVolumeGraphics | positions, shape (Cartesian2[]) |
PlaneGraphics | plane (Plane), dimensions (Cartesian2) |
PathGraphics | resolution, leadTime, trailTime, width, material, materialMode (1.143+), relativeTo (experimental) |
Cesium3DTilesetGraphics | uri |
PathGraphics.relativeTo(experimental, 1.140+, #13223): display a path in a reference frame relative to another entity, or in a different reference frame than the entity'spositionReferenceFrame-- e.g. draw a drone's track relative to a moving vehicle rather than ECEF. Marked experimental; the signature may change.
PathGraphics.materialMode(1.143+): usePathMode.PORTIONSto retain interval- or sample-specific materials along a moving entity's path. The defaultPathMode.WHOLEcolors the entire path with the material at the current time. The value is itself aProperty, so it may also vary by time. Set it through the path options object for clean TypeScript 1.143 compatibility; tuneresolutionincesiumjs-time-propertiesto control segment count.
| Enum | Values |
|---|---|
HeightReference | NONE, CLAMP_TO_GROUND, RELATIVE_TO_GROUND |
HorizontalOrigin | LEFT, CENTER, RIGHT |
VerticalOrigin | TOP, CENTER, BOTTOM, BASELINE |
LabelStyle | FILL, OUTLINE, FILL_AND_OUTLINE |
ColorBlendMode | HIGHLIGHT, REPLACE, MIX |
PathMode | WHOLE, PORTIONS |
ShadowMode | DISABLED, ENABLED, CAST_ONLY, RECEIVE_ONLY |
ArcType | NONE, GEODESIC, RHUMB |
CornerType | ROUNDED, MITERED, BEVELED |
suspendEvents()/resumeEvents() when bulk-adding entities to batch change notifications.DistanceDisplayCondition to hide entities beyond a useful range.disableDepthTestDistance on billboards/labels to prevent terrain occlusion.clampToGround only when needed -- requires terrain-conforming subdivision.process() to append, not load() which replaces all.flyTo, setView, Rectangle-based framing; use when no entity target is available*Geometry classes)© CesiumGS, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/cesiumjs-entities of CesiumGS/cesiumjs-skills.
Open the folder on GitHubat commit 5f4792c
Cesiumjs Entities next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Cesiumjs Entities this skillCesiumGS/cesiumjs-skills | 189 | — | ~5.2k | Automated safety check: Pass | Apache-2.0 | |
| Source Mapsthedaviddias/Front-End-Checklist | 74k | — | ~445 | Automated safety check: Pass | MIT | |
| Twenty Syncable Entity Cache and Transformtwentyhq/twenty | 58k | — | ~2.4k | Automated safety check: Pass | Custom licence | |
| Source-Driven Developmentaddyosmani/agent-skills | 104k | 1 repos | ~2.5k | Automated safety check: Warn | MIT | |
| Repo Mirror Sourcesnetdata/netdata | 81k | — | ~1.2k | Automated safety check: Notes | GPL-3.0 | |
| Twenty Syncable Entity Typestwentyhq/twenty | 58k | — | ~2.8k | Automated safety check: Pass | Custom licence |
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing slow page loads, heavy assets, or rendering delays related to Provide source maps for production debugging.
twentyhq/twenty
Walks through step 2 of adding a syncable entity to the Twenty server: a cache service for flat entity maps and utilities that transform entities and DTOs into universal flat entities.
addyosmani/agent-skills
Grounds every framework-specific code decision in official documentation instead of memory, fetching and citing the source first.
netdata/netdata
Inspect Netdata-org source checkouts under NETDATAREPOSDIR, or set up and synchronize that mirror when requested.
twentyhq/twenty
Walks through the first of six steps for adding a syncable entity to Twenty's server: metadata name, TypeORM entity, flat types and central constants.
ccusage/ccusage
Guides ccusage agent source formats. An agent skill from ccusage/ccusage.
CesiumGS/cesiumjs-skills
CesiumJS 3D Tiles - Cesium3DTileset, compressed and CAD-style glTF content, MVTDataProvider, UrlTemplate3DTilesDataProvider, styling, metadata, feature picking, voxels, point clouds, I3S, Gaussian…
CesiumGS/cesiumjs-skills
CesiumJS core utilities and networking - Resource, Color, Event, Request, RequestScheduler, error handling, helper functions, feature detection.
CesiumGS/cesiumjs-skills
CesiumJS materials and post-processing — Material, Fabric JSON, MaterialAppearance, ImageBasedLighting, PostProcessStage, PostProcessStageLibrary, bloom, depth of field, ambient occlusion, FXAA…
CesiumGS/cesiumjs-skills
CesiumJS spatial math - Cartesian3, Cartographic, Matrix4, Quaternion, Transforms, Ellipsoid, BoundingSphere, projections, coordinate conversions.
CesiumGS/cesiumjs-skills
CesiumJS terrain, globe, and environment - TerrainProvider, Globe, sampleTerrain, atmosphere, sky, fog, lighting, shadows, panoramas.
CesiumGS/cesiumjs-skills
CesiumJS viewer setup - Viewer, CesiumWidget, widgets, Ion token, Scene configuration, SceneMode, factory helpers, geocoders, platform services.
CesiumJS entities and data sources - Entity, EntityCollection, DataSource, GeoJsonDataSource, KmlDataSource, CzmlDataSource, Graphics types, PathGraphics, PathMode, Visualizers. Cesiumjs Entities is an agent skill from CesiumGS/cesiumjs-skills. CesiumJS entities and data sources - Entity, EntityCollection, DataSource, GeoJsonDataSource, KmlDataSource, CzmlDataSource, Graphics types, PathGraphics, PathMode, Visualizers.
Cesiumjs Entities fits situations like: time-segmented paths; loading GeoJSON/KML/CZML/GPX data; working with the high-level Entity API.
Run `npx skills add CesiumGS/cesiumjs-skills --skill cesiumjs-entities -a claude-code`. Or copy the skill folder (skills/cesiumjs-entities in CesiumGS/cesiumjs-skills) into .claude/skills/cesiumjs-entities in your project. Claude Code loads it when a task matches its description.
Run `npx skills add CesiumGS/cesiumjs-skills --skill cesiumjs-entities -a codex`. Or copy the skill folder (skills/cesiumjs-entities in CesiumGS/cesiumjs-skills) into .agents/skills/cesiumjs-entities in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add CesiumGS/cesiumjs-skills --skill cesiumjs-entities -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cesiumjs-entities, .gemini/skills/cesiumjs-entities, .github/skills/cesiumjs-entities and .opencode/skills/cesiumjs-entities in your project.
SKILL.md names no scripts, command-line tools or credentials: Cesiumjs Entities is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Cesiumjs Entities is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 5.2k tokens (SKILL.md is roughly 21k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Cesiumjs Entities: Source Maps (thedaviddias/Front-End-Checklist, 74k stars), Twenty Syncable Entity Cache and Transform (twentyhq/twenty, 58k stars), Source-Driven Development (addyosmani/agent-skills, 104k stars) and Repo Mirror Sources (netdata/netdata, 81k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
CesiumGS (a GitHub organization) maintains it in CesiumGS/cesiumjs-skills, which has 189 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on September 14, 2026.
Source: CesiumGS/cesiumjs-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.