Resources and distribution
Distribution flow
Create, validate, and publish Skills, Work, and Connectors in Resource Hub; then distribute immutable published versions to roles through Explore Management. Resource content maintenance and user discoverability are separate stages.
Connect a Git repository
- Open 【System】 → 【Git repositories】 (
/admin/settings/git-repositories) and create or verify a Git Repository Connection. - Configure repository URL, default branch, authentication method, and Access Scope. A connection serves only one resource type at a time.
- Confirm that the repository structure and
.workbenchconfiguration follow the page's requirements and contain no passwords, tokens, or private keys.
Create and publish a resource
- Open 【Resources】 → 【Resource Hub】 and create a Skill, Work, or Connector. Its type is locked after creation.
- Create a named draft from Git, local upload, or a blank resource.
- Verify
SKILL.mdand type-specific structure. Work also requires at least one top-level member directory with<member>/SKILL.md. - Set the publish behavior for each file or directory: 【Read-only】/【Writable】 controls whether users can edit it; 【Overwrite】/【Keep】 controls whether updates keep user changes at the same path. Configure each file or directory separately; policies do not inherit from a parent directory.
- Save, validate, and publish an immutable version. Make changes by creating a new draft, not editing a published version.
Distribute in Explore
- Open 【Resources】 → 【Explore Management】 (
/admin/skillhub/explore) and select 【New】. - Select only an already published Resource Hub version.
- Set 【Display】 values: Icon, Name, Description, and Display Order.
- Set
Visible Roles; selecting multiple roles means any of those roles can see the resource, while an empty selection makes it visible to all roles. - Select 【Always use latest version】 or 【Use specific version】, save, and validate with both authorized and unauthorized test accounts.
Turn team experience into shared capabilities
Follow a monthly sales review from method to result: maintain the analysis method and report template, publish the Skill, and distribute it to the sales team. A colleague adds it and starts a task with sales data to receive a report with charts, conclusions, and actions. After publishing an improved version, the maintainer switches the pinned distribution version from 1.0 to 1.1.
Watch the video in Academy 2.4 Tuning Skills to see how a team uses a shared capability and receives updated versions.
Checks and exceptions
- Syncing Git or changing a published resource creates a new draft; it does not overwrite the published version in place.
- Removing an Explore release does not delete the Resource Hub resource.
Common questions
Why do users remain on an old version?
Check 【Version mode】. 【Use specific version】 keeps the selected published version until a maintainer changes it; 【Always use latest version】 switches the current distribution version when a newer version is published. The version badge in user details shows the current distribution version.
Does 【Keep】 apply to child paths automatically?
No. Configure each required file or directory directly.
Related pages
First-time setup
For first-time setup, follow these configuration guides: