@the-open-engine-company/zeroshot 10.9.0 → 10.10.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/package.json +1 -1
- package/skills/zeroshot/SKILL.md +35 -0
package/package.json
CHANGED
package/skills/zeroshot/SKILL.md
CHANGED
|
@@ -52,6 +52,41 @@ zeroshot connection list --target cloud --scope org
|
|
|
52
52
|
Do not assume a profile creates a pull request. `--pr` requests pull-request delivery and `--ship`
|
|
53
53
|
requests merge delivery when materializing a compatible template; use either only when intended.
|
|
54
54
|
|
|
55
|
+
## Prepare the execution environment
|
|
56
|
+
|
|
57
|
+
Environments belong to a run, independently of its profile. A `local:NAME` profile can run on a
|
|
58
|
+
Docker target with its own environment. For Docker or Cloud, pass
|
|
59
|
+
`--environment environment.json` with a flat definition such as:
|
|
60
|
+
|
|
61
|
+
```json
|
|
62
|
+
{
|
|
63
|
+
"setup": "apt-get update && apt-get install -y jq",
|
|
64
|
+
"startup": "npm ci",
|
|
65
|
+
"variables": { "CI": "true" }
|
|
66
|
+
}
|
|
67
|
+
```
|
|
68
|
+
|
|
69
|
+
Cloud resolves an omitted environment from the repository's User default, then Org default, then
|
|
70
|
+
Base. `--no-environment` bypasses defaults. Choose saved environments through Cloud's UI or API;
|
|
71
|
+
the CLI accepts a concrete JSON file. Local runs use the invoking machine and reject setup/startup
|
|
72
|
+
and hook connections.
|
|
73
|
+
|
|
74
|
+
Setup runs as root before checkout or restoration, so it cannot read repository files. Startup
|
|
75
|
+
runs as the workspace user in the checkout; workers and reviewers share its dependencies and
|
|
76
|
+
services. Both hooks rerun on resume, so startup must tolerate existing workspace files.
|
|
77
|
+
Checkpoints restore files and graph progress, not running services or agent conversations.
|
|
78
|
+
|
|
79
|
+
Put shared executables in `$ZEROSHOT_TOOLS/bin` and project dependencies in the workspace.
|
|
80
|
+
Shell exports do not persist between hooks or agents; use `variables` for nonsecret values and
|
|
81
|
+
`connections` for required secret field names. Hook connections and node connections are separate.
|
|
82
|
+
On a direct Docker target, root setup changes the container shared by its runs.
|
|
83
|
+
|
|
84
|
+
Preparation failures stop before agent execution without spending repair attempts. Inspect the
|
|
85
|
+
failed phase and logs; fix the environment instead of requesting unrelated code repairs. Resume
|
|
86
|
+
reuses the accepted definition, so an edited environment requires a new run. For a pinned Node
|
|
87
|
+
installation and service/Docker conventions, see the
|
|
88
|
+
[environment guide](https://the-open-engine.github.io/zeroshot/current/guides/runtime-environments/).
|
|
89
|
+
|
|
55
90
|
## Expose a profile over ACP
|
|
56
91
|
|
|
57
92
|
Start `zeroshot acp` only when the user explicitly asks to expose a Zeroshot graph as an ACP agent.
|