git:20260616.89bb8fe to git:20260616.69dd3b5
73 added, 20 removed. Audit A to A.
---
name: clawhub-content-rights-correspondence
description: Use when drafting, sending, or preserving email correspondence for an existing ClawHub content rights case.
---
# ClawHub Content Rights Correspondence
- Use the bundled script for every existing-case email. It fetches the requester
- from Hermit, uses ClawHub's guarded generic email command, and records the exact
- sent correspondence back through Hermit.
+ Use ClawHub's authenticated admin CLI commands directly. Do not use helper
+ scripts, direct Hermit calls, or direct R2 access for correspondence.
## Safety Rules
- Require an existing `CHR-...` case. Never create cases with this skill.
- Dry-run first and show the final recipient, subject, and body.
- Send only after explicit user signoff on that final draft.
- - Never call Hermit or access R2 directly. Use authenticated `clawhub-admin`;
- ClawHub proxies approved case operations to Hermit.
+ - Use `bun run admin -- email send` for outbound email.
+ - Use `bun run admin -- content-rights record-correspondence` to preserve the
+ exact correspondence in Hermit.
- Do not retry after an email was sent if evidence recording fails; report the
failure so staff can repair the audit record without sending a duplicate.
- `--attachment` files are archived with the correspondence. The generic email
template does not send file attachments.
+ - The generic email template already adds the greeting. Do not add `Hello ...`
+ or `Hi ...` to the body file.
+ - The generic email template may render the subject as a visible heading. Do
+ not pass `--title`, and do not duplicate the title in the body file.
+ - Do not use the generic email action button for ClawHub content-rights
+ responses. Put the response form URL as plaintext in the body.
- ## Workflow
+ ## Publisher Removal Notice
- 1. Write the exact email body to a local text file.
- 2. Preview:
+ Use this subject:
+ ```text
+ ClawHub skill removal notice
+ ```
+
+ Use this body, replacing only the skill URL:
+
+ ```text
+ We removed the following ClawHub skill after receiving a content rights request involving Rednote/Xiaohongshu platform rights:
+
+ https://clawhub.ai/<owner>/<slug>
+
+ If you believe this removal was made in error, please submit a response using this form:
+ https://forms.openclaw.ai/clawhub-content-rights
+ ```
+
+ Preview the email:
+
```bash
- bun .agents/skills/clawhub-content-rights-correspondence/scripts/send-correspondence.ts \
- CHR-000007 --subject "Re: CHR-000007" --body-file /tmp/body.txt
+ bun run admin -- email send \
+ --user <publisher-handle> \
+ --subject "ClawHub skill removal notice" \
+ --body-file /tmp/body.txt
```
- 3. Show the preview and obtain explicit user signoff.
- 4. Send and preserve:
+ Send only after explicit signoff:
```bash
- bun .agents/skills/clawhub-content-rights-correspondence/scripts/send-correspondence.ts \
- CHR-000007 --subject "Re: CHR-000007" --body-file /tmp/body.txt \
- --attachment /tmp/evidence.pdf --send --confirm-user-signoff
+ bun run admin -- email send \
+ --user <publisher-handle> \
+ --subject "ClawHub skill removal notice" \
+ --body-file /tmp/body.txt \
+ --send \
+ --confirm-user-request \
+ --confirm-user-signoff \
+ --json
```
- For inbound correspondence that has already been received, append it without
- sending:
+ Record the exact sent correspondence:
```bash
bun run admin -- content-rights record-correspondence CHR-000007 \
- --direction inbound --to "ClawHub <noreply@notifications.openclaw.ai>" \
- --from "Requester <legal@example.com>" --subject "Re: CHR-000007" \
- --body-file /tmp/inbound.txt --attachment /tmp/evidence.pdf
+ --direction outbound \
+ --to "<publisher-handle-or-email>" \
+ --from "ClawHub <noreply@notifications.openclaw.ai>" \
+ --subject "ClawHub skill removal notice" \
+ --body-file /tmp/body.txt \
+ --provider-message-id "<providerId-from-send-response>" \
+ --json
+ ```
+
+ ## Existing-Case Replies
+
+ ```bash
+ bun run admin -- email send \
+ --to requester@example.com \
+ --subject "Re: CHR-000007" \
+ --body-file /tmp/body.txt
+ ```
+
+ Then, after send signoff and successful send, record it:
+
+ ```bash
+ bun run admin -- content-rights record-correspondence CHR-000007 \
+ --direction outbound \
+ --to "requester@example.com" \
+ --from "ClawHub <noreply@notifications.openclaw.ai>" \
+ --subject "Re: CHR-000007" \
+ --body-file /tmp/body.txt \
+ --provider-message-id "<providerId-from-send-response>" \
+ --attachment /tmp/evidence.pdf
```
Run from the ClawHub repository root with the normal authenticated admin CLI.