Hi
There are these steps
. Install globally with npm
. Create a manifest apps script.json with the scopes you will want to use
. Next there is a choice depending on the kind of auth you want to use. Application default credentials .. adc .. or domain wide delegation .. dwd. You can use dwd if you have permission to do this using domain admin ui. This will automatically create a service account with the scopes in your manifest and will act as if it was you and tell you what to do to enable dwd in the admin console. Alternatively, Adc will also act as you, but many scopes are sensitive and need a little more google oauth credential set up in the cloud console. All this is documented on the getting started docs in the repo.
. gas-fakes init will start a dwd dialog, gas-fakes init —auth-type adc will start an adc dialog.
. Next gas-fakes auth will take you through the usual google consent screens. This will set up your local environment with a permanent auth. The login persona you choose at this point will be the one that acts on your workspace assets.
. All this is generally a one off exercise unless you need to modify the scopes you need.
So essentially, whoever you login as during the auth process is who gas fakes will pretend to be from that point on.
The agent skills are installed either manually as per the docs, or as part of the gas-fakes init process if you choose that option.