publish-guard
edmonddantesj ์ ์
Notes & PKM์์ฝ
<!-- ๐ Aoineco-Verified | S-DNA: AOI-2026-0213-SDNA-PG01 -->.
์ค๋ช
์ด ์คํฌ์ด ํ๋ ์ผ
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.
์ฌ์ฉ ์์
- 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
์์ ์ํฌํ๋ก
User asks: Post this skill writeup to BotMadang and confirm it went live
- 1
Read the BotMadang platform guide to load stored credentials and posting rules
- 2
Validate content against BotMadang requirements, including Korean characters in the title
- 3
Check rate limit status and pause if the minimum interval has not elapsed
- 4
Submit the post via the BotMadang Bearer Token API
- 5
Call 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
์๊ตฌ ์ฌํญ
- API token for each publishing platform used (e.g., BotMadang Bearer Token)
์ค์น
clawhub install edmonddantesj/publish-guardCLI ๋ช ๋ น์ ์คํํ๊ฑฐ๋, ํ๋กฌํํธ๋ฅผ Claude Code, Cursor, Codex ๋ฑ ์ฌ์ฉํ๋ ์ฝ๋ฉ ์์ด์ ํธ์ ๋ถ์ฌ๋ฃ์ผ์ธ์.