Think of it as the “toolkit” or “runtime” for your AutoPkg environment.
Assets/ scripts/ accept_zoom_license.sh configure_outlook_profile.py icons/ company_vpn.icns tools/ jq Once built, host the package on an internal web server or a Jamf distribution point. Then, in any AutoPkg recipe that needs those assets, add: autopkg-assets.pkg
Without autopkg-assets.pkg , you’d have to fork the upstream recipe and embed your script—then rebase every time the parent recipe changes. Think of it as the “toolkit” or “runtime”