NEVER do this:

Secure verification method:

test -n "$MASTERGO_TOKEN" && echo "Token is set" || echo "Token is NOT set"

This only prints whether the token exists, never its value.

Script Location

Scripts are in scripts/ relative to this SKILL.md file. Use absolute path when executing:

{this_skill_directory}/scripts/mastergo_*.py

Workflow

Always analyze first to understand the page structure:

python scripts/mastergo_analyze.py "https://mastergo.com/goto/xxx"

Output shows:

For detailed DSL data:

python scripts/mastergo_get_dsl.py "https://mastergo.com/goto/xxx"

Output: JSON with { dsl, componentDocumentLinks, rules }

If componentDocumentLinks is non-empty, fetch relevant docs:

python scripts/mastergo_get_dsl.py URL | python scripts/mastergo_fetch_docs.py --from-dsl

Or fetch individually:

python scripts/mastergo_fetch_docs.py "https://example.com/button.mdx"

Script	Purpose	Output
`mastergo_analyze.py`	Structure summary	Human-readable tree to stdout
`mastergo_get_dsl.py`	Full DSL data	JSON to stdout
`mastergo_fetch_docs.py`	Component docs	Doc content to stdout
`mastergo_utils.py`	Utility functions	Import as module

token fields: Design tokens for colors, shadows, fonts (convert to CSS variables when generating code)
componentInfo: Component metadata including documentation links
interactive fields: User interactions including page navigation targets
rules array: Guidelines returned with DSL response

FORBIDDEN actions:

ALLOWED:

All script output goes to stdout only. Use the output directly; do not save intermediate files to user's project.