Cesium context7
Skill CesiumGS/cesium-ai-integrations/.github/skills/cesium-context7
Cesium AI Integrations is a collection of reference integrations and experiments connecting the Cesium ecosystem with AI systems including Model Context Protocol (MCP) tools, retrieval pipelines, and agent skills.
npx -y skills add CesiumGS/cesium-ai-integrations --skill cesium-context7Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Fetches up-to-date documentation for Cesium, CesiumJS, Cesium Viewer, 3D Tiles, Unreal Engine integration, Unity integration, cesium-unreal, cesium-unity, ACesium3DTileset, ACesiumGeoreference, Globe Anchor, Cesium plugin, georeferencing, and Cesium-related APIs using Context7 MCP tools. Useful for CesiumJS classes (Viewer, Entity, Camera, Scene, Cartesian3, etc.), Unreal Engine Cesium components, Unity Cesium components, 3D Tiles specification, and Cesium integrations. Use query-docs with library IDs: /cesiumgs/cesium (CesiumJS), /cesiumgs/cesium-unreal (Unreal), /cesiumgs/cesium-unity (Unity), /websites/ogc_cs_22-025r4 (3D Tiles spec).
SKILL.md
3.3 KB, as published. Nobody here has run it
Context7 for Cesium Development
This skill provides access to up-to-date Cesium documentation for CesiumJS, Unreal Engine integration, and Unity integration.
When working with Cesium-related code, use Context7 MCP Server tools to fetch current documentation before providing answers or generating code.
Available Tools
1. resolve-library-id
Search for libraries and retrieve their Context7 library IDs.
⚠️ Only use this tool when it's unclear which library to use. For Cesium projects, use the Known Library IDs listed below.
Parameters:
libraryName(string, required): Name of the library to searchquery(string, optional): Additional search context
Example use case: Find the correct library ID for an unfamiliar library or when the library ID is unknown.
2. query-docs
Retrieve documentation for a specific library and query.
Parameters:
libraryId(string, required): Context7 library IDquery(string, required): Documentation query or topicversion(string, optional): Specific library version
Example use case: Get documentation for Cesium Viewer initialization using library /cesiumgs/cesium.
Known Library IDs
CesiumJS API Documentation
For class constructors, methods, and properties (e.g., Viewer, Entity, Cartesian3, Camera methods, Scene properties):
- Library ID:
/cesiumgs/cesium
Cesium for Unreal Engine
For Unreal Engine integration (e.g., ACesium3DTileset, ACesiumGeoreference, Blueprint integration):
- Library ID:
/cesiumgs/cesium-unreal
Cesium for Unity
For Unity integration (e.g., Cesium3DTileset component, CesiumCameraController, C# scripting):
- Library ID:
/cesiumgs/cesium-unity
3D Tiles Specification
For tile formats and schema details (e.g., tileset JSON structure, refinement strategies, metadata schemas):
- Library ID:
/websites/ogc_cs_22-025r4
Usage Guidelines
- Use the Known Library IDs listed above for Cesium-related queries
- When a question requires information from multiple sources (e.g., CesiumJS API + 3D Tiles spec, or Unreal integration + CesiumJS concepts), make separate
query-docscalls with different library IDs to gather comprehensive documentation - Use
resolve-library-idwhen the library is unknown, not listed in Known Library IDs, or when it's unclear which library best fits the question - Use
query-docsto fetch documentation before generating code to ensure accuracy - Specify the
versionparameter when working with a specific version - Provide clear, specific queries to get the most relevant documentation
- Avoid hallucinations by using current, version-specific documentation