OrgX Power (OpenClaw)

Use this skill only when the caller explicitly needs the full mutation surface exposed by the OrgX OpenClaw plugin. This is the elevated counterpart to the default-safe orgx skill.

Use orgx by default. Use orgx-power when you need admin or orchestration operations that change entity state directly.

When to use this skill

• - creating or updating OrgX entities directly
• reassigning streams or changing execution ownership
• pausing, resuming, cancelling, or rolling back runs
• listing or restoring checkpoints
• inspecting or updating managed agent config policy
• working against the unscoped /orgx/mcp endpoint rather than a domain-scoped safe surface

Elevated tool surface

These tools are part of the plugin registry, but are elevated and should be used intentionally:

• - INLINECODE4
• INLINECODE5
• INLINECODE6
• INLINECODE7
• INLINECODE8
• INLINECODE9
• INLINECODE10
• INLINECODE11
• INLINECODE12
• INLINECODE13
• INLINECODE14
• INLINECODE15
• INLINECODE16
• INLINECODE17
• INLINECODE18

The default-safe reporting tools still apply and should usually wrap elevated work:

• - INLINECODE19
• INLINECODE20
• INLINECODE21
• INLINECODE22
• INLINECODE23
• INLINECODE24

Operating discipline

1. 1. Announce intent with orgx_emit_activity before making mutations.
2. Prefer orgx_request_decision before irreversible or org-wide changes.
3. Use orgx_apply_changeset when you need idempotent batched state updates.
4. Register artifacts for anything another operator would need to inspect later.
5. Verify completion and proof state after major mutations.

Examples

Batched entity mutation

CODEBLOCK0

Reassign a stream

CODEBLOCK1

Run control

CODEBLOCK2

Safety note

This skill assumes the runtime actually exposes the elevated tools. In the managed OrgX agent suite, many domain-scoped surfaces intentionally hide them. If a tool is unavailable, fall back to the safe orgx skill and request the necessary human decision or orchestration context.