validate-third-party

Audit third-party integrations for async loading and consent gating.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/aramark-destinations/aramark-mb --skill validate-third-party
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate-third-party
Source: https://github.com/aramark-destinations/aramark-mb/tree/main/.agents/skills/eds/validate-third-party
Command: npx skills add https://github.com/aramark-destinations/aramark-mb --skill validate-third-party

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This checklist helps engineering and product teams ensure third-party integrations load asynchronously, respect user consent, and do not degrade site performance.

Core Features & Use Cases

  • Async loading validation: scripts load with defer/async and are not render-blocking.
  • Consent gating: all tracking/analytics wait for OneTrust approval before firing.
  • Environment configuration: separate credentials and IDs per dev/stage/prod with automatic detection.
  • Use Case: audit a new Google Maps integration to verify environment separation and consent gating.

Quick Start

Audit your page to verify async loading, consent gating, environment separation, and performance.

Frequently Asked Questions about validate-third-party

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit third-party integrations for render-blocking scripts?

Audit third-party integrations by verifying that scripts load with defer or async attributes and do not block page rendering. This ensures integrations like Google Maps and chatbots maintain optimal site performance and Lighthouse scores.

Why does my analytics tracking fire before user consent is given?

Analytics tracking fires before consent if integrations are not properly gated. You must enforce consent gating so all tracking and analytics scripts wait for OneTrust approval before executing on the page.

How to check environment-specific configuration for third-party integrations?

Check environment-specific configuration by verifying separate credentials and IDs exist for development, staging, and production. The audit validates automatic environment detection to ensure third-party integrations use the correct configuration per environment.

Does this audit support integrations like HotJar, YouTube, and Elastic Search?

The audit supports integrations including HotJar, YouTube, Elastic Search, OneTrust, Fleeknote, Emplifi, Google Maps, and chatbots. It validates async loading, consent gating, and performance impact across these specific third-party integrations.

What is the best way to maintain Lighthouse scores when adding chatbots and tracking scripts?

Maintain Lighthouse scores by ensuring third-party scripts load asynchronously, respect user consent gating, and use environment-specific configurations. Auditing these factors prevents third-party integrations from degrading site performance.

Can I use this audit to verify OneTrust consent gating for Google Maps integrations?

You can use the audit to verify Google Maps integrations by checking environment separation and confirming consent gating. It ensures Google Maps waits for OneTrust approval before loading and uses the correct environment credentials.