Sharing skills with every tool

Beta. In beta and free for now: versions, review, access, distribution and revoke carry no charge. Agents running a skill, and tests judged by a model, use credits like any other model call.

A skill you publish in connect0 reaches more than connect0's own agents. This page covers where a production version goes, how to add a marketplace or a registry, how to take a version back, and what connect0 can see about its use. Everything here is under Settings → Skills → Distribution.

Where a skill goes

Three places are always on. connect0 serves the production version there itself, as soon as it changes:

• connect0 agents. Every agent of the account uses it, checked against the person who started the run.
• Zero. Zero uses the account's skills that its person may use.
• The connect0 MCP server. Any MCP client signed in to connect0 lists the skills that person may use, over the MCP Skills extension (skills/list, skills/get), and each skill as a prompt.

Two more you add yourself, and a third that comes with a GitHub pack:

• Marketplaces. A private GitHub repository that connect0 keeps current. Claude Code, Cursor, Codex and GitHub Copilot install the skills from it.
• Registries. Your company's catalogues at AWS, Google and Anthropic. connect0 pushes each signed production skill there.
• The pack's own repository. A skill that came from a GitHub pack can be written back to the folder it came from, as a commit or a pull request. See Skill packs for write-back.

Add a marketplace

You need a GitHub connection on the account and a private repository it can write to.

1. Open Settings → Skills → Distribution and go to Add a marketplace.
2. Pick the GitHub connection, enter the repository as owner/name, and a branch if it is not the default one.
3. Select Add marketplace. connect0 checks that the repository is private and that the connection can write to it.

The first sync runs within two minutes. connect0 writes one plugin per group of people: one for skills everyone may use, and one per team. It commits only when something changed.

Anyone who can read the repository can read every plugin in it. Limit who can read the repository on GitHub.

Give people the plugins

The marketplace page lists the admin settings to paste into each tool: Claude Code and Claude for Enterprise, GitHub Copilot and VS Code, Cursor, and ChatGPT and Codex. The same text is ADMIN-POLICY.md in the repository. Each plugin also carries the connect0 MCP connector, so a person who signs in gets the live version too.

Add a registry

Go to Add a registry on the Distribution tab and pick one:

Registry	What connect0 creates	You need
AWS Agent Registry	A skill record per version, submitted for approval to your registry's curators or auto-approval rules	An IAM user's access key with agent-registry:ListRegistryRecords, CreateRegistryRecord, GetRegistryRecord, SubmitRegistryRecordForApproval and DeleteRegistryRecord
Google Agent Registry (preview)	A skill in your project's Agent Registry; a new version is a new default revision	A service account with the Agent Registry User role (roles/agentregistry.user), the Agent Registry API enabled, and its JSON key
Claude API skills	A custom skill in your Anthropic workspace, for the Claude API and the Agent SDK	An API key of the workspace, and the workspace ID if the key reaches several

Choose whose skills go there, everyone's or one team's. connect0 checks the credentials with the registry before saving them. They are stored encrypted and never shown again. Turn a registry off to stop syncing; copies already there stay.

Revoke a version

Open the skill, go to its Distribution panel and select Revoke. Give a reason, and choose whether to put an earlier version back in production.

• connect0 agents, Zero and the MCP server stop serving it at once.
• Marketplaces drop it on the next sync, and connect0 deletes the registry copies.
• Anything connect0 cannot remove itself is listed as a step to do by hand.

Signatures

Every production version is signed with the account's key (OpenSSF Model Signing), and only signed versions leave connect0. A version is signed within a few minutes of publishing; the skill page shows the signature. Most other tools do not check skill signatures yet.

What connect0 sees

Every use through connect0 agents, Zero and MCP prompts is recorded with its version. The skill's Usage panel shows uses per version by channel, the success rate and the feedback on the replies that used it. Copies installed from a marketplace or a registry run inside those tools, which report nothing back. The panel says so.

Where to go next

• Managing skills: review, versions and who can use a skill.
• Authoring a skill: write one.
• Skill packs: import skills from GitHub or npm.