How to use
- Copy the installation command and review the source package before installing it in your own agent environment.
- Check the source document for required tools, credentials and supported hosts.
- Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/maplibre/navara --skill supported-maplibre-statusBefore you start
- Installation does not include a model subscription, API allowance or permission to access your files.
- Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document
Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.
Navara Feature Support Documentation Standard
Rules for documenting feature support status across all Navara documentation.
Icon Usage Rules
✅ Fully supported
- Complete implementation, no limitations
- Format:
{ "status": "✅" }
⚠️ Partial support
- REQUIRED: Must include specific issue description
- Format:
{ "status": "⚠️ [specific issue]" } - Examples:
"status": "⚠️ Evaluated once at initialization""status": "⚠️ No animation support""status": "⚠️ Performance degrades with >1000 features"
❌ Not supported
- Not implemented
- Format:
{ "status": "❌" }
JSON Structure
Basic feature:
json
{
"feature-name": { "status": "✅ | ⚠️ [issue] | ❌" }
}Hierarchical feature:
json
{
"feature-name": {
"status": "⚠️ Partial support",
"properties": {
"property-name": { "status": "✅ | ⚠️ [issue] | ❌" }
}
}
}Parent/Child Status Rules
- Parent =
⚠️ Partial supportif ANY child is ❌ or ⚠️ - Parent =
✅only if ALL children are ✅ - Parent =
❌if entire feature not implemented
Checklist
- [ ] Every ⚠️ includes specific issue description
- [ ] Parent status reflects child status
- [ ] All features use
{ "status": "..." }object format (no plain strings) - [ ] Issue descriptions are specific (< 80 chars)
Example: MapLibre Style Support
MapLibre support is documented in docs/src/content/docs/maplibre_style/supported.json following these rules. See that file for reference structure.
