DataMaker Hub
Install and share reusable packs with a reviewable import diff.
Open Hub to browse the configured catalogue, import a .dmpack.json file, or inspect installed packs. A pack can contain templates, skills, plans, custom data types, value libraries and scenarios.
Install a pack
- Select a catalogue item or import a pack file.
- Review the publisher, version, signature status, requirements and included assets.
- Inspect the proposed changes before confirming installation.
- Open the imported assets, bind them to your project's systems and review their configuration.
Imports create or skip assets; they do not overwrite existing content. A skipped asset with different content is a conflict to resolve, not evidence that the existing asset was upgraded. Review update diffs just as carefully as first installs.
Trust and activation
Catalogue installs require a valid signature from a trusted key. File imports can be unsigned, with that state shown to you, but an invalid signature is rejected.
Imported scenarios start as drafts and skills start disabled. Installing a pack does not authorize execution. Review code and instructions, configure required connections or variables, and enable or run the assets deliberately.
Share your own pack
Use the pack creation/export flow to select reusable assets and provide package metadata. The portable format excludes environment-specific bindings and credentials. Still inspect authored text and code before sharing: a credential hard-coded into a script or instruction remains content you must remove.
The catalogue can be disabled on an installation. File import/export can still be useful where permitted. Ask the deployment administrator about catalogue configuration and use workspace permissions to control pack changes.