> This page is for version v4 (default).
> For other versions, use one of these documentation indexes:
> - v4 (default): https://docs-beta.getzep.com/v4/llms.txt
> - v3: https://docs-beta.getzep.com/v3/llms.txt
> - v2: https://docs-beta.getzep.com/v2/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs-beta.getzep.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs-beta.getzep.com/_mcp/server.

# Share Agent Skills

Admission and publication control different steps. Admission makes a Skill available to its source Agent. Publication creates a separate candidate for a destination Agent. The destination can inspect the candidate for an audit, but it cannot find or use the Skill in search until it admits the candidate.

Agents in the same security domain do not automatically see each other's Skills. A member publishes a Skill version from the Zep Dashboard.

## Publish a Skill version

The source Agent and the destination Agent must be active, belong to the same project, and have the same nonempty security domain. A project API key cannot request publication.

To publish a Skill version in the Zep Dashboard:

1. Open the source Agent.
2. Select **Skills**, then open the Skill.
3. Select **Publish version**.
4. Select the **Destination Agent**.
5. Upload the **Transformed portable archive**. This is a `.zip` export of the Skill that contains no source evidence or restricted content.
6. Select the **Retention mode**: **Source linked** or **Independent**.
7. Enter the **Review rationale**.
8. Confirm the declassification review, then select **Publish reviewed version**.

Publication creates a candidate in the destination Agent. Publication does not activate the Skill. The copy has no source evidence or citations, and it does not inherit the verification strength of the source.

## Verify and admit a destination copy

Use `agent.skill.publication.lookup` with the source Agent UUID, Skill UUID, and version number to find the destination Skill. Read the destination version and run the task-answer and identifier audits before admission. After admission, use `agent.skill.publication.get` to confirm the lineage and `agent.skill.list` to confirm retrieval. The lineage endpoints return 404 when a publication is invalidated.

Run the destination admission procedure before you expect the copy in search results. Confirm that the destination Skill is active and searchable. Each publication of a new source version creates a new candidate. It does not replace an admitted destination copy.

The public export API remains available for generated Skills. Export creates a portable artifact; it does not publish a Skill to another Agent.