maslibs-parameter-guide

Load specific MAS web component versions via URL parameters.

1|1|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/adobecom/mas-claude-config --skill maslibs-parameter-guide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: maslibs-parameter-guide
Source: https://github.com/adobecom/mas-claude-config/tree/main/config/skills/maslibs-parameter-guide
Command: npx skills add https://github.com/adobecom/mas-claude-config --skill maslibs-parameter-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill solves the challenge of controlling and testing the correct version of MAS (Merch at Scale) web components on any page by providing precise URL parameters.

Core Features & Use Cases

  • Parameter Control: Load different versions of MAS web components for testing.
  • Local Development: Test local changes directly with a single URL parameter.
  • Feature Branch Testing: Validate feature branches by specifying the branch name.

Quick Start

To test local changes, append '?maslibs=local' to your Adobe page URL.

Frequently Asked Questions about maslibs-parameter-guide

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

FAQPage Schema
How do I load a specific version of MAS web components for testing?

To load specific MAS web components for testing, append the appropriate URL parameter to your Adobe page address. This allows selective loading of different component versions directly in the browser.

What URL parameter do I use to test local changes for Adobe Merch at Scale?

To test local changes for Merch at Scale, append '?maslibs=local' to your Adobe page URL. This parameter forces the environment to load your local development version of the web components.

Can I validate a feature branch by specifying its name in the page URL?

Yes, you can validate feature branches by specifying the branch name within the URL parameter. This targets the custom branch deployment, allowing you to test specific features before merging.

Does this URL parameter approach work for custom branch deployments in the Adobe environment?

Yes, this approach is fully optimized for custom branch deployments within the Adobe environment. It enables precise control over which Merch at Scale branch is loaded on any page.

Why does my Adobe page load the default MAS web components instead of my feature branch?

Your page loads default MAS components because the URL parameter specifying your feature branch is missing or incorrect. You must append the exact branch name parameter to override the default deployment.