Skip to content
Get packs

Guide · Agent skill

How to use the ClawHub Content Rights Email agent skill

Updated · written with AI from the project's own documentation and checked against our catalogue data

This is a guide to the clawhub-content-rights-correspondence agent skill, a set of written procedures that tells an AI agent how to handle email for a content rights case that already exists in ClawHub, the skill registry run by the OpenClaw project. The skill is built for ClawHub staff and maintainers, because it depends on the internal admin command line tool, authenticated access and existing CHR case IDs. After reading, you will know what the skill does, how to install it, how to phrase a request so the agent uses it, and what safety limits it sets.

ClawHub Content Rights Emailopenclaw/clawhub · MIT

Quick start

  1. 1Get the skill files. Download the ZIP from the download link on this directory page and unzip it, keeping the clawhub-content-rights-correspondence folder with SKILL.md.
  2. 2Place the skill. Put the folder in ~/.claude/skills/ for personal use or in .claude/skills/ inside your project, or upload the ZIP under Settings, Capabilities, Skills.
  3. 3Check prerequisites. Confirm you have the ClawHub repository checked out, Bun installed, authenticated admin CLI access and an existing CHR-... case ID.
  4. 4Ask for a preview. Describe the case and recipient in plain language and ask for a dry run so the agent shows the recipient, subject and body.
  5. 5Approve and send. Give explicit signoff on the final draft. The agent sends through the admin CLI and then records the exact correspondence in the case.

What this agent skill makes the agent do

An agent skill is a folder containing a SKILL.md file of instructions that an AI agent loads when a request matches the skill's description. This skill is triggered when someone wants to draft, send or preserve email correspondence for an existing ClawHub content rights case.

The skill fixes the order of work. The agent previews each email with a dry run, shows the final recipient, subject and body, and waits for explicit human approval. It then sends the email through the ClawHub admin CLI and records the exact sent message in the case file so there is an audit trail. The skill forbids creating new cases and forbids resending an email if the recording step fails.

  • Requires an existing CHR-... case ID; it never creates cases
  • Uses bun run admin -- email send for outbound email
  • Uses bun run admin -- content-rights record-correspondence to preserve the sent message
  • Includes a publisher removal notice template and a requester status update flow

Install the clawhub-content-rights-correspondence skill

Download the ZIP from the download link on this directory page. Unzip it so that the clawhub-content-rights-correspondence folder, containing SKILL.md, sits in one of the skill locations below. For a personal install, use ~/.claude/skills/. For a single project, use the .claude/skills/ folder inside that project.

You can also upload the ZIP in the Claude apps under Settings, then Capabilities, then Skills. The package lists two files: agents/openai.yaml and SKILL.md.

  • Personal: ~/.claude/skills/clawhub-content-rights-correspondence/
  • Project: .claude/skills/clawhub-content-rights-correspondence/ inside your project
  • Claude apps: Settings, then Capabilities, then Skills, then upload the ZIP
~/.claude/skills/clawhub-content-rights-correspondence/SKILL.md

Prerequisites: what you need before the skill works

The skill is not a standalone tool. It assumes you already have the ClawHub repository checked out, the Bun runtime installed, and authenticated access to the ClawHub admin CLI. It also needs access to the Hermit case system used by content-rights record-correspondence. Without these, the commands in the skill will fail.

You must also have an existing case ID in the form CHR-... before you start. The skill will not open one for you.

  • Bun runtime and a ClawHub repository checkout
  • Authenticated ClawHub admin CLI access (bun run admin)
  • Access to the Hermit case system
  • An existing CHR-... case ID

Trigger the skill with clear natural requests

Agents choose skills by matching your request to the skill description, so name the task and the case. Mention that you want a draft or a preview first, and say clearly when you are approving a final version to be sent.

Be explicit about the recipient and the case. Agents follow the safety rules in the skill, so a request to send without approval will be stopped at the preview step.

  • Draft a removal notice for publisher handle example-publisher on case CHR-000007, preview only.
  • Send the approved removal notice for CHR-000007 to the publisher and record it in the case.
  • Send a status update to requester@example.com for CHR-000007 and log the provider message ID.
  • Show me the case record for CHR-000007 after the correspondence is logged.

Run the publisher removal notice workflow

For a publisher removal notice, the skill uses a fixed subject and body. The body names the skill URL and a response form. The agent first previews the email with the publisher handle, then sends it only after you give explicit signoff, then records the sent correspondence with the provider message ID from the send response.

The preview command looks like this. Replace the publisher handle and make sure the body file is at /tmp/body.txt.

  • Do not add a greeting to the body; the template already adds one.
  • Do not pass --title, and do not repeat the subject in the body.
  • Do not use the generic email action button; put the form URL as plain text.
bun run admin -- email send --user <publisher-handle> --subject "ClawHub skill removal notice" --body-file /tmp/body.txt

Safety notes: scripts, network and what not to do

The listing marks this skill as running scripts and using the network. The SKILL.md tells the agent to use the authenticated admin CLI commands directly and not to use helper scripts, direct Hermit calls or direct R2 access for correspondence. Read the SKILL.md and the commands it lists before you let an agent run them, and only run the skill inside a repository you trust.

The skill is scoped to content rights correspondence. The removal notice template names Rednote/Xiaohongshu rights, so do not reuse it for general or marketing email. Attachments passed with --attachment are archived with the correspondence, but the generic email template does not send them.

  • Never send without explicit signoff on the final draft
  • If recording fails after a send, do not retry the send; report it so staff can repair the audit record
  • Run commands from the ClawHub repository root

What people use it for

  • Sending a publisher removal notice for a skill removed after a Rednote/Xiaohongshu content rights request, with the response form link included as plain text.
  • Sending a requester a status update or closure note without exposing the internal case ID in the subject line.
  • Checking a case with content-rights get after an email is logged to confirm the correspondence is attached.
  • Reviewing how an agent should safely send outbound email tied to a case record, as a reference for maintainers.

Frequently asked questions

How do I install the clawhub-content-rights-correspondence skill?

Download the ZIP from the download link on this directory page and unzip it into ~/.claude/skills/ for personal use or into .claude/skills/ inside a project. You can also upload the ZIP in the Claude apps under Settings, then Capabilities, then Skills.

Is the ClawHub content rights email skill free to use?

The skill is published under the MIT licence. Using it still requires ClawHub internal access, including the authenticated admin CLI, Bun, the repository checkout and Hermit case access.

Can I use this skill if I am not ClawHub staff?

No. The skill requires internal admin CLI access, authenticated credentials and existing internal case IDs, so a general user cannot run it.

What do I need before the skill will work?

You need the ClawHub repository checked out, the Bun runtime, authenticated access to bun run admin, access to the Hermit case system, and an existing CHR-... case ID.

Can the skill create a new content rights case?

No. The skill requires an existing CHR-... case and forbids creating cases. Open the case through your normal ClawHub process first.

Why won't the agent resend an email if logging fails?

Resending could send a duplicate to a real person. The skill tells the agent to report the recording failure so staff can repair the audit record without sending again.

New agent skills, repos and AI tools — every week

The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.

Our verdict

This skill suits ClawHub staff and maintainers who want an agent to draft, preview, send and log content rights replies in a consistent, audited way. It is a poor fit for anyone outside ClawHub, for general or marketing email, or for anyone unwilling to review the scripts and network access before running it.

Download the skill