How Claude knows what to do

Claude needs the remote Sprig MCP connection and four workflow skills. The MCP tools enforce identity and authorization. Skills tell Claude how to combine those tools into complete builder and operator workflows.

Skill	Install for	Purpose
sprig-data	Builders	Discover exposed data, ask for an app’s access to a source, and build apps that query it at view time
sprig-publish	Builders	Package, upload, publish, resume, and share apps
sprig-ops	Operators	Expose sources, onboard builders, approve sharing, decide what an app may read, and check the platform
sprig-diagnostics	Builders and operators	Compare the installed skill version with the connected Sprig release

Download from your Sprig installation

An authorized Sprig operator opens Admin > Setup > Skills. Download all four ZIP files shown there. The archives are built into that Sprig installation and stamped with its installed release version. They are not downloaded from GitHub.

Each ZIP contains exactly one top-level skill folder and one SKILL.md. Keep the files separate. Claude rejects a combined ZIP containing several skill folders or several SKILL.md files.

Upload to Claude

A Claude tenant administrator opens Organization settings > Skills and uploads each ZIP as a separate organization skill. Organization skills are tenant-wide. Sprig authorization still decides what each person can do, so uploading sprig-ops does not grant the Ops role.

On every Sprig upgrade, return to Admin > Setup > Skills, download all four archives again, and replace the existing organization skills with those copies. Do not mix files downloaded from different Sprig installations or releases.

The MCP connector is configured separately because the skill ZIPs contain no credentials. Claude Code users also connect the gateway as an MCP server:

claude mcp add --transport http sprig https://gateway.<apps-domain>/mcp \
  --client-id <cli-client-id> --callback-port 8899
claude mcp login sprig

<cli-client-id> is the public sprig-cli client id from the install descriptor.

Check compatibility

Ask Claude: Check my Sprig skill version. The sprig-diagnostics skill calls whoami, reads its own bundled release metadata, and reports one status:

• compatible: the platform and diagnostic skill versions are valid SemVer and equal;
• incompatible: both are valid but differ, so replace all four skills from the connected installation;
• indeterminate: a version is absent or invalid, or the MCP call failed.

The diagnostic can verify its own version only. Claude does not expose the installed versions of other organization skills, so an administrator should replace all four archives together.