skilld
All skills
mapbox avatar

/mapbox-style-quality

@65bab68 official
by mapboxmapbox/mapbox-agent-skills80 stars
17

Expert guidance on validating, optimizing, and ensuring quality of Mapbox styles through validation, accessibility checks, and optimization. Use when preparing styles for production, debugging issues, or ensuring map quality standards.

Ask your Agent

Use this Skill: https://skilld.dev/gh/mapbox/mapbox-agent-skills/mapbox-style-quality

This session only. Nothing lands on disk.

referencescomparison.md

≈341 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Style Comparison Workflow

When to Compare Styles

Before merging changes:

  • Review what changed in your feature branch
  • Ensure no unintended modifications
  • Generate change summary for PR description

When investigating issues:

  • Compare working version vs. broken version
  • Identify what changed between versions
  • Narrow down root cause of problems

During migrations:

  • Compare old format vs. new format
  • Verify data integrity after conversion
  • Document transformation differences

Comparison Best Practices

Use ignoreMetadata flag:

// Ignore metadata differences (id, owner, created, modified)
compare_styles_tool({
  styleA: oldStyle,
  styleB: newStyle,
  ignoreMetadata: true
})

Focus on meaningful changes:

  • Layer additions/removals
  • Source changes
  • Expression modifications
  • Paint/layout property updates

Document significant changes:

  • Note breaking changes in documentation
  • Update style version numbers
  • Communicate changes to team/users

Refactoring Workflow

1. Create backup of current style
2. Make refactoring changes
3. Compare before vs. after
4. Validate all modified expressions
5. Optimize to clean up
6. Review size impact

Best Practices Summary

Before Committing:

  • Compare with previous version
  • Document significant changes
  • Validate modified expressions

Source: SKILL.md on GitHub

Third-party checks

1 warning16d5 checks · Risk SAFE
  • Gen Agent Trust Hub16d

    The skill provides guidance, documentation, and best practices for validating and optimizing Mapbox styles. No security issues or malicious patterns were found.

  • Socket16d

    No alerts

  • Snyk16d

    Risk: LOW · No issues

  • Runlayer7mo

    2/2 files flagged

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Provenance

Signed by skilld at 65bab68. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 5 hours ago.

Activeupdated 6 months ago

Topics

  • mapbox
  • style-validation
  • accessibility
  • wcag
  • geojson
  • expressions
  • optimization
  • color-contrast

README badge

README badge for mapbox/mapbox-agent-skills/mapbox-style-quality

What it does

Validates Mapbox styles for syntax errors, accessibility compliance, and performance issues using GeoJSON validation, expression checking, color contrast analysis, and optimization tools. Targets pre-production workflows, debugging map quality problems, and ensuring WCAG text contrast standards before deployment.

Generated from the current SKILL.md.

Frequently asked

What does this skill validate?
It validates Mapbox style expressions, GeoJSON sources, color contrast for text layers (WCAG compliance), and provides tools to compare style versions and optimize file size.
Does this work with all Mapbox GL JS versions?
The skill validates expressions against operator availability, but you should verify your specific Mapbox GL JS version when validating—the validation will catch version-specific operator issues.
What accessibility standards does it check?
It checks color contrast for WCAG AA (4.5:1 for normal text, 3:1 for large text) and AAA (7:1 for normal text, 4.5:1 for large text) standards.
Can this fix GeoJSON errors automatically?
No. The skill validates GeoJSON and reports errors (invalid coordinates, unclosed rings, wrong order), but you must fix them manually before re-validation.
Does this integrate with CI/CD?
The skill references CI/CD integration patterns in `references/ci-integration.md`, including pre-commit hooks and pipeline steps, but does not bundle CI configuration itself.

Generated from the current SKILL.md. These answers refresh after source changes.