Skip to content

Dual-skill pattern: native-tool docs for OpenClaw plugin, CLI for standalone, bump to 0.10.1#4

Merged
pallaoro merged 1 commit into
mainfrom
dual-skill-pattern
May 19, 2026
Merged

Dual-skill pattern: native-tool docs for OpenClaw plugin, CLI for standalone, bump to 0.10.1#4
pallaoro merged 1 commit into
mainfrom
dual-skill-pattern

Conversation

@pallaoro
Copy link
Copy Markdown
Owner

v0.10.0 shipped 16 native tools but the published SKILL.md still only documented the CLI — so agents installed via `openclaw plugins install rulespec` reached for `npx rulespec` and shelled out, ignoring the native tools entirely.

Fix

Two SKILL.md variants, each authoritative for its install context:

  • `skills/rulespec-plugin/SKILL.md` (NEW) — documents the 16 native tools, workflow example using tool calls, `rulespec_emit` approval-gate config. The OpenClaw plugin manifest now points at this variant, so `openclaw plugins install rulespec` publishes the native-tool-aware doc.
  • `skills/rulespec/SKILL.md` (existing, lightly amended) — stays the CLI-focused doc for standalone consumers (Claude Code, Cursor, Codex, etc. via `rulespec init -a `) and ClawHub if/when published. Top-of-file note points OpenClaw users at the plugin variant.

Both directories ship in the npm tarball (no change to `files`); the plugin manifest just selects which one OpenClaw publishes on install.

What didn't change

  • Same 16 tools register
  • Same plugin behavior, same approval gate, same compat range
  • Standalone CLI unchanged

Test plan

  • `npm run build` clean
  • Tool registration smoke test: `default.register(fakeApi)` still registers 16 tools
  • `npm pack --dry-run` shows both skill files in the tarball
  • After publish: `openclaw plugins install rulespec` re-publishes plugin SKILL.md to `~/.openclaw/plugin-skills/rulespec/` with native-tool content
  • Agent on a freshly-updated VPS picks the native tools instead of shelling out

…ndalone, bump to 0.10.1

When the plugin landed at v0.10.0 with 16 native tools, the published
SKILL.md still documented only the CLI — so agents installed via
`openclaw plugins install rulespec` happily reached for `npx rulespec`
and shelled out, ignoring the native tools entirely.

Split into two SKILL.md variants, each authoritative for its install
context:

- `skills/rulespec-plugin/SKILL.md` (NEW)
  - Documents the 16 native tools in a per-category table
  - Workflow example using native tool calls
  - Notes the `rulespec_emit` approval gate + `skipSessionPatterns`
    bypass config
  - This is the variant the plugin manifest points at — gets
    published to `~/.openclaw/plugin-skills/rulespec/SKILL.md` on
    `openclaw plugins install rulespec`

- `skills/rulespec/SKILL.md` (existing, lightly amended)
  - Stays the CLI-focused doc that ships in the npm tarball
  - Used by standalone consumers (Claude Code, Cursor, Codex, etc.
    via `rulespec init -a <agent>`) and ClawHub if/when published
  - Top-of-file note now points OpenClaw users at the plugin variant
    so they don't follow the CLI advice when native tools are
    available

`openclaw.plugin.json` `skills` field updated to
`./skills/rulespec-plugin`. Both directories ship in the npm tarball
(`files: ["dist", "skills/**/*"]`).

No code changes — same 16 tools register, same plugin behavior. Patch
version bump since this only affects which SKILL.md the plugin
publishes.
@pallaoro pallaoro merged commit ff4be48 into main May 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant