Problem or motivation
OpenClaw users can install plugins that act through real public social accounts. Those tools need a clear Sponsio recipe for keeping endpoint discovery available while requiring operator approval before live account-scoped API calls.
Proposed solution
Add a small OpenClaw social-account actions example that uses TweetClaw as the concrete plugin path:
- keep
explore available for endpoint review and planning
- require
confirm_reconfirmed before tweetclaw executes
- cap live TweetClaw calls per session
- validate the sample config with Sponsio's config loader and CLI
Alternatives considered
The existing sponsio:incident/openclaw pack is useful background, but it is a mixed deterministic and stochastic reference pack. A deterministic example recipe is easier for default OSS users to validate and adapt before they opt into the full incident pack.
Problem or motivation
OpenClaw users can install plugins that act through real public social accounts. Those tools need a clear Sponsio recipe for keeping endpoint discovery available while requiring operator approval before live account-scoped API calls.
Proposed solution
Add a small OpenClaw social-account actions example that uses TweetClaw as the concrete plugin path:
exploreavailable for endpoint review and planningconfirm_reconfirmedbeforetweetclawexecutesAlternatives considered
The existing
sponsio:incident/openclawpack is useful background, but it is a mixed deterministic and stochastic reference pack. A deterministic example recipe is easier for default OSS users to validate and adapt before they opt into the full incident pack.