You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: apex/skills/apex-flow/SKILL.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -107,6 +107,7 @@ Options to offer via AskQuestion:
107
107
- If it exists, use `create` for a new job or `refresh-global` for an existing job; both convert the key to a fresh ticket and write it to `global.json`.
108
108
- Verify that `global.json` contains a non-empty `bohrium_config.ticket` before submission.
109
109
-`run.sh` must only install/verify APEX and call `apex submit`. Do not add ticket API calls or depend on `BOHRIUM_ACCESS_KEY` inside the APEX container.
110
+
- Install with `python3 -m pip install --upgrade --no-cache-dir apex-flow`.
110
111
See `reference/submission.md`.
111
112
7.**Project ID from environment only.**`generate_config.py` reads `BOHRIUM_PROJECT_ID` (or `--project-id`). Never hardcode a project ID (including old examples like `13529`) into `global.json`, docs, or prompts.
112
113
8.**Hard-validate inside the task directory before every upload.** Run:
│ → Waits for completion and retrieves results automatically │
@@ -69,14 +69,11 @@ the job directory is packaged:
69
69
70
70
## Outer Job run.sh Template
71
71
72
-
The outer Bohrium job always uses this pattern. **Do NOT pin apex-flow version** — this ensures the latest code (with bug fixes) is used and propagated to inner steps via `upload_packages`.
73
-
74
72
```bash
75
73
#!/bin/bash
76
74
set -eo pipefail
77
75
78
-
# Always install latest apex-flow (DO NOT pin version)
0 commit comments