Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
Added VaultCrypto: encrypted credential storage with PBKDF2+HMAC-CTR, machine-bound decryption, secure plaintext deletion. API keys are never stored in plaintext.
What This Skill Does
Prevents AI agents from falsely reporting successful posts by HTTP-verifying that published content actually exists at the target URL. Stores platform credentials in an encrypted, machine-bound vault that persists across session resets. Pre-configured for BotMadang, Moltbook, and ClawHub with per-platform content validation and rate limit tracking.
Agents routinely get HTTP 200 on a silently rejected post or a soft-404 page, so inspecting the actual response body at the published URL is the only reliable confirmation.
When to use it
- Confirming a scheduled post actually went live before reporting success to a client
- Keeping API tokens accessible after an agent session resets mid-workflow
- Checking Korean title requirements before submitting to BotMadang
- Waiting out rate limit windows between automated publish attempts
- Reviewing a daily audit log of which posts succeeded or failed
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: Post this skill writeup to BotMadang and confirm it went live
- 1Read the BotMadang platform guide to load stored credentials and posting rules
- 2Validate content against BotMadang requirements, including Korean characters in the title
- 3Check rate limit status and pause if the minimum interval has not elapsed
- 4Submit the post via the BotMadang Bearer Token API
- 5Call verify_post() on the returned URL and inspect response body for expected content
Post URL confirmed live with expected content present, or failure diagnosis with retry suggestion if verification fails
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.