Share Agent Skills

Publish an admitted Skill to a named Agent in the same security domain

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. By default, publication requires a member review. An authorized member can enable automatic publication for one source Agent, one destination Agent, and named task families.

Configure automatic publication

Send a member bearer token to the web policy endpoint. A project API key cannot configure this policy or request publication.

curl -X PUT "$ZEP_BASE_URL/api/web/v1/agents/$SOURCE_AGENT_UUID/skill-publication-policy" \
  -H "Authorization: Bearer $ZEP_MEMBER_TOKEN" \
  -H "Content-Type: application/json" \
  -d "{\"destination_agent_uuid\":\"$DESTINATION_AGENT_UUID\",\"mode\":\"auto\",\"task_families\":[\"tool.airline\"],\"expected_revision\":0}"

The Agents must be active, belong to the same project, and have the same nonempty security domain. The policy response includes its revision. Set expected_revision to that value when you change the policy. Set mode to manual to stop future automatic publications. Existing destination copies remain subject to their admission and retention rules.

The server publishes an eligible, admitted source version without a separate publication request. The server scans the portable copy and creates a destination candidate. The copy has no source evidence or citations and does not inherit the source’s verification strength.

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 new source version creates a new candidate rather than replacing 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.