package-pack
Load when a working app should become a pack, or when installing or changing a pack. Export, check, install, versions.
- License 许可
- Apache-2.0
- 所属仓库
- gents-ai/gents
- 最近更新
- 2026-11-15
- Stars
- ★ 24
- Forks
- 4
01 前言 Front Matter
- name
- package-pack
- description
- Load when a working app should become a pack, or when installing or changing a pack. Export, check, install, versions.
03 SKILL.md 正文
Package a pack
A pack carries an app to another node, or back to this one, in one install. Make it from what already works.
Export what you built
- Clean up first: remove documents, pages, plugins and collections you tried and dropped (
config help cleanup,schemahelpcollections). What is live is what ships. - Run
pack export NAME(config help pack). Select the app's documents by ID, tag or collection. The export follows references, so naming the triggers and the page usually brings the rest. Tagging the app's documents as you build makes this one option. - Read the receipt. It lists what was written and anything it could not carry. Agents become inference slots the installer binds.
pack check, thenpack build. Fix every finding.- Prove it: preview the install and read what it would create. If you can, install it where the app does not already exist and run the app once.
Use a pack
pack search and pack get show what a pack holds before you install it. pack preview install lists what it creates and what its plugins ask for. Install binds inference slots as --inference-slot NAME=PROFILE_ID. You can install any pack yourself.
Installing a plugin does not select it. Add it to the Tools of each agent that needs it, then use a fresh request: changes apply to later requests only.
Change a pack
Change the live documents, test, and export again with a higher version. For a pack kept as a directory, edit the source, check, build and reinstall. Don't edit the installed copy.
Directory layout
| Part | Location | Declared under |
|---|---|---|
| Collections | schemas/*.graphql |
assets |
| Agents, tools, surfaces, tasks, triggers | pack_config.json |
config |
| Prompts | Markdown that pack_config.json names |
assets |
| Page | ux/<name>/plugin.js and plugin.css |
ux and assets |
| Compiled code | plugins/ |
plugins and assets |
Only files the manifest declares travel with the pack. A page's surfaces and tools are listed under ux[].data, and a plugin's collections are declared in the pack's schemas.
04 同仓库更多 Skills
write_plugin
暂无简介
use-database
Load before designing an app's data. What DefraDB does for you, and how to shape collections.
plan-work
Load first when asked to build or automate an app for people. Sets the checks and build order.
diagnose-node
Load when a trigger, tool, request or session didn't work as expected. Gives the order of checks.
design_page
暂无简介
delegate-work
Load before a long build, or when parts of a job can run on their own. When and how to use helpers.