Mapbox Data Visualization Patterns
v1.0.0Patterns for visualizing data on maps including choropleth maps, heat maps, 3D visualizations, data-driven styling, and animated data. Covers layer types, co...
⭐ 0· 102·0 current·0 all-time
by@mapbox
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match the content: examples, patterns, and guidance all relate to Mapbox GL JS visualizations. There are no unrelated environment variables, binaries, or config paths requested.
Instruction Scope
SKILL.md contains many concrete code examples that fetch or reference external data URLs (https://example.com, /api/live-data, wss://api.example.com) and demonstrates client-side data updates and WebSocket polling. This is expected for a visualization patterns skill, but users should replace the placeholder endpoints and validate any real endpoints they connect to.
Install Mechanism
No install spec and no code files are executed by the platform — lowest-risk pattern. A snippet references 'npm install classybrew' for preprocessing, but that's an optional example and not an installer declared by the skill.
Credentials
Skill declares no environment variables, credentials, or config paths. The examples do not attempt to access system secrets. No disproportionate credential requests are present.
Persistence & Privilege
always is false and the skill does not request persistent system presence or modify other skills. Autonomous invocation is allowed (platform default) but the skill has no elevated privileges.
Assessment
This skill appears coherent and low-risk: it's a documentation/instruction pack for Mapbox visualizations and requires no credentials or installs. Before using: replace placeholder endpoints (example.com, api.example.com) with your own trusted data sources; do not point examples at private endpoints unless you understand the data flow and CORS implications; if you use Mapbox services you will need a Mapbox access token in your app (the skill doesn't request one) — store that token securely and avoid pasting it into untrusted places; when running examples that fetch live data or open WebSockets, verify the remote service's trustworthiness to avoid inadvertently sending sensitive data. If you want higher assurance, request the author/source and any licensing/usage terms for included patterns or assets.Like a lobster shell, security has layers — review code before you run it.
latestvk979h67ft9b28c1x23wtdn954x83w7g2
License
MIT-0
Free to use, modify, and redistribute. No attribution required.