Git and Pages hosting

Build from the repository

The CLI runs from the local checkout's root—the directory containing skills/ and any remote-skills.json. On your machine, that means opening a terminal in the repository. In CI, it means running the build after the checkout and dependency-install steps.

With the CLI installed in that checkout:

npm exec -- remote-skills build

build validates the skills and creates dist/. The source, lockfile, and publisher settings in Git give the pipeline the same inputs as your local build. The CLI does not clone a repository URL or accept a separate project-directory argument.

Serve the output

Your provider's deployment step uploads the contents of dist/, including .well-known. The hosting guide covers response types and preserving the built files unchanged.

Discovery expects .well-known at the hostname's root. A custom domain such as skills.example.com gives a Pages project that layout without changing the source repository.

A default project site such as https://example.github.io/repository-name/ puts the files one level deeper. It needs a custom domain or hosting configuration that serves them at the host root instead—an origin-root mapping. Adding /repository-name/ to the SDK URL does not change where it looks for the catalog.

Check the deployed result

From a machine that can reach the deployed hostname, run:

npm exec -- remote-skills verify https://skills.example.com

Once verification succeeds, the SDK can connect to https://skills.example.com. Future source changes follow the same checkout, build, and deployment process.