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
Add OpenClaw (github.com/openclaw/openclaw) as an experimental
deployment target for skills. Once enabled via
'apm experimental enable openclaw', users can deploy SKILL.md
bundles to:
project scope: .agents/skills/<name>/SKILL.md
user scope: ~/.openclaw/skills/<name>/SKILL.md (--global)
At project scope the output is identical to agent-skills; the
--global user path (~/.openclaw/skills/) is the distinguishing
capability -- it maps to OpenClaw's priority-4 managed skill
loading directory.
Changes:
- Register ExperimentalFlag 'openclaw' in FLAGS
- Add KNOWN_TARGETS['openclaw'] TargetProfile
- Wire into EXPERIMENTAL_TARGETS, get_target_description(),
_CROSS_TARGET_MAPS, and enable-hint UX block
- Update exact-set guardian tests
- Add 25 new tests (E2E, constants, flags, profile, description,
cross-target-map)
- Update targets-matrix docs and apm-usage commands.md
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
-**Use case.** Author-time target for shipping a SKILL bundle that any Skills-aware client (Codex, Copilot CLI, Claude Code, etc.) can read without per-tool deployment.
-**Detection.** Never auto-detected. Select with `--target openclaw`
186
+
after enabling the experimental flag.
187
+
-**Enable.**`apm experimental enable openclaw`.
188
+
-**Deploy directory.**`.agents/skills/` at project scope (identical to
189
+
`agent-skills`); `~/.openclaw/skills/` at user scope (`--global`).
190
+
-**Supported primitives.** skills only.
191
+
-**File conventions.**`.agents/skills/<name>/SKILL.md` (project) or
192
+
`~/.openclaw/skills/<name>/SKILL.md` (user).
193
+
-**Note.** At project scope the output is identical to `agent-skills`.
194
+
The `--global` user path is the distinguishing capability, deploying
195
+
skills where OpenClaw reads its managed/local skill directory
196
+
(priority 4 in the OpenClaw loading order).
197
+
180
198
## Skills convergence
181
199
182
200
By default, every target with a `skills` primitive deploys to `.agents/skills/<name>/SKILL.md` rather than under the target root. This matches the cross-tool agent skills convention so a single skill bundle serves every harness.
Copy file name to clipboardExpand all lines: packages/apm-guide/.apm/skills/apm-usage/commands.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -179,6 +179,8 @@ Use `apm experimental enable copilot-cowork` to turn on Microsoft 365 Copilot Co
179
179
180
180
Use `apm experimental enable copilot-app` to turn on GitHub Copilot desktop App workflow deployment. Once enabled, prompts that carry workflow frontmatter -- any flat top-level key of `interval`, `schedule_hour`, `schedule_day` -- can be deployed to the App's SQLite store at `~/.copilot/data.db` with `apm install --target copilot-app` (project scope) or `--target copilot-app --global` (user scope). A `.prompt.md` belongs to exactly ONE surface: workflow-shape prompts go to the App DB, plain prompts go to slash-command targets. Rows always start `enabled = 0` -- you opt in from the App. `apm install / update / uninstall` preserve user state (`enabled`, `last_run_at`, schedule overrides). Override the database path with `APM_COPILOT_APP_DB=<abs-path>`. Workflows are scoped to a real Copilot App project: when the App is running APM registers the project over the App's loopback WebSocket so the project is immediately known to the webview; when the App is closed APM falls back to a direct-SQLite `BEGIN IMMEDIATE` resolver. The first install in a brand-new repo prints a one-time "restart the Copilot App once" hint (see github/github-app#5483); subsequent installs are silent. `--global` installs that carry workflow-shape prompts warn-and-proceed because workflows run with `CWD=~/.copilot` rather than a repo -- attach the row to a project from the App's Workflows tab to fix.
181
181
182
+
Use `apm experimental enable openclaw` to turn on OpenClaw agent runtime skill deployment. Once enabled, deploy skills with `apm install --target openclaw` (project scope, `.agents/skills/`) or `apm install --target openclaw --global` (user scope, `~/.openclaw/skills/`). At project scope, output is identical to `agent-skills`; the `--global` user path is the distinguishing capability.
183
+
182
184
### Cross-client skills (`agent-skills`)
183
185
184
186
Use `--target agent-skills` to deploy skills to `.agents/skills/` -- the cross-tool standard directory. This is useful when multiple clients (Codex, future tools) read from `.agents/skills/`. Unlike `--target all`, `agent-skills` must be requested explicitly: `apm install --target agent-skills` or `apm install --target all,agent-skills` for both. `apm compile --target agent-skills` is a no-op (skills-only target).
0 commit comments