Skip to content

AI Skills CLI

The Jarvis Registry CLI is the secure delivery layer from private Registry skills to local Claude Code, Codex, and GitHub Copilot environments. It lets developers consume organization-approved skills without manually copying content or handling Registry credentials in scripts.

The Skill Gateway is where skills are authored, imported, governed, and shared. The CLI is where an authenticated developer reconciles the skills they can access into a local integration.

For installation, platform requirements, configuration, command reference, and troubleshooting, see the Jarvis Registry CLI repository.

Shared Workflow

Every integration follows the same three steps:

jarvis-registry configure
jarvis-registry auth login
jarvis-registry skills sync --mode <claude|codex|copilot>

The CLI stores credentials in the operating system keyring, authenticates against the Registry, and syncs only the skills available to the signed-in user.

Supported Integrations

Skills can be synchronized for personal use across projects or for a specific project. The CLI handles the integration-specific local layout and invocation conventions for each supported tool.

Governed Delivery

Sync is access-aware and repeatable: the CLI delivers newly accessible skills, updates changed content, and reconciles managed skills when access changes. This gives developers a consistent local experience while the Registry remains the source of truth for approved content.

The CLI also protects local content from unintended collisions and supports repeatable execution, including scheduled sync workflows. See the CLI getting started guide for integration-specific behavior.

Learn More

Next Steps

  • Skill Gateway - author, import, govern, and share the skills delivered by the CLI