3.13 Share and receive resources

A share distributes reusable definitions and methods. It does not transfer employee accounts, model keys, conversation history or execution grants. Materials and file bodies may contain content you supplied: inspect them and their licenses before publication. Automated checks do not replace that review.

Where to start

Resource	Sharing entrypoint	Receiver checks
AI employee	Share action in the employee profile	One employee, five responsibility arrays, included methods and materials
AI team	Share action on a group/team; choose participating employees	At least two employees, coordinator and relationships
App	App sharing in My apps and skills	Fixed skills/connections/extensions and setup requirements
SKILL	Share action in skill details	One method, content, version, source and license

An app containing one skill retains its app subject. A tool connection may be shared separately as MCP; it remains an app capability, not a fifth primary marketplace category. See resource formats.

Offline sharing

1. Open Share on the relevant object. Review title, publisher, fixed version, license, sources and contents. Select only material you can redistribute and remove private content. Connection prompts must contain no actual secret or credential-bearing address.
2. Expand the complete file preview, check responsibilities and dependencies, and choose Export offline template. The resulting JSON contains the receivable definitions; screenshots do not replace it.
3. In Employees, choose Import template in the upper-right toolbar (the download-arrow icon), then select the JSON in the receiving drawer. This drawer also accepts apps and SKILLs. It differs from the employee/team import flow under Marketplace's Create menu.
4. Inspect composition and file content, select the business and skills, then explicitly add. Employees start paused. Review item results and separately configure models, installation, accounts, grants or group formation. After interruption or failure, continue the original receipt instead of repeatedly creating copies.

The employee, team, app and SKILL examples contain extracted JSON and editable source files. They include no accounts or external execution.

Online sharing

1. Choose Publish share link from the same preview. The browser opens the Teloa marketplace account page for the sharer's own login.
2. Recheck the complete public files, sources and license on the website, then explicitly publish. Cancelling does not publish. Return to the original workbench, verify state and copy the actual generated link.
3. Receivers open the official link to preview it, then follow the page into their own Teloa or paste the link into the receiving drawer. They explicitly add their own copy and configure their own accounts and grants. The sharer's connected sessions are not inherited.
4. The sharer can Revoke link from the original share record. This stops future receipt through the link, not use of already downloaded files or installed copies. Changes to your original employee do not silently update those copies.

Online links are for public distribution, not private group invitations or permission grants. Keep private material local. If the service is unavailable, export a file. For an uncertain response, check the original record before publishing again. Complete account login and public-content confirmation through the website; do not send login secrets in chat.

Versions, licenses and formats

Current shares use teloa.template-share/v2 with employee, team, app or skill subjects. Existing v1 links retain their original reader; changing the version field is not a migration. The inner manifest uses teloa.business-package/v2, v3 or v4, with matching identity/version. Serialized share JSON is limited to 8 MiB, and each UTF-8 file body to 2 MiB. This differs from the 20 MiB business-resource import total.

Publish a new fixed version when content changes. Preserve source authorship, licenses and modification records. Public readability does not establish redistribution rights; a publisher label is not official verification. Exclude owner IDs, runtime state, credentials and instance permissions. Portable employee bodies in shares do not carry runtimeConfig.

Share links and official catalog submission

Publishing a link does not list a resource in the official catalog. After publication, expand Submit for official review in the original share drawer, confirm your redistribution rights, optionally add notes, then submit. While review is pending, Withdraw submission leaves the share link available; Revoke link is a separate action. Check the actual review status and comments; submission is not a listing.

If the service offers no submission option, or you contribute directly through GitHub, follow the submission rules for catalog metadata, pinned sources, licensing, validation and compatibility evidence, then PR review and index publication. See development guides for employees, teams, apps and SKILLs.