Mapbox Style Quality
v1.0.0Expert guidance on validating, optimizing, and ensuring quality of Mapbox styles through validation, accessibility checks, and optimization. Use when prepari...
⭐ 0· 40·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
The name/description (Mapbox style validation, accessibility, optimization) match the SKILL.md and ancillary docs. All recommended actions (validate expressions/GeoJSON, check contrast, optimize, compare versions) are relevant to the stated purpose.
Instruction Scope
The instructions reference several helper tools (validate_geojson_tool, validate_expression_tool, check_color_contrast_tool, compare_styles_tool, optimize_style_tool) and recommend CI/pre-commit integration. The skill does not include implementations of those tools or commands, so users must provide trusted tools that perform the described checks. The instructions do not attempt to read unrelated system files, request secrets, or send data to external endpoints.
Install Mechanism
No install spec and no code files — lowest-risk, instruction-only skill. Nothing will be downloaded or written by the skill itself.
Credentials
The skill declares no required environment variables, credentials, or config paths. Its recommendations (CI hooks, npm scripts) are conventional for a developer workflow and do not demand extra secrets.
Persistence & Privilege
always is false and there is no request for permanent presence or modification of other skills/config. Autonomous invocation is allowed (platform default) but the skill itself does not elevate privileges or persist state.
Assessment
This skill is a coherent checklist and set of guidelines, not an executable package. Before relying on it: 1) confirm you have (or will install) the validation/optimization tools the instructions reference — the skill does not provide them; 2) verify those tools are from trusted sources and understand whether they transmit data (especially if validating third‑party GeoJSON) to avoid accidental exfiltration; 3) when adding pre-commit or CI hooks, review the invoked npm scripts or binaries to ensure they don't require unexpected credentials; and 4) if you integrate with Mapbox APIs or tokens in your workflow, keep those secrets confined to secure CI variables and not passed to untrusted tooling.Like a lobster shell, security has layers — review code before you run it.
latestvk977s7mwwcctpwsc3xcfm448g183zz5d
License
MIT-0
Free to use, modify, and redistribute. No attribution required.